Document Playwright coverage expectations
This commit is contained in:
@@ -49,3 +49,4 @@ This board is normalized to the shared playbook lane model.
|
||||
- After the merge, move the ticket into `Ready for Test` and then `Deploying to Dev` while the dev build/deploy proves the change.
|
||||
- Trinity handles validation once the dev environment is ready, and the ticket only moves forward after the live check passes.
|
||||
- QA promotion is a separate step after dev validation, not part of the merge itself.
|
||||
- When new functionality lands, update the Playwright suite at the same time so browser coverage keeps pace with the app and can gradually replace repetitive manual validation.
|
||||
|
||||
Reference in New Issue
Block a user