In order to define a strategy for testing UI specific elements, I have reviewed our manual test cases with the UI component. During the review, I found that some of the test cases were executed 1-2 times a long time ago (i.e. Sprint 25), which suggest that the test case isn’t valuable. Moreover, I found a few test cases with ~140 steps. According to the Testing Guide, a test case should contain up to 40 steps which I think is reasonable and we should avoid adding such long TCs.
Below you can see the improvements which may reduce the time spent on the release testing and increase the quality. All of the mentioned UI elements are currently tested manually.
- Filter buttons should be checked by functional tests (no need to test alignment in a separate ticket).
- Sort buttons should be checked by functional tests (no need to test alignment in a separate ticket).
- We should include checking some component, like the filter button, in the functional test for the specific screen rather than create a specific manual test case for all occurrences.
- Checking whether the given screen is accessible for a user with or without proper rights should be checked by functional tests.
- Dropdown placing shouldn’t be tested.
- Resizing input boxes shouldn’t be tested.
- The colors of the rows in the tables shouldn’t be tested.
- Redirecting to the login form after token expiration should be checked by functional tests.
- Product grid error messages (validations) should be checked by functional tests.
- Toggle on View Shipment should be checked by a functional test.
- There is no need to have a test case for the background of the application.
- The order of the items in the navigation bar should be checked by a functional test.
- Offline actions (power icon, initiate, submit, authorize) should be checked by functional tests.
- Filter button’s color should be checked by a functional test.
- The pagination component shouldn’t be checked separately because it is checked in the other functional tests (i.e. submitting requisition).
- The order of facilities within drop-downs has a unit test, so there is no need to check it manually.
- Auto-save the requisition should be checked by a functional test.
The UI elements which should be tested manually:
- Table horizontal scrollbar
- Sticky columns
- Sticky headers
I would appreciate your feedback very much.