## Problem to Solve By automating the creation of issues, the QA team has been piloting the relationship of [test session reports](https://gitlab.com/gitlab-org/quality/testcase-sessions/-/issues?page=3&state=opened) and [test cases](https://gitlab.com/gitlab-org/quality/testcases/-/issues). While this may solve the problem in the interim, this solution does not scale for others to replicate. ## JTBD When there is a release, release managers and quality engineers want to see what was tested with this change, so that they can collaborate on the release by reviewing the testing performed. ## Proposal **Create a dedicated Test Sessions Page and incorporate linkages** - Reuse the same architecture and base layout functionality of `test cases` for the foundation of `test sessions`. - Add a field to select a `pipeline id` to create a link within a test session - Add the `linked issues` component to associate Test Sessions and Test Cases. |Test Session Report List (Current)|Test Session Report List (Proposed)| |---|---| ||| |Test Session Report (Current)|Test Session Report (Proposed)| |---|---| ||| |Creating a Test Session|Test Cases with Linked Test Session| |---|---| ||| ## Out of scope **Test Sessions** - Creation of Test Sessions from a ["Test Plan" or Scenario](https://gitlab.com/gitlab-org/gitlab/-/issues/233520#note_471063341) - Duplication of Test Sessions to reduce copy/pasting effort **Test Cases** - Showing [how test results are displayed](https://gitlab.com/gitlab-org/gitlab/-/issues/233520#note_453157051), because each test case will have multiple test results. - Incorporate the [test report feature](https://docs.gitlab.com/ee/ci/unit_test_reports.html#viewing-unit-test-reports-on-gitlab) which includes [screenshots and errors](https://gitlab.com/groups/gitlab-org/-/epics/3197). ## Resources [See Figma →](https://www.figma.com/file/4ScW5cvx21mQwlHVVa0QKc/Quality-Management?node-id=320%3A0)