### Problem to solve <!-- What problem do we solve? --> GitLab CI/CD shows job log information, so you can dig into why tests fail, but it requires humans reading a bunch of text. Most languages/frameworks are able to output [JUnit XML](https://en.wikipedia.org/wiki/JUnit) (or xUnit, NUnit, PHPUnit, etc.) **The user** needs a way to **more efficiently digest JUnit-style XML information** so that they **can find out why tests fail quicker**. ### Intended users <!-- Who will use this feature? If known, include any of the following: types of users (e.g. Developer), personas, or specific company roles (e.g. Release Manager). It's okay to write "Unknown" and fill this field in later. Personas can be found at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/ --> ### Further details <!-- Include use cases, benefits, and/or goals (contributes to our vision?) --> ### Proposal <!-- How are we going to solve the problem? Try to include the user journey! https://about.gitlab.com/handbook/journeys/#user-journey --> - https://gitlab.com/gitlab-org/gitlab-ee/issues/24792 An artifact-based view to see the amount of tests vs failed for pipeline pages. This will gather cross job test information and collectively shows it, including metadata. - https://gitlab.com/gitlab-org/gitlab-ee/issues/22360 Focusses in on making it easy to find out about when a failed test was introduced. - https://gitlab.com/gitlab-org/gitlab-ee/issues/24944 A historical view which showcases unit test information across pipelines. They will include information such as: * We can determine which tests fail, not just which jobs (when a job runs many tests) * => We can display better summary information of failures * We can determine time taken for each test individually * => We can graph/analyze test durations over time * => We can use test duration to balance parallel jobs ### Links / references