anthony.wen
2eed645a85
- update the ATVM automation guide to require a post-template verification gate before launching run-sorry-cypress.py - require verification that both the generated .ts files and the config specPattern include every requested VM after cmc-templates.py finishes - document that the runner must not be launched when any requested VM is missing from the generated spec set - update the ATVM AGENTS rules so this template-to-runner verification step is part of the default automation workflow
ATVM Workspace
This folder contains the ATVM setup workflow, ATVM Cypress automation workflow, and the lab inventory/reference material used to operate them.
Start Here
- Setup/bootstrap workflow:
docs/setup/guide.md
- ATVM Cypress automation workflow:
docs/automation/guide.md
- Shared maintenance conventions:
docs/workflow/conventions.md
- Environment inventory and credentials:
inventory/overview.md
Layout
scripts/- executable scripts used by setup/bootstrap
docs/setup/- setup procedure and setup run learnings
docs/automation/- automation procedure, reusable examples, and automation run learnings
docs/workflow/- conventions for how this workspace is structured and maintained
inventory/- environment inventory, credentials, reserved IPs, and reference maps
archive/imported-notes/- preserved original long-form notes that were reorganized into the current structure
Practical Guidance
- Use
guide.mdfiles for authoritative workflow behavior. - Use
examples.mdfor reusable command patterns only. - Use
run-learnings.mdonly when a run produced a new lasting lesson. - For detailed ATVM automation test results, especially per-host failures, use
/root/cdc-e2e-cyp-12.17.4/cypress/cmcReporteron the automation controller. - Use
inventory/for persistent environment information such as hosts, credentials, and IP assignments. - Use
archive/imported-notes/when you need the original full historical notes in their original layout.