autonomic-bot
f283a371bb
Sanitized single-commit public mirror of recipe-maintainer. - Removed test-ssh/.testenv (live creds); added test-ssh/.testenv.example placeholders. - Removed plans/ and planned-updates/ (deployment-planning docs) so no client/ deployment domains appear in the public repo. - All other secret stores were already gitignored. - docs.coopcloud.tech retained as a submodule (public upstream).
2.0 KiB
2.0 KiB
description, argument-hint, allowed-tools
| description | argument-hint | allowed-tools | ||||||
|---|---|---|---|---|---|---|---|---|
| Run all tests for a Co-op Cloud recipe | <recipe-name> |
|
Recipe Test
Run all available tests for a Co-op Cloud recipe.
The recipe name is: $ARGUMENTS
Read and follow the instructions in .claude/commands/includes/logging.md.
Read and follow the instructions in .claude/commands/includes/guidelines.md.
Steps
-
Free server resources by running
/test-context-reset $ARGUMENTSto undeploy unrelated apps from the test server while keeping this recipe and its dependencies running. -
Locate the test directory at
recipe-info/$ARGUMENTS/tests/.- If the directory does not exist, tell the user no tests are configured for this recipe and suggest running
/recipe-check $ARGUMENTSfirst (which creates the directory structure). - Stop here if no test directory is found.
- If the directory does not exist, tell the user no tests are configured for this recipe and suggest running
-
Read the test plan from
recipe-info/$ARGUMENTS/test.md.- Note the target URL and any manual verification steps listed.
- Note which automated check scripts are referenced.
-
Discover all test scripts by globbing
recipe-info/$ARGUMENTS/tests/*.py. -
Run each test script in sequence:
- Execute each
.pyscript withpython3 recipe-info/$ARGUMENTS/tests/<script>. - Capture stdout and stderr.
- Record whether each script exited 0 (PASS) or non-zero (FAIL).
- Execute each
-
Perform the manual verification checks listed in
test.md:- For URL-based checks (e.g. "open URL and confirm page loads"), use
curlorWebFetchto verify the endpoint is reachable and returns expected content. - Report which manual checks could be verified automatically and which truly require a human.
- For URL-based checks (e.g. "open URL and confirm page loads"), use
-
Summarise results:
- List each automated script with its PASS/FAIL status and output.
- List each manual check with its result (verified / needs human / failed).
- If any tests failed, highlight them clearly and suggest troubleshooting steps.
- If all tests passed, confirm the recipe deployment looks healthy.