Date
Attendees
Goals
- Review comments or questions about
regression testing ticketJira Legacy server JIRA (openlmis.atlassian.net) columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2721 - This ticket should be assigned to Lucyna and included in the current sprint
- Discuss expectations for the showcase to explain the regression testing ticket
- Should we use Labels for the regression testing?
- Review updates to Test Strategy
- If there's time to discuss:
- RBAC testing: what exists today that we need to expand on? Is this easy to pull out of the test cases today? For example, testing the requisition workflow for a user that has create rights. This user should be able to create for their facilities, but they shouldn't be able to see the Approve dropdown, or Convert to Order screens, they should not be able to delete once a requisition has been authorized, etc.
Discussion items
| Time | Item | Who | Notes |
|---|---|---|---|
...
- Define goals for big regression
- Create RBAC test cases (what is missing?)
- Create Requisition workflow status test cases - test cases for all requisition statuses such as: Not yet started, initiated, rejected, deleted, authorized, approved, released.
- Setting up demo data (adding new users to support new features, updating rights and roles for these new scenarios)
- Define testing metrics & traceability (what needs to be updated in test tickets to maintain the existing traceability reports?)
- Tickets for improvements (contract tests, documentation)
- Should we track regression testing with labels in JIRA?