Permalink
Browse files

a little more on the tutorial

  • Loading branch information...
1 parent 7c8269f commit aa52420e0731207c6f90aeb6a1ef3727f5187476 @camd camd committed Mar 30, 2013
@@ -28,8 +28,14 @@ The test case steps executed in test runs may be different for each Product
Version, as the Product itself evolves. See :ref:`Test Cases <test-cases>` for
more info on how test case versions relate to Product Versions.
-An active test run can be disabled, which halts all execution of tests in that
-run until it is made active again.
+.. _test-run-states:
+
+Draft test runs cannot be executed yet. This is a good state if you're still
+working on it and aren't ready for people to see it. It won't show up in the
+list of test runs for your product in the ``Run Tests`` section.
+
+An active test run can be disabled or made draft, which halts all
+execution of tests in that run until it is made active again.
.. _test-run-series:
@@ -72,6 +72,7 @@ Steps
That's one down. Whew! OK, now create another test case for the ``firmware``
suite with steps like this:
+ #. name: ``update firmware``
#. for ``instruction`` 1, enter::
navigate to firmware update screen and select "update"
@@ -28,20 +28,31 @@ steps:
#. navigate to ``manage | environments``
* |manage_environments|
#. click ``create a profile``
- #. give your profile a name
- #. Depending on your setup, you may have several
- :ref:`environment elements<environment-elements>` in your system already.
- #. If you see a category that applies to your product already, then expand
- It to choose the elements that apply. If not, then click |add_category|
- to create a new one
- #. Within a category, if you don't see the correct element, then create
- one by typing in the field |add_element| and hitting enter
- #. Once you have all the categories and elements checked that you want to
- test, click ``save profile``
-
-This will create a matrix list of all possible combinations of the environment
-elements you chose. However, it may be true that you don't want to test ALL
-combinations. If that's the case, then you can winnow down the list to test.
+ #. give your profile the name ``Speck Envs``
+ #. .. note::
+
+ Depending on your setup, you may have several
+ :ref:`environment elements<environment-elements>` in your system already.
+
+ If you see a category that applies to your product already, then expand
+ It to choose the elements that apply. If not, then click |add_category|
+ to create a new one
+ #. In our case, we'll need to create everything, so click |add_category|
+ and type ``location`` and hit enter
+ #. in the category, find the field that says |add_element| and type
+ ``laboratory`` and hit "enter"
+ #. add another element called ``field`` and hit enter
+ #. make sure to check the ``location`` category and all its elements
+ #. click ``save profile``
+
+.. note::
+
+ This will create a matrix list of all possible combinations of the
+ environment elements for each category you chose. In our case it's very
+ simple (only 2). However, for other products, you may have several
+ categories. It may be true that you don't want to test ALL combinations
+ that were created. If that's the case, then you can winnow down the list
+ to test.
To winnow down the list of environments to test:
@@ -43,7 +43,28 @@ Steps
#. click ``save run``
-Isn't this exciting? You now have a test run series created!
+Activate your Run
+-----------------
+
+Your run is just about ready. However, there's one more critical step you
+must take before it can be executed. You must make the run *active*.
+
+Why not have test runs active all the time? Good question.
+:ref:`Look here<test-run-states>`, Curious George.
+
+Steps
+^^^^^
+ #. navigate to ``manage | runs``
+ #. find your test run ``feature complete``
+ #. click the status icon
+ * |run_activate|
+ #. click "Activate"
+
+.. |run_activate| image:: img/run_activate.png
+ :height: 150px
+
+
+Isn't this exciting? You now have a test run series created and ready to go!
Go tell your boss.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
@@ -3,7 +3,65 @@
Moztrap Tutorial, part 4
========================
+You have now built all the parts you need to start testing your product.
+Allons-y! (Let's go!)
+
Start Testing
-------------
-Coming soon!
+There are a few ways to get to your test run to execute it.
+
+Run Tests Steps
+^^^^^^^^^^^^^^^
+ #. navigate to ``run tests``
+ #. in the finder, click ``SpeckDetector``
+ #. click ``1.0``
+ #. click ``feature complete``
+ #. This is a :ref:`run series<test-run-series>` so you will be asked to enter
+ a ``build``. Let's pretend this is your 5th feature complete build.
+ Here type: ``FC-5``
+ #. set ``location`` to ``field``
+ #. click ``run tests in feature complete``
+
+
+Manage Runs Steps
+^^^^^^^^^^^^^^^^^
+ #. navigate to ``manage | runs``
+ #. find the ``feature complete`` run
+ #. expand the arrow on the left to display the details of that run
+ #. click the green button that says ``run tests in feature complete``
+ #. .. note::
+ if you want to send this URL to your testers in an email, then just
+ right-click that same button and select ``copy link location``.
+ #. specify your environment, as above.
+
+"I got a URL!" Steps
+^^^^^^^^^^^^^^^^^^^^
+ #. If somebody gave you a URL to their run or run series, then click on it.
+ #. specify your environment, as above.
+
+Pass a Test
+-----------
+Some tests pass, some fail. This is the way of the world. Let's pass this
+one.
+
+ #. Click the title or expansion arrow of ``update firmware``
+ #. Click ``pass test``
+ #. that was easy
+
+Fail a Test
+-----------
+
+ #. Click the title or expansion arrow of ``Detect a pollen speck``
+ #. Click ``fail test`` next to the first step.
+ #. you must provide some explanation for the failure::
+
+ We applied the cortical electrodes but were unable to get
+ a neural reaction from the pollen speck.
+
+ #. speficying a bug URL is optional, but it's a good idea. I'll leave
+ that up to you.
+
+
+You're done with the run! This is fantastic! If only those kids from High
+School could see you *now!*

0 comments on commit aa52420

Please sign in to comment.