You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Review issues reported on the board with “no test id” or “no test case” to decide whether to include them in the test sheet or specify which test they are part of
The text was updated successfully, but these errors were encountered:
I reviewed the issues, searched the test sheet using keywords, and then classified them with the closest Test ID, e.g.: #379
This process should be part of the triage so that each issue corresponds to a test case ID in the spreadsheet. However, this approach doesn't solve what happens when a test case is marked as passing, but a new report is created with no test ID that matches that test case —maybe because someone was testing another part of the system and found this behavior by accident.
@magajh@DonatoBD: what do you think we should do in this case? I believe the test cases should be marked as failing too, so we keep the 1:1 relationship between the test sheet and this board, but we'd need a way of communicating the status changes.
Context
https://openedx.atlassian.net/wiki/spaces/COMM/pages/4318527513/Redwood.1+Retrospective
Tasks
The text was updated successfully, but these errors were encountered: