dc
ad061946c3
The shared-estate cycle is two npm scripts and sasjs test, but the seed in npm run server is load-bearing: without it testsetup 404s settings.sas and 59 of the 64 test programs fail to complete, which reads like a broken deployment. Record the targets, the token-pair credentials, the ADMIN group the estate actually uses, how to read the results, and the frontend passphrase steps as a repo-local skill, and point the testing doc at it.
1.3 KiB
1.3 KiB
Testing
Backend (SAS) tests are run with the sasjs CLI from the sas/ directory. For a deploy-and-run on the shared state see the dc-estate-testing skill (.agents/skills/dc-estate-testing/SKILL.md), which covers the credentials, the makedata seed the suite needs and the estate's group name.
Commands
- Full deploy + test cycle:
npm run 4gl(compiles, deploys to the 4gl target, runs makedata) thensasjs test -t 4gl. - The shared estate under its
servertarget:npm run server(compile, deploy, seed) thensasjs test -t server. - Run tests only (no rebuild/redeploy):
sasjs test -t 4gl. - Run a subset of tests:
sasjs test -t 4gl SOMESTRING— the positional argument filters to matching tests (e.g.sasjs test -t 4gl stagedata.test.3).
Results
- Test results:
sas/sasjsresults/testResults.json/.csv/.xml - Individual test logs:
sas/sasjsresults/logs/<testsuite>.log(e.g.services_editors_stagedata.test.3.log) - Coverage:
sas/sasjsresults/coverage.lcov
Notes
- Test source files live in
sas/sasjs/**;sas/sasjsbuild/is generated build output — do not hand-edit it. sasjs testexecutes tests against the deployed app, so runnpm run 4glfirst after changing any service/hook/test code.- Assertions are made with
%mp_assert(); results are written towork.test_results.