summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMark Lapierre <mlapierre@gitlab.com>2019-09-05 04:04:22 +0000
committerMark Lapierre <mlapierre@gitlab.com>2019-09-05 04:04:22 +0000
commitb84292f6c88d7973bbc5b20f75195506029c5e7e (patch)
tree8b2238aed1f832ed8d98cd8e79a6dc7ed52388bb
parent86e1802c0fd37a5b96444558c90689ec04955d0f (diff)
downloadgitlab-ce-docs-qa-prefer-multiple-files.tar.gz
Apply suggestion to doc/development/testing_guide/end_to_end/best_practices.mddocs-qa-prefer-multiple-files
-rw-r--r--doc/development/testing_guide/end_to_end/best_practices.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/testing_guide/end_to_end/best_practices.md b/doc/development/testing_guide/end_to_end/best_practices.md
index 5138b208a7b..2200069ecfd 100644
--- a/doc/development/testing_guide/end_to_end/best_practices.md
+++ b/doc/development/testing_guide/end_to_end/best_practices.md
@@ -43,7 +43,7 @@ Now that we are aware of all of it, [let's go create some tests](quick_start_gui
Our framework includes a couple of parallelization mechanisms that work by executing spec files in parallel.
-However, because tests are parallelized by spec *file* and not by test/example, we can't acheive greater parallelization if a new test is added to an existing file.
+However, because tests are parallelized by spec *file* and not by test/example, we can't achieve greater parallelization if a new test is added to an existing file.
Nonetheless, there could be other reasons to add a new test to an existing file.