mirror of
https://github.com/azaion/gps-denied-onboard.git
synced 2026-06-23 05:01:14 +00:00
Oleksandr Bezdieniezhnykh
1f634c2604
ci/woodpecker/push/02-build-push Pipeline failed
- Modified the autodev state to reflect the current testing phase and details of the new `jetson-e2e` tests. - Enhanced the "How to Test" documentation to provide clearer instructions on the demo replay validation process, including video and tlog alignment steps. - Updated architectural documentation to include the new demo replay operator flow and its dependencies. - Documented the removal of deprecated auto-sync features and clarified the operator-facing UI for replay validation. - Added new entries in the dependencies table for upcoming tasks related to the demo replay flow. These changes improve clarity and usability for operators and developers working with the demo replay system.
46 lines
1.9 KiB
Markdown
46 lines
1.9 KiB
Markdown
# Step 1t: Test Infrastructure Bootstrap (tests-only mode only)
|
|
|
|
**Role**: Professional Quality Assurance Engineer
|
|
**Goal**: Produce `01_test_infrastructure.md` — the first task describing the test project scaffold.
|
|
**Constraints**: This is a plan document, not code. The `/implement` skill executes it.
|
|
|
|
## Steps
|
|
|
|
1. Read `TESTS_DIR/environment.md` and `TESTS_DIR/test-data.md`
|
|
2. Read `problem.md`, `restrictions.md`, `acceptance_criteria.md` for domain context
|
|
3. Document the test infrastructure plan using `templates/test-infrastructure-task.md`
|
|
|
|
The test infrastructure bootstrap must include:
|
|
|
|
- Test project folder layout (`e2e/` directory structure)
|
|
- Mock/stub service definitions for each external dependency
|
|
- `docker-compose.test.yml` structure from `environment.md`
|
|
- Test runner configuration (framework, plugins, fixtures)
|
|
- Test data fixture setup from `test-data.md` seed data sets
|
|
- Test reporting configuration (format, output path)
|
|
- Data isolation strategy
|
|
|
|
## Self-verification
|
|
|
|
- [ ] Every external dependency from `environment.md` has a mock service defined
|
|
- [ ] Docker Compose structure covers all services from `environment.md`
|
|
- [ ] Test data fixtures cover all seed data sets from `test-data.md`
|
|
- [ ] Test runner configuration matches the consumer app tech stack from `environment.md`
|
|
- [ ] Data isolation strategy is defined
|
|
|
|
## Save action
|
|
|
|
Write `todo/01_test_infrastructure.md` (temporary numeric name).
|
|
|
|
## Tracker action
|
|
|
|
Create a work item ticket for this task under the "Blackbox Tests" epic. Write the work item ticket ID and Epic ID back into the task header.
|
|
|
|
## Rename action
|
|
|
|
Rename the file from `todo/01_test_infrastructure.md` to `todo/[TRACKER-ID]_test_infrastructure.md`. Update the **Task** field inside the file to match the new filename.
|
|
|
|
## Blocking
|
|
|
|
**BLOCKING**: Present test infrastructure plan summary to user. Do NOT proceed until user confirms.
|