Bug Triage: review the following bugs and prioritize
OLMIS-5637
-
Getting issue details...STATUS
: Joanna Bebak (Deactivated) to create a new test case for editing requisition template and validating the UI & print match
All slack channels (QA, General, Malawi) need to be notified that testing is starting two days before
Everyone needs to be notified when testing has started
Everyone is notified of testing status daily
Joanna Bebak (Deactivated) to link from Test strategy: Exploratory testing & Batch Approval testing - this needs to be explained for testers, or someone will need to own this to make sure it happens
Reviewing test cases from JSI before adding them to release candidate testing (has been done by Joanna Szymańska (Deactivated))
Reporting test plan: We need to work with Craig and Clay to understand what is needed to test reporting, who will test, and add details to test plan (Joanna Bebak (Deactivated) and Joanna Szymańska (Deactivated) to attend meeting)
Bugs that must be fixed before release candidate
Blocker and critical bugs
Malawi bugs?
Setting up and managing bug triage
Should we have a daily bug triage? Or should it be every couple of days?
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