Created
November 20, 2025 18:31
-
-
Save Scheevel/20fe03794f2223eb483289471738307d to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| =qa | |
| *review and *gate based on scenarios in @ 2.7 | |
| create an e2e test spec for @ | |
| - Navigate to http://localhost:3000/search | |
| - Click the first component's "View" action to view card | |
| - On card observe "Component Schema" value is propably "Default-Schema" | |
| - On card observe "Note" input box (a field inherited from the Default-Schema) | |
| - On card click "edit" action button | |
| - On card click "Cancel" action button | |
| - Observe that "Component Schema" now reads "No schema selected" and observe that where "Note" input box was previously a message reads "No schema selected. Component data may not display correctly." | |
| - Expected: Cancel action should have changed nothing | |
| - Reality: Component card now appears as if Schema has been discarded | |
| Evaluate the console or logs for errors | |
| =analyst | |
| *elicit a new feature or refactoring that will implement the functionality described @ 6.9 | |
| use #9 Red Team vs Blue Team - Attack/defend the proposal | |
| When preparing the Dev Story determine the logical epic and story number from @docs/completed-epics.md | |
| ↳ | |
| Restate here only the concerns that need clarification before moving on, present them in a very concise format | |
| ↳ | |
| 1. Responsive Behavior Strategy on viewports < 1200px can we implement scro11 bars. Scroll between both sides of window? | |
| 2. Development Timeline is not relevant, ignore | |
| 3. Product Owner Sign-off - PROCESS CHECK will happen shortly | |
| ↳ | |
| =@sm | |
| *story-checklist @ 6.9 Don't try to do too much. Remove the duplicate in `backlog` but first make sure documents match. | |
| ↳ | |
| Restate here all the tests in the excessive test scope, present them in a very concise format | |
| ↳ | |
| Show me your REDUCED test scope recommendation | |
| ↳ | |
| Agreed, punt all the non-Chrome tests and I agree with the list of "manual verification instead" | |
| =po | |
| *validate-story-draft @ 6.9 and set status to for dev start | |
| =dev | |
| *develop-story @ 6.9 you are authorized to begin and follow closely the QA guidance in the story | |
| ↳ | |
| #1 Apply the DrawingViewer changes now | |
| ↳ | |
| Restate here only the concerns regarding the remaining phases, present them in a very concise format | |
| ↳ | |
| All is working as expected, finalize your dev notes on @ 6.9 | |
| =qa | |
| *review and *gate based on scenarios in @ 6.9 | |
| ↳ | |
| Restate here only the major concerns, in a very concise format | |
| ↳ | |
| commit all changes, this is for @ 6.9 tag as "known good check point" |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment