## Context This test plan focuses mostly on gaps at the **end-to-end level** of the test pyramid. Check the [documentation](https://docs.gitlab.com/ee/development/testing_guide/end_to_end/#end-to-end-testing) on how we are doing end-to-end testing at GitLab for more context on this set of tests. ### Test gaps This epic tracks the end-to-end coverage effort for the ~"group::configure" to address its test gaps ____ ### End-to-end test coverage | Feature | Covered? | Documentation | Notes | | ------ | ------ | ------ | ------ | | [AutoDevops with Kubernetes Agent on a GKE cluster](https://gitlab.com/gitlab-org/gitlab/-/blob/master/qa/qa/specs/features/browser_ui/7_configure/auto_devops/create_project_with_auto_devops_spec.rb) | :white_check_mark: | [docs](https://docs.gitlab.com/ee/user/clusters/agent/install/) | | | [Deploy a kubernetes manifest file using the Kubernetes Agent](https://gitlab.com/gitlab-org/gitlab/-/blob/master/qa/qa/specs/features/ee/api/7_configure/kubernetes/kubernetes_agent_spec.rb) | :white_check_mark: | | | | | | | | ### :fast_forward: What's Next? Upcoming 3 milestones: * https://gitlab.com/gitlab-org/gitlab/-/issues/378035+ | 15.6 * https://gitlab.com/gitlab-org/gitlab/-/issues/371837+ | 15.6 * https://gitlab.com/gitlab-org/gitlab/-/issues/378034+ | 15.7 * https://gitlab.com/gitlab-org/gitlab/-/issues/371835+ | 15.7 * https://gitlab.com/gitlab-org/gitlab/-/issues/371501+ | 15.8 * https://gitlab.com/gitlab-org/gitlab/-/issues/371838+ | 15.8 This is subject to change due to quad-planning/milestone planning capacity and priorities ____ ### :book: Resources * [Run QA tests against GDK](https://gitlab.com/gitlab-org/gitlab-qa/-/blob/master/docs/run_qa_against_gdk.md) * [Testing Guide - End to End Testing](https://docs.gitlab.com/ee/development/testing_guide/end_to_end/) * [Beginner's Guide to Writing End-to-End tests](https://docs.gitlab.com/ee/development/testing_guide/end_to_end/beginners_guide.html) * [GitLab QA Orchestration tool](https://docs.gitlab.com/ee/development/testing_guide/end_to_end/beginners_guide.html) #### :movie_camera: Recorded sessions * Not yet available ## :raised_back_of_hand: How to Contribute to this Epic New tests can be added through: * **Quad Planning** - Milestone planning with EM/PM/UX to ensure a feature being developed has quality standards and efficient test coverage. Not all new features require end-to-end tests, see [Consider not writing an end-to-end test](https://docs.gitlab.com/ee/development/testing_guide/end_to_end/#consider-not-writing-an-end-to-end-test). Quad planning also should foresee refactorings, deprecations and all changes that could break the existing test suite. * **Test Gap Analysis** - Looking at existing functionality and user flows that are key, complex, and require testing across multiple components, fitting the end-to-end level category and providing that enough unit and component/feature/integration tests have been recommended/added. **Note:** There can be end-to-end issues associated to a feature epic to bring explicit visibility that a test is planned to be delivered as part of that epic. These won't be listed here but the test coverage section should reflect them. :star: [Quality is everyone's responsibility at GitLab.](https://about.gitlab.com/handbook/engineering/quality/#mission) Interested in working on any of the issues in this plan? Great! 1) pick an issue 2) if applicable, follow the ~"group::configure" [planning flow](https://about.gitlab.com/handbook/engineering/development/ops/configure/#milestone-planning-and-timeline) 3) and ping `@svistas` for assistance and code review or the `#quality` Slack channel.