Commit 1117ce24 authored by Ray Paik's avatar Ray Paik Committed by Dan Davison

Add a subsection on not writing end-to-end test

parent 28947114
...@@ -178,6 +178,13 @@ Once you decided where to put [test environment orchestration scenarios](https:/ ...@@ -178,6 +178,13 @@ Once you decided where to put [test environment orchestration scenarios](https:/
the [GitLab QA orchestrator README](https://gitlab.com/gitlab-org/gitlab-qa/tree/master/README.md), and [the already existing the [GitLab QA orchestrator README](https://gitlab.com/gitlab-org/gitlab-qa/tree/master/README.md), and [the already existing
instance-level scenarios](https://gitlab.com/gitlab-org/gitlab-foss/tree/master/qa/qa/specs/features). instance-level scenarios](https://gitlab.com/gitlab-org/gitlab-foss/tree/master/qa/qa/specs/features).
### Consider **not** writing an end-to-end test
We should follow these best practices for end-to-end tests:
- Do not write an end-to-end test if a lower-level feature test exists. End-to-end tests require more work and resources.
- Troubleshooting for end-to-end tests can be more complex as connections to the application under test are not known.
Continued reading: Continued reading:
- [Beginner's Guide](beginners_guide.md) - [Beginner's Guide](beginners_guide.md)
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment