Home / How we test
Written and maintained by Muke Lam (X: @LamMuke)
Test runs follow written task cards and are carried out by scripts and other automation, including an AI executor. Commands and their output are written down, and a number on a page can be traced to the record it came from.
This page says how the numbers on ArtCraft Tutorial were produced: which machine, which files, which marks, and what we do when a page is wrong.
ArtCraft Tutorial is written and maintained by Muke Lam.
We are not affiliated with, sponsored by or endorsed by ArtCraft, Storyteller.ai or the storytold project. We don't accept payment, free products or pre-publication review from them, and this site has no affiliate links.
Write to contact@artcrafttutorial.com.
Mac. The notes name an Apple-silicon Mac on macOS 26. The Oct 18, 2026 preflight for the local-setup guide recorded macOS 26.4 and arm64. The session notes name a Mac mini on that same macOS 26.4, and one note names the chip Apple M4. A read on Oct 31, 2026 names the model Mac16,10 and the chip Apple M4, on the same macOS 26.4. A page that only says macOS 26, or only Apple silicon, is not naming that model.
Browser. The web package from a GitHub release, served from 127.0.0.1 and opened in headless Chromium at 1440×900.
Each app page names the version we ran, the platform, and the day. Test files are ones we made, samples that shipped with the app, or samples from other sources. The app page says which it used.
A run follows written task cards. The steps are carried out by scripts and other automation, including an AI executor working from the card. Commands and their output are written down. The logs stay in our own project records. Those records are not published, and this page does not give their paths. A number on a page can be traced to the record it came from. Each task card has a report. The Oct 31, 2026 version update was checked this way: a second reviewer, another AI executor, read the report against the saved logs and against GitHub before publication. Small wording fixes are read and signed off by the team without a second review.
Screenshots are taken during the run, and the Screenshots section below says how they are captioned and cropped.
Installers come from the official GitHub releases (storytold) and from getartcraft.com. When a release includes SHA256SUMS.txt, we check the download with shasum -a 256. ArtCraft Studio's release has no checksum file. For that one we compared a local shasum -a 256 with the digest the GitHub API returned. We do not treat a missing checksum file as if it were there.
Gatekeeper is recorded only for the packages the notes cover. On Oct 14, 2026 a read-only check of PhotoCraft 0.8.2 and ArtCraft Studio 0.41.0 found both notarized. spctl accepted both as Notarized Developer ID, so that check says Gatekeeper would not block those two. The disk images were mounted read-only, the apps were not opened, and quarantine was not cleared with xattr. On Oct 17, 2026 the WordCraft, GridCraft and DeckCraft 0.7.0 command-line builds ran without a quarantine attribute blocking them, so xattr was not used. On Oct 19, 2026 the PhotoCraft 0.10.0, WordCraft 0.8.0 and PDFCraft 0.9.0 command-line zips showed no Gatekeeper dialog and no quarantine attribute. Builds outside those notes are not covered.
On the apps page, ✓ means the thing we tried finished and produced a result. ◐ means we got part way. The words beside a ◐ say what was missing. ✗ means it did not work. The apps page does not define ✗; SoundCraft uses it where the command line refused a format.
On each app page, "What we tried, and what happened" is the main list of what we did on that build. Where an app page has complaint tests further down, they add to it. What we have not done sits under "What we haven't tested yet". A line taken from a project's README is labelled as the official claim. It is not one of our results.
The screenshots are ours. A caption names the app, the version, the platform and the date, as in Screenshot by ArtCraft Tutorial · DesignCraft 0.7.1 · macOS · Oct 16, 2026. Some captions say Mac instead of macOS.
Browser shots are the headless Chromium window at 1440×900. Desktop shots are window captures. A session note says when a shot was cut so a file path would not show, and when the window was left whole. On Oct 15, 2026 a PhotoCraft desktop session cropped shots so a full path would not show. The same day's DesignCraft session left three window shots whole at 1440×900, because the status line had no path. There is no single crop rule. Oct 14 browser notes point at webp files, and desktop notes record png captures. The notes do not describe one conversion step.
File size is the GitHub release asset's byte count. MB is that count divided by 1,048,576, to one decimal. KB is that count divided by 1,024. The download table uses KB for SHA256SUMS.txt. The exact count sits in a title attribute, so a hover shows it. A file we made ourselves is sized from the saved file, for example DesignCraft writes one export as a 45.1 KB PNG.
A release date is the GitHub time, converted to Eastern time, which is what the GitHub page says. On an app page, the version in the fact strip is the GitHub tag with a leading v removed, so v0.18.0 is written 0.18.0. The tag column on the GitHub page keeps the v. Studio's tag is artcraft-v0.41.0 and is shown that way.
Latest version means the newest GitHub release on the day the page says Facts checked. Tested build means the version that page says we ran. On PhotoCraft, Facts checked Oct 31, 2026 names latest release 0.18.0, and the tested build is 0.8.2.
Three counts, read from the records, match the app pages:
ls -l printed 80264 for designcraft-test, and file read it as Zip data. The DesignCraft page shows the same 80,264.elapsed_ms 2389 on the first screenshot. The page's first-screen line is that figure. It is the time until the first screenshot, not a timer on the whole session./usr/bin/time -l recorded real 14.56 seconds. The SoundCraft page rounds that to 14.6 s.Facts checked, and the date beside it, is the day we last checked the version, the date and the file size. A hands-on result belongs to the build that page names.
An app page has a button that reads "Want us to retest this version?" The note under the form says we read every request, but we can't promise when or whether we'll retest.
Email contact@artcrafttutorial.com with the page address and what you saw. We fix errors and update the date on the page.
A real correction. On Oct 31, 2026 a second reviewer checked a version update before it was published. One sentence on the Adobe comparison joined an Oct 19, 2026 look at the ArtCraft website to PhotoCraft 0.18.0, which GitHub published on Oct 31. Before publication the sentence was split: the Oct 19 look stays with the 0.7.0 that site showed that day, and 0.18.0 stays with the Oct 31 check. The page already on the site still had the older wording, which named 0.11.1. The mistake was caught in that review, not on the live site.