diff options
| author | Walmyr <walmyr@gitlab.com> | 2019-04-25 14:36:20 +0000 |
|---|---|---|
| committer | Walmyr Lima <walmyr@gitlab.com> | 2019-05-10 15:07:21 -0500 |
| commit | df0497ebc8c5efd0fc4343e11bcabb01315984fc (patch) | |
| tree | d0b3d0ece44127342d423b898f951e60502cadc9 | |
| parent | 971184971233f2b4176b1e9f13b42cc2784ab03f (diff) | |
| download | gitlab-ce-df0497ebc8c5efd0fc4343e11bcabb01315984fc.tar.gz | |
Apply suggestion to qa/docs/WRITING_TESTS_FROM_SCRATCH.md
| -rw-r--r-- | qa/docs/WRITING_TESTS_FROM_SCRATCH.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/qa/docs/WRITING_TESTS_FROM_SCRATCH.md b/qa/docs/WRITING_TESTS_FROM_SCRATCH.md index 5c910de5137..37d83578a91 100644 --- a/qa/docs/WRITING_TESTS_FROM_SCRATCH.md +++ b/qa/docs/WRITING_TESTS_FROM_SCRATCH.md @@ -94,7 +94,7 @@ The `describe` statement receives a string that briefly describes the test suite #### The `it` statements -Every test suite is composed by at least one `it` statement, and a good way to start writing _e2e_ tests is by typing test cases descriptions as `it` statements. Take a look at the below example: +Every test suite is composed by at least one `it` statement, and a good way to start writing end-to-end tests is by typing test cases descriptions as `it` statements. Take a look at the following example: ```ruby module QA |