Test spec review feedback #20

Closed
opened 2026-09-07 04:11:32 +00:00 by Ty · 1 comment
Owner
    • the document is full of magic acronyms. Dont do that. If theres acronyms to use, do it AFTER they have been defined.
    • The cannonical rule at the top of the document is "Each case states what must happen, where the rule lives, and how it is verified.". EVERY TEST CASE FAILS TO FOLLOW THIS RULE.
  1. Phase 1 remainder - "Ty drives curl through a full calibrated → ready cycle; OPENAPI endpoints match" >> NO Ty doesnt. The test automation written by the AI Agents does.
  2. What the hell does the 'cadence' column mean?
  3. This spec does not define how the test cases are to be executed. Where is the automation written? How it is harnessed? What tools / dependencies are needed? Where are they staged (Playwright??)

This is junior level work.

1. - the document is full of magic acronyms. Dont do that. If theres acronyms to use, do it AFTER they have been defined. 2. - The cannonical rule at the top of the document is "Each case states what must happen, where the rule lives, and how it is verified.". EVERY TEST CASE FAILS TO FOLLOW THIS RULE. 3. Phase 1 remainder - "Ty drives curl through a full calibrated → ready cycle; OPENAPI endpoints match" >> NO Ty doesnt. The test automation written by the AI Agents does. 4. What the hell does the 'cadence' column mean? 5. This spec does not define *how* the test cases are to be executed. Where is the automation written? How it is harnessed? What tools / dependencies are needed? Where are they staged (Playwright??) This is junior level work.
Owner

Closed: feedback addressed during M3.

Closed: feedback addressed during M3.
Sign in to join this conversation.
No Label
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Ty_Tech/SlabUploader#20