Skip to content

Commit 588f97b

Browse files
committed
(spec) Normalize integration test formatting
1 parent 2e14784 commit 588f97b

2 files changed

Lines changed: 5 additions & 2 deletions

File tree

‎specs/integration-test-list.md‎

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -413,10 +413,12 @@ This section exists to force implementation as true integration tests, not unit
413413

414414
- `tests/integration/smoke/`: INT-001..INT-004 (fast baseline).
415415
- `tests/integration/architecture_p0/`: INT-005..INT-030, INT-053..INT-056, INT-061..INT-063, INT-070..INT-075, INT-101..INT-114, INT-120..INT-128, INT-184, INT-187, INT-200, INT-201, INT-204.
416-
- `tests/integration/architecture_p1/`: (TODO: find tests here)
417-
- `tests/integration/architecture_p2/`: (TODO: find tests here)
416+
- `tests/integration/architecture_p1/`: (TODO: find tests here)
417+
- `tests/integration/architecture_p2/`: (TODO: find tests here)
418+
418419
<!--- `tests/integration/evals_p2/`: INT-046..INT-052, INT-151..INT-156.
419420
Note: eval tests are not in force - eval themselves are.--->
421+
420422
- `tests/integration/agent/p1/`: INT-181, INT-182, INT-183, INT-185, INT-186.
421423
- `tests/integration/frontend/p0/`: INT-157, INT-158, INT-159, INT-162, INT-163, INT-164, INT-165, INT-167, INT-170, INT-172, INT-173, INT-174, INT-177, INT-189, INT-205.
422424
- `tests/integration/frontend/p1/`: INT-160, INT-161, INT-166, INT-168, INT-171, INT-175, INT-176, INT-178, INT-179.

‎specs/integration-test-rules.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -164,4 +164,5 @@ Validation-preview tests should therefore assert:
164164
Controller-initiated heavy operations are expected to travel through Temporal workflows. Integration tests that verify product behavior from controller or agent tool paths should assert workflow lifecycle, persisted events, and returned results from the Temporal-mediated path.
165165

166166
Direct `worker-heavy` HTTP requests remain valid only in integration tests that exercise worker-level boundaries such as single-flight admission, crash containment, and preview artifact generation. They are not the product-path routing model for controller tool calls.
167+
167168
<!--FIXME: so are worker-render-->

0 commit comments

Comments
 (0)