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.

My suggestions:

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.

Those suggestions sound good to me. I think it would be most valuable to get our testers opinion on this. They can probably weigh in more and confirm where they are seeing regressions on the UI and where they don’t and whether that matches with what we want/don’t want to test.

Thanks for gathering this list Klaudia. I would love for all of this to be handled by functional tests. Here are some other scenarios that I’ve seen when testing that I’d like to be handled in functional tests, if they aren’t already:

Ad. 6 - I think resizing input boxes should still be tested because there were some regressions related to it.
Ad. 16 - I wonder whether this unit test works correctly, as for some reason, the following regressions occurred:

Joanna, we can add a functional test for resizing input boxes. As for the second issue, We never had that sorting on the UI but displayed facilities in the order returned by the backend. It is probably broken because of login refactor and saving (minimal) facilities in the database. Although, you are right; we should have a functional test for it.