Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

“no test id” or “no test case” issues #391

Open
jalondonot opened this issue Oct 7, 2024 · 1 comment
Open

“no test id” or “no test case” issues #391

jalondonot opened this issue Oct 7, 2024 · 1 comment
Assignees
Labels
retrospective Action items from previous release retrospectives.

Comments

@jalondonot
Copy link

Context
https://openedx.atlassian.net/wiki/spaces/COMM/pages/4318527513/Redwood.1+Retrospective

Tasks

  • 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
@mariajgrimaldi mariajgrimaldi added the retrospective Action items from previous release retrospectives. label Oct 21, 2024
@mariajgrimaldi
Copy link
Member

mariajgrimaldi commented Oct 23, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
retrospective Action items from previous release retrospectives.
Projects
Status: No status
Development

No branches or pull requests

2 participants