Sam (for Team ILL) Joanna (for Team Parrot) | - Create Test Cycles
- Create missing test cases and assign to test cycles
- Assign Test Cases to team members
- Point person for any questions about test cases from the team
- Review execution of the test cycles, there should be positive progress during the day
- Prioritize bugs per test cycle, Check that developers have detailed proposed solutions (if time allows or developer's experience allows)
- Report the status of each test cycle, including defects reported, before end of day
- Review automated testing and provide status before end of day (go to http://build.openlmis.org/view/all/builds)
| - Sam Im (Deactivated) One question concerning the next phase of regression tests. In this phase, some of the test cases were added to more than one test cycle, and thus executed by more than one person (frequently by members of both teams, and in several cases, even by three people, as they were added to the Team Parrot's cycle and two team ILL's cycles). Will it be so also in the next phase? I'm asking about it because during standard regression test cycle executions, the test cases were divided between testers and each test case was always executed only once, by one person.
|
| Team ILL & Team Parrot | - Execute test cases assigned to you
- Record the test execution by following these steps:Testing Process
- Enter Defects as needed (by following the steps detailed in the "creating bugs" section below)
- If there are any Blocker bugs, try to spend time completing a root cause analysis and detail in the bug ticket
- When a defect is found, research and provide proposals in the ticket for review by Sam & Joanna (as time allows)
- Assist other testers as needed
- Josh Zamor to set up testing server environment(s)
- Josh Zamor to provide updates on automated performance testing results
- Brandon Bowersox-Johnson to coordinate manual UI Performance Testing
| - For the test run in Sprint 38 testers will be Sam Im, Visvapriya Kandasamy, maybe one dev from Team Parrot if they are not working on critical tickets
- Brandon Bowersox-Johnson will work with Paweł Gesek on assigning responsibility for member on Team Parrot to help test UI performance during the release candidate testing
|