Update test skeleton section of writing tests doc

Based on:
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/27603#note_164470061

1 files changed, 2 insertions, 6 deletions

diff --git a/qa/docs/WRITING_TESTS_FROM_SCRATCH.md b/qa/docs/WRITING_TESTS_FROM_SCRATCH.md
index b4642802966..4754b251708 100644
--- a/qa/docs/WRITING_TESTS_FROM_SCRATCH.md
+++ b/qa/docs/WRITING_TESTS_FROM_SCRATCH.md
@@ -41,9 +41,9 @@ Under `.../browser_ui/2_plan/`, let's create a sub-directory called `ee_scoped_l
 
 Inside the newly created sub-directory, let's create a file describing the test suite (e.g. `editing_scoped_labels_spec.rb`.)
 
-#### The `describe` statement
+#### The `context` and `describe` statements
 
-Every test suite starts with a `describe` statement, and it looks like this:
+Specs have an outer `context` that indicates the DevOps stage. The next level is the `describe` statement that briefly states the subject of the tests. See the following example:
 
 ```ruby
 module QA
@@ -54,10 +54,6 @@ module QA
 end
 ```
 
-The `describe` statement receives a string that briefly describes the test suite.
-
-> Note that the test suite is a module from `QA`, and that its `context` is the Plan stage.
-
 #### The `it` statements
 
 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: