rework the test documentation
-Testing image
-=============
+Testing images
+==============
-Concreate is able to run `behave <https://pythonhosted.org/behave/>`_ based test for the image. We suggest to read behave documentation before reading this chapter.
+Concreate is able to run `behave <https://pythonhosted.org/behave/>`_ based
+test for images. We suggest you read the Behave documentation before reading
+this chapter.
-Image can be tested by running:
+An image can be tested by running:
.. code:: bash
@@ -11,37 +13,46 @@ Image can be tested by running:
**Test options**
-* ``--test-wip`` -- run only tests tagged with ``@wip`` tag.
+* ``--test-wip`` -- only run tests tagged with the ``@wip`` tag.
* ``--test-steps-url`` -- a git repository url containing `steps <https://pythonhosted.org/behave/tutorial.html#python-step-implementations>`_ for tests.
-* ``--tag`` -- an image tag used to determine image which will be tests. It can be specified multiple times but only the first occurence is honored.
+* ``--tag`` -- only run tests tagged with the supplied tag. Only the
+ first occurence of this argument is honoured.
About Tests
-----------
-Behave tests are separate to two parts steps and features. You can place tests in ``tests`` directory next
-to the image descriptor, module descriptor or in a root of a git repository which contains the modules.
-The tests directory is structured in following way:
+Behave tests are defined in two separate parts: steps and features.
+
+You can place the files defining tests in a ``tests`` directory next to the
+image descriptor, module descriptor or in a root of a git repository which
+contains the modules.
+
+The tests directory is structured as follows:
.. code::
tests/features
- tests/features/amq.features
+ tests/features/amq.feature
tests/steps
tests/steps/custom_steps.py
-The ``tests/features`` directory is the place where you can drop your custom developed `behave features. <https://pythonhosted.org/behave/gherkin.html>`_
+The ``tests/features`` directory is the place where you can drop your `behave features. <https://pythonhosted.org/behave/gherkin.html>`_
The ``tests/steps`` directory is optional and contains custom `steps <https://pythonhosted.org/behave/tutorial.html#python-step-implementations>`_ for specific image/module.
We strongly recommend that a test is written for every feature that is added to the image.
-For the list of steps that are available for use in tests, see the `steps repository <https://github.com/jboss-openshift/concreate-test-steps>`_.
-Where necessary we encourage people to add or extend the steps.
+
+Concreate comes with a list of build-in steps that are available for use in
+tests. See the `steps repository <https://github.com/jboss-openshift/concreate-test-steps>`_.
+
+Where necessary we encourage people to add or extend these steps.
**Tags**
-Concreate is selecting which test to run via tags mechanism. There are two way the tags are used:
+Concreate selects which tests to run via the *tags* mechanism. There are two
+way that tags are used:
1. `Product tags`
