@@ -186,6 +186,8 @@ We can monitor test results in the following Slack channels:
* #e2e-run-staging
* #e2e-run-production
For full details of scheduled E2E test pipelines running against live environments see [E2E test pipelines](../../../../testing/end-to-end-pipeline-monitoring#end-to-end-e2e-test-pipelines).
### Running and Fixing E2E specs
#### Prerequisites
@@ -261,6 +263,8 @@ See the [related handbook entry](https://docs.gitlab.com/ee/development/ee_featu
### Troubleshooting common errors and fixes
* For general troubleshooting hints, see [E2E test troubleshooting](https://docs.gitlab.com/development/testing_guide/end_to_end/troubleshooting/).
@@ -325,11 +329,13 @@ For any questions, reach out to [#s_developer_experience](https://gitlab.enterpr
### Resources
*[Testing at GitLab handbook page](../../../../testing)
*[Testing Code in Merge Requests](https://docs.gitlab.com/development/testing_guide/end_to_end/#testing-code-in-merge-requests)
*[Running Govern E2E Specs Locally Against GDK](https://gitlab.com/gitlab-org/gitlab/-/tree/master/qa?ref_type=heads#generic-command-for-a-typical-gdk-installation)
*[Automatic test execution when a feature flag definition changes](https://docs.gitlab.com/development/testing_guide/end_to_end/best_practices/feature_flags/#automatic-test-execution-when-a-feature-flag-definition-changes)
*[End-to-end test pipelines](https://docs.gitlab.com/development/testing_guide/end_to_end/test_pipelines/)
*[GitLab team member's guide to using official build infrastructure](https://docs.gitlab.com/omnibus/build/team_member_docs/)
