<!-- The first section "Release notes" is required if you want to have your release post blog MR auto generated. Currently piloting, details can be found in this issue: https://gitlab.com/gitlab-com/Product/-/issues/1392 and this video: https://www.youtube.com/watch?v=rfn9ebgTwKg The next four sections: "Problem to solve", "Intended users", "User experience goal", and "Proposal", are strongly recommended in your first draft, while the rest of the sections can be filled out during the problem validation or breakdown phase. However, keep in mind that providing complete and relevant information early helps our product team validate the problem and start working on a solution. --> ### Release notes <!-- What is the problem and solution you're proposing? This content sets the overall vision for the feature and serves as the release notes that will populate in various places, including the [release post blog](https://about.gitlab.com/releases/categories/releases/) and [Gitlab project releases](https://gitlab.com/gitlab-org/gitlab/-/releases). " --> ### Problem to solve As a gitlab user looking at the [unit test report](https://docs.gitlab.com/ee/ci/unit_test_reports.html#viewing-unit-test-reports-on-gitlab), I want a clean view of data from failed tests (test file name, trace, test duration, etc.), so that I can make decisions / issues quickly and efficiently to get this pipeline passing. <!-- What problem do we solve? Try to define the who/what/why of the opportunity as a user story. For example, "As a (who), I want (what), so I can (why/value)." --> ### Intended users * [Sasha (Software Developer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sasha-software-developer) - who is looking at the tests that failed in their current MR on the pipeline page because they don't use MRs. * [Simone (Software Engineer in Test)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#simone-software-engineer-in-test) - who is reviewing failed tests from scheduled builds / an MR from a developer. ### User experience goal <!-- What is the single user experience workflow this problem addresses? For example, "The user should be able to use the UI/API/.gitlab-ci.yml with GitLab to <perform a specific task>" https://about.gitlab.com/handbook/engineering/ux/ux-research-training/user-story-mapping/ --> The user should be able to easily view, select, and share information about failed tests within the gitlab ui. ### Proposal <!-- How are we going to solve the problem? Try to include the user journey! https://about.gitlab.com/handbook/journeys/#user-journey --> One option would be to re-use the existing modal from the Test Summary to display some of this data including the trace. That modal is displayed below. It would need to be augmented with Test History and Filename. The column name should be renamed from `Trace` to `Details` and the column contain a link/button (@v_mishra to help decide) to open the modal.  ### Further details Several new features are being or have been introduced to add functionality to the Unit Test report since it's introduction. This has improved the feature set but decreased the usability of the features unfortunately as the page gets more crowded with information. This only gets worse with [filename](https://gitlab.com/gitlab-org/gitlab/-/issues/119032) and [test history](https://gitlab.com/gitlab-org/gitlab/-/issues/235525) columns being added in addition to sorting the failed tests to the top so trace data is immediately presented. Cleaning up this view so a user can still see the failed tests first but having the data from those tests more easily readable is the ideal outcome for this issue. No matter the approach the [CSS fix](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/41935) implemented to cleanup the scrolling should be removed/un-cleaned up/? <!-- Include use cases, benefits, goals, or any other details that will help us understand the problem better. --> ### Permissions and Security <!-- What permissions are required to perform the described actions? Are they consistent with the existing permissions as documented for users, groups, and projects as appropriate? Is the proposed behavior consistent between the UI, API, and other access methods (e.g. email replies)? Consider adding checkboxes and expectations of users with certain levels of membership https://docs.gitlab.com/ee/user/permissions.html * [ ] Add expected impact to members with no access (0) * [ ] Add expected impact to Guest (10) members * [ ] Add expected impact to Reporter (20) members * [ ] Add expected impact to Developer (30) members * [ ] Add expected impact to Maintainer (40) members * [ ] Add expected impact to Owner (50) members --> ### Documentation <!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/workflow.html#for-a-product-change * Add all known Documentation Requirements in this section. See https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements * If this feature requires changing permissions, update the permissions document. See https://docs.gitlab.com/ee/user/permissions.html --> ### Availability & Testing <!-- This section needs to be retained and filled in during the workflow planning breakdown phase of this feature proposal, if not earlier. What risks does this change pose to our availability? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing? Please list the test areas (unit, integration and end-to-end) that needs to be added or updated to ensure that this feature will work as intended. Please use the list below as guidance. * Unit test changes * Integration test changes * End-to-end test change See the test engineering planning process and reach out to your counterpart Software Engineer in Test for assistance: https://about.gitlab.com/handbook/engineering/quality/test-engineering/#test-planning --> ### What does success look like, and how can we measure that? #### Acceptance Criteria * Given that a pipeline outputs one or more JUnit reports, when one or more of those contains one more ore test failures, then a user on the unit test report page should be able to quickly identify and review information about failed tests (test file location, trace, history, suite and test name, etc.) in a user friendly manner. #### Success metrics * We expect that once [measurement of page views](https://gitlab.com/gitlab-org/gitlab/-/issues/235524) of the unit test report is in place that measure will increase by 20% within 60 days after launch of the feature on gitlab.com <!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. --> ### What is the type of buyer? This is for the individual developer and part of the Core product. ### Is this a cross-stage feature? No. ### Links / references <!-- Label reminders - you should have one of each of the following labels if you can figure out the correct ones -->