mirror of https://github.com/azaion/gps-denied-onboard.git synced 2026-06-21 07:11:13 +00:00

Files

T

Oleksandr Bezdieniezhnykh 827d4fe644 [AZ-240] Update product implementation and task decomposition processes

- Refined task decomposition steps to ensure implementation tasks are atomic and complexity does not exceed 5 points.
- Enhanced the product implementation process with a completeness gate to verify task outcomes against architecture promises before proceeding to testing.
- Updated dependencies table to reflect new tasks and their relationships, ensuring all test tasks are linked to product remediation tasks.
- Adjusted workflow documentation to clarify entry points for task decomposition and implementation contexts.

Co-authored-by: Cursor <cursoragent@cursor.com>

2026-05-05 01:02:25 +03:00

2.0 KiB

Raw Blame History

Step 3: Blackbox Test Task Decomposition (tests-only mode only)

Role: Professional Quality Assurance Engineer Goal: Decompose blackbox test specs into atomic, implementable task specs. Constraints: Behavioral specs only — describe what, not how. No test code.

Numbering

In tests-only mode: start from 02 (01 is the test infrastructure bootstrap from Step 1t).

Steps

Read all test specs from DOCUMENT_DIR/tests/ (blackbox-tests.md, performance-tests.md, resilience-tests.md, security-tests.md, resource-limit-tests.md)
Group related test scenarios into atomic tasks (e.g., one task per test category or per component under test)
Each task should reference the specific test scenarios it implements and the environment/test-data specs
Dependencies:
- In tests-only mode: blackbox test tasks depend on the test infrastructure bootstrap task (Step 1t)
Write each task spec using templates/task.md
Estimate complexity per task (1, 2, 3, 5 points); no task should exceed 5 points — split if it does
Note task dependencies (referencing tracker IDs of already-created dependency tasks)
Immediately after writing each task file: create a work item ticket under the "Blackbox Tests" epic, write the work item ticket ID and Epic ID back into the task header, then rename the file from todo/[##]_[short_name].md to todo/[TRACKER-ID]_[short_name].md.

Self-verification

Every scenario from tests/blackbox-tests.md is covered by a task
Every scenario from tests/performance-tests.md, tests/resilience-tests.md, tests/security-tests.md, and tests/resource-limit-tests.md is covered by a task
No task exceeds 5 complexity points
Dependencies correctly reference the test infrastructure task
Every task has a work item ticket linked to the "Blackbox Tests" epic

Save action

Write each todo/[##]_[short_name].md (temporary numeric name), create work item ticket inline, then rename to todo/[TRACKER-ID]_[short_name].md.

2.0 KiB Raw Blame History