...
Time | Item | Who | Notes | ||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Bug Triage: review the following bugs and prioritize
| |||||||||||||||||||||||||||||||||
3.5 Release Candidate test plan
Tasks before Release Candidate testing starts:
Bugs that must be fixed before release candidate
Setting up and managing bug triage
| Sam Im (Deactivated) | Create different test cycles for each team that contain multiple components in each test cycle. Reorganize test cases by new features first? Reviewing test cases when they are new: Test cases that haven't been reviewed should be in a QA status. QA person will review test case and decide if the test is a CoreRegression testing. Every 2-3 sprints, review test cases that were tested or impacted by the most recent changes. Check test cases to ensure they are still valid and steps are correct. |
Action items
- Sam Im (Deactivated) to schedule meeting with Ashraf & Adugna, and QA team to explain writing test cases changes
- Joanna Szymańska (Deactivated) add what was changed in test cases and what Adugna or others should do moving forward when writing test cases