Replies: 1 comment
|
Krake_Regression_Test_TOC.docx |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Structure decision is made: chapters are scope-based (One-Time Tests / Infrequent Tests / Per-Release Tests). Within each, individual test cases are tagged by domain (Hardware / Firmware / Both) rather than hardware and firmware being separate chapters — this avoids splitting tests that inherently span both.
First draft targeted for early next week. Will post here for review once ready — flag anything you want changed, including if you think domain should be a full structural chapter after all; open to revisiting if the tagging approach doesn't hold up in practice.
@ForrestErickson @nk25719 @Yhya99
All reactions