After https://gitlab.com/gitlab-org/quality/quality-engineering/team-tasks/-/issues/2359+, we have come up with a new criteria for E2E tests and are ready to pilot it with a few groups to begin to onboard and gather feedback. ## Implementation From the [previous issue](https://gitlab.com/gitlab-org/quality/quality-engineering/team-tasks/-/issues/2359#note_1881694902 "Defining a criteria on when to write E2E tests"), we've identified the next set of tasks that we will be working with various groups on. * [ ] https://gitlab.com/gitlab-org/quality/quality-engineering/team-tasks/-/issues/2658+ | Reach out to counterpart teams to come up with a list of key workflows based on the different personas. We may start with 1 or 2 groups first and slowly expand that out. Part of this work is figuring out who are the key stakeholders who have knowledge on what these workflows are. It would be great to rank these workflows by importance as not all workflows need to be an E2E test but it is equally important to know what these workflows are since we want to map every level of test to these workflows that can help us monitor that these workflows stay running smoothly. * [ ] https://gitlab.com/gitlab-org/quality/quality-engineering/team-tasks/-/issues/2659+ | From the list of workflows, we can review them and pick out which workflows would be the best candidate as E2E tests. This is factoring in how important a workflow might be but also ensuring these tests exercise the applications various different integrations as well. * [ ] https://gitlab.com/gitlab-org/quality/quality-engineering/team-tasks/-/issues/2660+ | With the shortlisted list of workflows, we can then proceed to reviewing our existing E2E tests and see if we have any of these covered already. This will determine the work that needs to be done to make sure we have E2E tests for these workflows. * [ ] https://gitlab.com/gitlab-org/quality/quality-engineering/team-tasks/-/issues/2661+ | At the same time, for the workflows that didn't make the shortlist, we want the groups to help piece together what Unit or Feature tests that, when grouped together, paints a picture of the health of the workflow (ie. still working, performing well, etc). This can be a lot of work to piece together so maybe we can start with a few first and see if there's any learnings we can take from it to make it easier to do. * [ ] https://gitlab.com/gitlab-org/quality/quality-engineering/team-tasks/-/issues/2662+ | With the test mappings available, we want to start to look into setting up monitoring tools that would be the place to check how these workflows are doing with the different specs linked to it listed out for ease of use. https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/9233+ is also ongoing in parallel which is more focused towards new features and introduction of new E2E tests while this issue is focused on existing features and their associated E2E tests.