...
For Regression testing we will follow this bug prioritization (also outlined on docs.openlmis.org):
| Priority Level | Example |
|---|
| Blocker | - Cannot execute function (cannot click button, button doesn't exist, cannot complete action when button is clicked)
- Cannot complete expected action (does not match expected results for the test case)
- No error message when there is an error
- We will not not release with this bug
|
| Critical | - Error message is unactionable by the user, and user cannot complete next action (500 server error message)
- Search results provided do not match expected results based on data
- Poor UI performance or accessibility (user cannot tab to column or use keyboard to complete action)
- We should not release with this bug
|
| Major | - Performance related (slow response time)
- Major asthetic issue (See UI Styleguide for reference)
- Incorrect filtering, but doesn't block users from completing tasks and executing functionality
- Wrong user error message (user does not know how to proceed based on the error message provided)
|
| Minor | - Asthetics (spacing is wrong, alignment is wrong, see UI Styleguide)
- Message key is wrong
- Console errors
- Service giving the wrong error between services
|
| Trivial | |
...