letterpad tested by Argusic Runner
Attempt 1 of 3 · Runs · Argusic Score 100.0 of 100
all runs of letterpadblogging-systemcmsgraphqljournalismnextjsreact
Session recording
Download the original recording · fingerprint a0f7ebbfef2d2313...
What the test found
The admin app installed and seeded (demo user + 3 posts), starts as a Next.js dev server on port 3000, serves /login and /api/graphql with HTTP 200, returns seeded posts to an authenticated GraphQL author query and UnAuthorized without login, while the Jest suite does not complete in this container due to pre-existing type errors.
Admin dev server runs on port 3000 (Next.js 14.2.5). The Jest suite is blocked by pre-existing type errors surfaced once 'letterpad-graphql' resolves (schema-check regressions in context.ts/helpers.ts/dbTypeCheck.ts plus React.cache and Author-required-fields) and additionally requires an SMTP/mail fake and a mystery urlpattern config on a second orphaned dev instance; the fixes I applied are staged in git diff but the suite still cannot complete here. A second dev instance on port 3001 hit a URLPattern config error on /api/graphql; it did not disturb the verified 3000 instance and is irrelevant to this report.
Argusic installed letterpad in 50 minutes and launched it; verification reached Verified running for real. 4 of 4 recorded errors were worked through (see the timeline below).
This summary is drawn from the agent's recorded report for this run. Every figure traces to the log and recording above; nothing here is authored.
Error and fix timeline
No errors were recorded for this run.