Starter scenarios for creating saved tests with ta. The markdown files are
authoring references: translate their actions and assertions into dashboard test
steps, then run the saved tests in TesterArmy cloud.
examples/
├── TESTER.md
├── prompts/
│ └── ad-hoc-regression.md
└── tests/
├── 01-landing-page.md
├── 02-auth-smoke.md
└── 03-project-create.md
Find your project, then create a test based on a scenario:
ta projects list --json
echo '{"title":"Landing page","steps":[{"title":"Open the landing page","type":"act"},{"title":"The main heading and primary call to action are visible","type":"assert"}]}' | ta tests create --project <projectId> --jsonUse IDs returned by the commands. For development validation, save a cloud-reachable preview or tunnel URL as an environment:
ta projects environments-create <projectId> --name Development --url https://dev.example.com --json
ta tests run <testId> --env development --wait --jsonFor a saved suite, find its group and run the group:
ta groups list --project <projectId> --json
ta tests run --group <groupId> --project <projectId> --env development --wait --json--wait waits for validation to finish; without it, success only confirms that
the run was queued. Save JSON output locally when an artifact is useful:
ta tests run <testId> --env development --wait --json > result.json