Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

a little more on the tutorial

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

0 notes on commit aa52420

Please sign in to comment.
Something went wrong with that request. Please try again.