Usability improvements for Unit Test Report view
Problem to solve
When I navigate to the tests tab the tests header data is really a job name from a pipeline which is confusing.
The headers on the Test Suite view are confusing, especially the duplicate names. In reality the Test Suite name should probably be pulled out and Class + Name combined into a column or just skip Class and use Name.
A use case from a customer
Our use case for this is the following: We run android-device tests on Google's Firebase Test labs. Each device the test runs on produces a junit_result.xml file. This results in the following quirk in displaying the test results:
When a test succeeds on all devices, it is listed in the results view exactly once. If the test fails on 4 devices, but succeeds on 3 devices, the test is listed as failing 4 times, and succeeding one time.
We thought to work around this by setting the suite name of each of the resulting files to the device characteristics, but it seems like the suite name is ignored by GitLab, and so this was unsuccessful.
Testsin the text under Summary
- Relabel 'Test Suites' to 'Job' to better reflect where the data is from
- In the detail view change out
suiteto better reflect the test being run
In the detail view add a toggle to sort the tests in the order ran OR sort failed tests first.- instead the failed tests will be shown by default and have an option to show all tests.
Permissions and Security
What does success look like, and how can we measure that?
- Changes detailed are made, UX approves