cms tested by Argusic Runner

Attempt 1 of 3 · Runs with mocks · Argusic Score 92.0 of 100

all runs of cmsapi-gatewaygatsbygatsbyjshacktoberfestheadlessheadless-cms

Session recording

Loading recording...

Download the original recording · fingerprint 0e074bbaae7b6be0...

What the test found

BCMS backend server starts on port 8080 with all 12 repository modules and all API controllers registered, connects to a mock MongoDB via mongodb-memory-server, and responds to health-check with status 200.

The project is a monorepo (BCMS headless CMS) with root, backend, cli, client, and ui packages. npm i at root triggers postinstall which installs backend and ui deps and builds types. The backend compiled successfully. No project-level tests exist (jest configs in cli/ and client/ have no matching test files). The UI could not be verified because it requires Vite/vue-tsc build which would need the full Node 20 toolchain and additional dependencies; the / route returning 500 is expected without a built UI. The CLI tests have no test files to run.

Argusic installed cms in 10 minutes and launched it; verification reached Verified with mock services. 4 of 4 recorded errors were worked through (see the timeline below).

Runs with mocksall runs of cms

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.

Discussion