[robotframework] 3 new revisions pushed by pekka.klarck on 2013-05-31 10:58 GMT

[robotframework]

3 new revisions:

Revision: a17f2f024496
Branch:   default
Author:   Pekka Klärck
Date:     Fri May 31 03:57:13 2013
Log:      UG: Updated docs related deprecated --runmode and new options  
that rep...
http://code.google.com/p/robotframework/source/detail?r=a17f2f024496
Revision: 28aa094b5ba3
Branch:   default
Author:   Pekka Klärck
Date:     Fri May 31 03:57:53 2013
Log:      Automated merge with https://code.google.com/p/robotframework/
http://code.google.com/p/robotframework/source/detail?r=28aa094b5ba3

Revision: cbb70a6ec447
Branch:   default
Author:   Pekka Klärck
Date:     Fri May 31 03:58:02 2013
Log:      regen
http://code.google.com/p/robotframework/source/detail?r=cbb70a6ec447

==============================================================================
Revision: a17f2f024496
Branch:   default
Author:   Pekka Klärck
Date:     Fri May 31 03:57:13 2013
Log:      UG: Updated docs related deprecated --runmode and new options  
that replace it.
http://code.google.com/p/robotframework/source/detail?r=a17f2f024496

Modified:
 /doc/userguide/src/Appendices/CommandLineOptions.rst
 /doc/userguide/src/ExecutingTestCases/ConfiguringExecution.rst
 /doc/userguide/src/ExecutingTestCases/TestExecution.rst

=======================================
--- /doc/userguide/src/Appendices/CommandLineOptions.rst	Wed May 29  
05:51:32 2013
+++ /doc/userguide/src/Appendices/CommandLineOptions.rst	Fri May 31  
03:57:13 2013
@@ -31,8 +31,8 @@
   -o, --output <file>     Sets the path to the generated `output file`_.
   -l, --log <file>        Sets the path to the generated `log file`_.
   -r, --report <file>     Sets the path to the generated `report file`_.
-  -x, --xunitfile <file>  Sets the path to the generated `XUnit compatible  
result file`_.
-  --xunitskipnoncritical  Mark non-critical tests on `XUnit compatible  
result file`_ as skipped.
+  -x, --xunitfile <file>  Sets the path to the generated `xUnit compatible  
result file`_.
+  --xunitskipnoncritical  Mark non-critical tests on `xUnit compatible  
result file`_ as skipped.
   -b, --debugfile <file>  A `debug file`_ that is written during execution.
   -T, --timestampoutputs  `Adds a timestamp`_ to all output files.
   --splitlog              `Split log file`_ into smaller pieces that open  
in
@@ -59,18 +59,17 @@
   --warnonskippedfiles    Show a warning when `an invalid file is  
skipped`_.
   --nostatusrc            Sets the `return code`_ to zero regardless of  
failures
                           in test cases. Error codes are returned normally.
-  --runemptysuite         Executes tests also if the top level `test suite  
is
-                          empty`_.
-  --dryrun                When `dry run`_, keywords coming from the test
-                          libraries are not executed at all.
+  --runemptysuite         Executes tests also if the selected `test suites  
are empty`_.
+  --dryrun                In the `dry run`_ mode tests are run without  
executing
+                          keywords originating from test libraries. Useful  
for
+                          validating test data syntax.
   --exitonfailure         `Stops execution`_ immediately if a critical  
test fails.
-  --skipteardownonexit    `Skips teardowns`_ when the execution is stopped.
-  --randomize <what>      `Randomizes the test execution order`_.
-  --runmode <mode>        Deprecated in Robot Framework 2.8, please use the
-                          the respective options above.
-                          Sets the execution mode for this test run.
-                          Valid modes are `ExitOnFailure`_,  
`SkipTeardownOnExit`_,
-                          `DryRun`_, and `Random`_:<what>.
+  --skipteardownonexit    `Skips teardowns`_ is test execution is  
prematurely stopped.
+  --randomize <all|suites|tests|none>  `Randomizes`_ test execution order.
+  --runmode <mode>        Deprecated in Robot Framework 2.8. Use separate
+                          :opt:`--dryrun`, :opt:`--exitonfailure`,
+                          :opt:`--skipteardownonexit`  
and :opt:`--randomize`
+                          options instead.
   -W, --monitorwidth <chars>  `Sets the width`_ of the console output.
   -C, --monitorcolors <on|off|force>  `Specifies are colors`_ used on the  
console.
   -K, --monitormarkers <on|off|force>  Specifies are `console markers`_
@@ -98,8 +97,8 @@
   -o, --output <file>     Sets the path to the generated `output file`_.
   -l, --log <file>        Sets the path to the generated `log file`_.
   -r, --report <file>     Sets the path to the generated `report file`_.
-  -x, --xunitfile <file>  Sets the path to the generated `XUnit compatible  
result file`_.
-  --xunitskipnoncritical  Mark non-critical tests on `XUnit compatible  
result file`_ as skipped.
+  -x, --xunitfile <file>  Sets the path to the generated `xUnit compatible  
result file`_.
+  --xunitskipnoncritical  Mark non-critical tests on `xUnit compatible  
result file`_ as skipped.
   -T, --timestampoutputs  `Adds a timestamp`_ to all output files.
   --splitlog              `Split log file`_ into smaller pieces that open  
in
                           browser transparently.
@@ -126,8 +125,8 @@
   --endtime <timestamp>   Sets the `ending time`_ of test execution when  
creating reports.
   --nostatusrc            Sets the `return code`_ to zero regardless of  
failures
                           in test cases. Error codes are returned normally.
-  --processemptysuite     Processes an output file even if the top level  
`test suite is
-                          empty`_.
+  --processemptysuite     Processes output files even if files contain
+                          `empty test suites`_.
   -E, --escape <what:with>  `Escapes characters`_ that are problematic in  
the console.
   -A, --argumentfile <path>   A text file to `read more arguments`_ from.
   -h, --help              Prints `usage instructions`_.
@@ -145,13 +144,11 @@
 .. _considered critical: `Setting criticality`_
 .. _not critical: `considered critical`_
 .. _ContinueOnFailure: `Continue on failure`_
-.. _Stops execution: `ExitOnFailure mode`_
-.. _ExitOnFailure: `ExitOnFailure mode`_
+.. _Stops execution: `Stopping when first test case fails`_
 .. _Skips teardowns: `Handling Teardowns`_
 .. _SkipTeardownOnExit: `Handling Teardowns`_
 .. _DryRun: `Dry run`_
-.. _Randomizes the test execution order: `Randomizing execution order`_
-.. _Random: `Randomizing execution order`_
+.. _Randomizes: `Randomizing execution order`_
 .. _individual variables: `Setting variables in command line`_

 .. _create output files: `Output directory`_
@@ -170,7 +167,8 @@

 .. _Sets a listener: `Setting listeners`_
 .. _an invalid file is skipped: `Warning on invalid files`_
-.. _test suite is empty: `When no tests match selection`_
+.. _test suites are empty: `When no tests match selection`_
+.. _empty test suites: `test suites are empty`_
 .. _Sets the width: `Console width`_
 .. _Specifies are colors: `Console colors`_
 .. _search test libraries: `library search path`_
=======================================
--- /doc/userguide/src/ExecutingTestCases/ConfiguringExecution.rst	Wed May  
29 05:51:32 2013
+++ /doc/userguide/src/ExecutingTestCases/ConfiguringExecution.rst	Fri May  
31 03:57:13 2013
@@ -358,14 +358,7 @@
 run normally otherwise, but the keywords coming from the test libraries
 are not executed at all. The dry run mode can be used to validate the
 test data; if the dry run passes, the data should be syntactically
-correct. This mode is triggered using option :opt:`--dryrun`
-(case-insensitive) and supported starting from Robot Framework 2.8.
-
-.. note:: Prior to Robot Framework 2.8, dry run mode is triggered using
-          option :opt:`--runmode dryrun` (case-insensitive).
-
-          Option :opt:`--runmode` is deprecated in 2.8 and will be removed
-          in the future.
+correct. This mode is triggered using option :opt:`--dryrun`.

 The dry run execution may fail for following reasons:

@@ -380,6 +373,10 @@
 .. note:: The dry run mode does not validate variables. This
           limitation may be lifted in the future releases.

+.. note:: Prior to Robot Framework 2.8, the dry run mode was activate using
+          option :opt:`--runmode dryrun`. Option :opt:`--runmode` was
+          deprecated in 2.8 and will be removed in the future.
+
 __ `Errors and warnings during execution`_

 Randomizing execution order
@@ -411,8 +408,8 @@

 .. note:: Prior to Robot Framework 2.8, randomization is triggered using  
option
           :opt:`--runmode <mode>`, where <mode> is  
either :opt:`Random:Test`,
-          :opt:`Random:Suite` or :opt:`Random:All`.
-          These values work respectively as with option :opt:`--randomize`.
+          :opt:`Random:Suite` or :opt:`Random:All`. These values work the
+          same way as matching values for :opt:`--randomize`.

           Option :opt:`--runmode` is deprecated in 2.8 and will be removed
           in the future.
=======================================
--- /doc/userguide/src/ExecutingTestCases/TestExecution.rst	Wed May 29  
05:51:32 2013
+++ /doc/userguide/src/ExecutingTestCases/TestExecution.rst	Fri May 31  
03:57:13 2013
@@ -250,8 +250,7 @@
 to accomplish this are explained below. In all these cases the remaining
 test cases are marked failed.

-.. Note:: Most of these features are new in Robot Framework 2.5. Only
-          the `ExitOnFailure mode`_ is supported in earlier versions.
+.. Note:: Most of these features are new in Robot Framework 2.5.

 Pressing :code:`Ctrl-C`
 '''''''''''''''''''''''
@@ -284,35 +283,29 @@

 __ `Stopping test execution`_

-:opt:`ExitOnFailure` mode
-'''''''''''''''''''''''''
+Stopping when first test case fails
+'''''''''''''''''''''''''''''''''''

-If option :opt:`--exitonfailure` (case-insensitive) is used, the execution  
of
-tests stops immediately if a `critical test`_ fails. Also the remaining  
tests
+If option :opt:`--exitonfailure` is used, test execution stops
+immediately if any `critical test`_ fails. Also the remaining tests
 are marked as failed.

-.. Note:: Prior to Robot Framework 2.8, this behaviour is achieved by
-          using :opt:`--runmode ExitOnFailure` (case-insensitive).
-
-          Option :opt:`--runmode` is deprecated in 2.8 and will be removed
-          in the future.
-
+.. note:: Prior to Robot Framework 2.8, this behaviour was achieved by
+          using :opt:`--runmode exitonfailure`. Option :opt:`--runmode`
+          was deprecated in 2.8 and will be removed in the future.

 Handling teardowns
 ''''''''''''''''''

-By default teardowns for tests and suites that have been started are  
executed
-even if test execution is stopped using one of the methods above. This  
allows
-clean-up activities to be run regardless how execution ends.
-
-Starting from Robot Framework 2.8, teardowns are skipped when the  
execution is
-stopped and command line option :opt:`--SkipTeardownOnExit`  
(case-insensitive)
-is used.
-
-This can be useful if clean-up takes a lot of time.
+By default teardowns of the tests and suites that have been started are
+executed even if the test execution is stopped using one of the methods
+above. This allows clean-up activities to be run regardless how execution
+ends.

-.. Note:: Prior to Robot Framework 2.8, this behaviour is achieved by
-          using :opt:`--runmode SkipTearDownOnExit` (case-insensitive).
+It is also possible to skip teardowns when execution is stopped by using
+:opt:`--skipteardownonexit` option. This can be useful if, for example,
+clean-up tasks take a lot of time.

-          Option :opt:`--runmode` is deprecated in 2.8 and will be removed
-          in the future.
+.. note:: Prior to Robot Framework 2.8, this behaviour was achieved by
+          using :opt:`--runmode skipteardownonexit`.  
Option :opt:`--runmode`
+          was deprecated in 2.8 and will be removed in the future.

==============================================================================
Revision: 28aa094b5ba3
Branch:   default
Author:   Pekka Klärck
Date:     Fri May 31 03:57:53 2013
Log:      Automated merge with https://code.google.com/p/robotframework/
http://code.google.com/p/robotframework/source/detail?r=28aa094b5ba3

Modified:
 /doc/userguide/src/Appendices/CommandLineOptions.rst

=======================================
--- /doc/userguide/src/Appendices/CommandLineOptions.rst	Fri May 31  
02:34:18 2013
+++ /doc/userguide/src/Appendices/CommandLineOptions.rst	Fri May 31  
03:57:53 2013
@@ -31,8 +31,8 @@
   -o, --output <file>     Sets the path to the generated `output file`_.
   -l, --log <file>        Sets the path to the generated `log file`_.
   -r, --report <file>     Sets the path to the generated `report file`_.
-  -x, --xunitfile <file>  Sets the path to the generated `XUnit compatible  
result file`_.
-  --xunitskipnoncritical  Mark non-critical tests on `XUnit compatible  
result file`_ as skipped.
+  -x, --xunitfile <file>  Sets the path to the generated `xUnit compatible  
result file`_.
+  --xunitskipnoncritical  Mark non-critical tests on `xUnit compatible  
result file`_ as skipped.
   -b, --debugfile <file>  A `debug file`_ that is written during execution.
   -T, --timestampoutputs  `Adds a timestamp`_ to all output files.
   --splitlog              `Split log file`_ into smaller pieces that open  
in
@@ -59,18 +59,17 @@
   --warnonskippedfiles    Show a warning when `an invalid file is  
skipped`_.
   --nostatusrc            Sets the `return code`_ to zero regardless of  
failures
                           in test cases. Error codes are returned normally.
-  --runemptysuite         Executes tests also if the top level `test suite  
is
-                          empty`_.
-  --dryrun                When `dry run`_, keywords coming from the test
-                          libraries are not executed at all.
+  --runemptysuite         Executes tests also if the selected `test suites  
are empty`_.
+  --dryrun                In the `dry run`_ mode tests are run without  
executing
+                          keywords originating from test libraries. Useful  
for
+                          validating test data syntax.
   --exitonfailure         `Stops execution`_ immediately if a critical  
test fails.
-  --skipteardownonexit    `Skips teardowns`_ when the execution is stopped.
-  --randomize <what>      `Randomizes the test execution order`_.
-  --runmode <mode>        Deprecated in Robot Framework 2.8, please use the
-                          the respective options above.
-                          Sets the execution mode for this test run.
-                          Valid modes are `ExitOnFailure`_,  
`SkipTeardownOnExit`_,
-                          `DryRun`_, and `Random`_:<what>.
+  --skipteardownonexit    `Skips teardowns`_ is test execution is  
prematurely stopped.
+  --randomize <all|suites|tests|none>  `Randomizes`_ test execution order.
+  --runmode <mode>        Deprecated in Robot Framework 2.8. Use separate
+                          :opt:`--dryrun`, :opt:`--exitonfailure`,
+                          :opt:`--skipteardownonexit`  
and :opt:`--randomize`
+                          options instead.
   -W, --monitorwidth <chars>  `Sets the width`_ of the console output.
   -C, --monitorcolors <on|off|force>  `Specifies are colors`_ used on the  
console.
   -K, --monitormarkers <on|off|force>  Specifies are `console markers`_
@@ -98,8 +97,8 @@
   -o, --output <file>     Sets the path to the generated `output file`_.
   -l, --log <file>        Sets the path to the generated `log file`_.
   -r, --report <file>     Sets the path to the generated `report file`_.
-  -x, --xunitfile <file>  Sets the path to the generated `XUnit compatible  
result file`_.
-  --xunitskipnoncritical  Mark non-critical tests on `XUnit compatible  
result file`_ as skipped.
+  -x, --xunitfile <file>  Sets the path to the generated `xUnit compatible  
result file`_.
+  --xunitskipnoncritical  Mark non-critical tests on `xUnit compatible  
result file`_ as skipped.
   -T, --timestampoutputs  `Adds a timestamp`_ to all output files.
   --splitlog              `Split log file`_ into smaller pieces that open  
in
                           browser transparently.
@@ -125,8 +124,8 @@
   --endtime <timestamp>   Sets the `ending time`_ of test execution when  
creating reports.
   --nostatusrc            Sets the `return code`_ to zero regardless of  
failures
                           in test cases. Error codes are returned normally.
-  --processemptysuite     Processes an output file even if the top level  
`test suite is
-                          empty`_.
+  --processemptysuite     Processes output files even if files contain
+                          `empty test suites`_.
   -E, --escape <what:with>  `Escapes characters`_ that are problematic in  
the console.
   -A, --argumentfile <path>   A text file to `read more arguments`_ from.
   -h, --help              Prints `usage instructions`_.
@@ -144,13 +143,11 @@
 .. _considered critical: `Setting criticality`_
 .. _not critical: `considered critical`_
 .. _ContinueOnFailure: `Continue on failure`_
-.. _Stops execution: `ExitOnFailure mode`_
-.. _ExitOnFailure: `ExitOnFailure mode`_
+.. _Stops execution: `Stopping when first test case fails`_
 .. _Skips teardowns: `Handling Teardowns`_
 .. _SkipTeardownOnExit: `Handling Teardowns`_
 .. _DryRun: `Dry run`_
-.. _Randomizes the test execution order: `Randomizing execution order`_
-.. _Random: `Randomizing execution order`_
+.. _Randomizes: `Randomizing execution order`_
 .. _individual variables: `Setting variables in command line`_

 .. _create output files: `Output directory`_
@@ -169,7 +166,8 @@

 .. _Sets a listener: `Setting listeners`_
 .. _an invalid file is skipped: `Warning on invalid files`_
-.. _test suite is empty: `When no tests match selection`_
+.. _test suites are empty: `When no tests match selection`_
+.. _empty test suites: `test suites are empty`_
 .. _Sets the width: `Console width`_
 .. _Specifies are colors: `Console colors`_
 .. _search test libraries: `library search path`_

==============================================================================
Revision: cbb70a6ec447
Branch:   default
Author:   Pekka Klärck
Date:     Fri May 31 03:58:02 2013
Log:      regen
http://code.google.com/p/robotframework/source/detail?r=cbb70a6ec447

Modified:
 /doc/userguide/RobotFrameworkUserGuide.html

=======================================
--- /doc/userguide/RobotFrameworkUserGuide.html Fri May 31 02:35:24 2013
+++ /doc/userguide/RobotFrameworkUserGuide.html Fri May 31 03:58:02 2013
@@ -10517,7 +10517,7 @@
 <li><a class="reference internal" href="#pressing-ctrl-c"  
id="id562">Pressing <span class="code">Ctrl-C</span></a></li>
 <li><a class="reference internal" href="#using-signals" id="id563">Using  
signals</a></li>
 <li><a class="reference internal" href="#using-keywords" id="id564">Using  
keywords</a></li>
-<li><a class="reference internal" href="#exitonfailure-mode"  
id="id565"><span class="opt">ExitOnFailure</span> mode</a></li>
+<li><a class="reference internal"  
href="#stopping-when-first-test-case-fails" id="id565">Stopping when first  
test case fails</a></li>
 <li><a class="reference internal" href="#handling-teardowns"  
id="id566">Handling teardowns</a></li>
 </ul>
 </li>
@@ -10715,8 +10715,7 @@
 test cases are marked failed.</p>
 <div class="note">
 <p class="first admonition-title">Note</p>
-<p class="last">Most of these features are new in Robot Framework 2.5. Only
-the <a class="reference internal" href="#exitonfailure-mode">ExitOnFailure  
mode</a> is supported in earlier versions.</p>
+<p class="last">Most of these features are new in Robot Framework 2.5.</p>
 </div>
 <div class="section" id="pressing-ctrl-c">
 <h4><a class="toc-backref" href="#id562">Pressing <span  
class="code">Ctrl-C</span></a></h4>
@@ -10742,34 +10741,32 @@
 separate <span class="name">Fatal Error</span> <a class="reference  
internal" href="#builtin-library">BuiltIn keyword</a> for this purpose, and
 custom keywords can use <a class="reference internal"  
href="#stopping-test-execution">fatal exceptions</a> when they fail.</p>
 </div>
-<div class="section" id="exitonfailure-mode">
-<h4><a class="toc-backref" href="#id565"><span  
class="opt">ExitOnFailure</span> mode</a></h4>
-<p>If option <span class="opt">--exitonfailure</span> (case-insensitive)  
is used, the execution of
-tests stops immediately if a <a class="reference internal"  
href="#setting-criticality">critical test</a> fails. Also the remaining  
tests
+<div class="section" id="stopping-when-first-test-case-fails">
+<h4><a class="toc-backref" href="#id565">Stopping when first test case  
fails</a></h4>
+<p>If option <span class="opt">--exitonfailure</span> is used, test  
execution stops
+immediately if any <a class="reference internal"  
href="#setting-criticality">critical test</a> fails. Also the remaining  
tests
 are marked as failed.</p>
 <div class="note">
 <p class="first admonition-title">Note</p>
-<p>Prior to Robot Framework 2.8, this behaviour is achieved by
-using <span class="opt">--runmode ExitOnFailure</span>  
(case-insensitive).</p>
-<p class="last">Option <span class="opt">--runmode</span> is deprecated in  
2.8 and will be removed
-in the future.</p>
+<p class="last">Prior to Robot Framework 2.8, this behaviour was achieved  
by
+using <span class="opt">--runmode exitonfailure</span>. Option <span  
class="opt">--runmode</span>
+was deprecated in 2.8 and will be removed in the future.</p>
 </div>
 </div>
 <div class="section" id="handling-teardowns">
 <h4><a class="toc-backref" href="#id566">Handling teardowns</a></h4>
-<p>By default teardowns for tests and suites that have been started are  
executed
-even if test execution is stopped using one of the methods above. This  
allows
-clean-up activities to be run regardless how execution ends.</p>
-<p>Starting from Robot Framework 2.8, teardowns are skipped when the  
execution is
-stopped and command line option <span  
class="opt">--SkipTeardownOnExit</span> (case-insensitive)
-is used.</p>
-<p>This can be useful if clean-up takes a lot of time.</p>
+<p>By default teardowns of the tests and suites that have been started are
+executed even if the test execution is stopped using one of the methods
+above. This allows clean-up activities to be run regardless how execution
+ends.</p>
+<p>It is also possible to skip teardowns when execution is stopped by using
+<span class="opt">--skipteardownonexit</span> option. This can be useful  
if, for example,
+clean-up tasks take a lot of time.</p>
 <div class="note">
 <p class="first admonition-title">Note</p>
-<p>Prior to Robot Framework 2.8, this behaviour is achieved by
-using <span class="opt">--runmode SkipTearDownOnExit</span>  
(case-insensitive).</p>
-<p class="last">Option <span class="opt">--runmode</span> is deprecated in  
2.8 and will be removed
-in the future.</p>
+<p class="last">Prior to Robot Framework 2.8, this behaviour was achieved  
by
+using <span class="opt">--runmode skipteardownonexit</span>. Option <span  
class="opt">--runmode</span>
+was deprecated in 2.8 and will be removed in the future.</p>
 </div>
 </div>
 </div>
@@ -11213,15 +11210,7 @@
 run normally otherwise, but the keywords coming from the test libraries
 are not executed at all. The dry run mode can be used to validate the
 test data; if the dry run passes, the data should be syntactically
-correct. This mode is triggered using option <span  
class="opt">--dryrun</span>
-(case-insensitive) and supported starting from Robot Framework 2.8.</p>
-<div class="note">
-<p class="first admonition-title">Note</p>
-<p>Prior to Robot Framework 2.8, dry run mode is triggered using
-option <span class="opt">--runmode dryrun</span> (case-insensitive).</p>
-<p class="last">Option <span class="opt">--runmode</span> is deprecated in  
2.8 and will be removed
-in the future.</p>
-</div>
+correct. This mode is triggered using option <span  
class="opt">--dryrun</span>.</p>
 <p>The dry run execution may fail for following reasons:</p>
 <blockquote>
 <ul class="simple">
@@ -11238,6 +11227,12 @@
 <p class="last">The dry run mode does not validate variables. This
 limitation may be lifted in the future releases.</p>
 </div>
+<div class="note">
+<p class="first admonition-title">Note</p>
+<p class="last">Prior to Robot Framework 2.8, the dry run mode was  
activate using
+option <span class="opt">--runmode dryrun</span>. Option <span  
class="opt">--runmode</span> was
+deprecated in 2.8 and will be removed in the future.</p>
+</div>
 </div>
 <div class="section" id="randomizing-execution-order">
 <h3><a class="toc-backref"  
href="#id591">3.4.7&nbsp;&nbsp;&nbsp;Randomizing execution order</a></h3>
@@ -11264,8 +11259,8 @@
 <p class="first admonition-title">Note</p>
 <p>Prior to Robot Framework 2.8, randomization is triggered using option
 <span class="opt">--runmode &lt;mode&gt;</span>, where &lt;mode&gt; is  
either <span class="opt">Random:Test</span>,
-<span class="opt">Random:Suite</span> or <span  
class="opt">Random:All</span>.
-These values work respectively as with option <span  
class="opt">--randomize</span>.</p>
+<span class="opt">Random:Suite</span> or <span  
class="opt">Random:All</span>. These values work the
+same way as matching values for <span class="opt">--randomize</span>.</p>
 <p class="last">Option <span class="opt">--runmode</span> is deprecated in  
2.8 and will be removed
 in the future.</p>
 </div>
@@ -16098,11 +16093,11 @@
 <tr><td class="option-group" colspan="2">
 <kbd><span class="option">-x</span>, <span class="option">--xunitfile  
<var>&lt;file&gt;</var></span></kbd></td>
 </tr>
-<tr><td>&nbsp;</td><td>Sets the path to the generated <a class="reference  
internal" href="#xunit-compatible-result-file">XUnit compatible result  
file</a>.</td></tr>
+<tr><td>&nbsp;</td><td>Sets the path to the generated <a class="reference  
internal" href="#xunit-compatible-result-file">xUnit compatible result  
file</a>.</td></tr>
 <tr><td class="option-group" colspan="2">
 <kbd><span class="option">--xunitskipnoncritical</span></kbd></td>
 </tr>
-<tr><td>&nbsp;</td><td>Mark non-critical tests on <a class="reference  
internal" href="#xunit-compatible-result-file">XUnit compatible result  
file</a> as skipped.</td></tr>
+<tr><td>&nbsp;</td><td>Mark non-critical tests on <a class="reference  
internal" href="#xunit-compatible-result-file">xUnit compatible result  
file</a> as skipped.</td></tr>
 <tr><td class="option-group" colspan="2">
 <kbd><span class="option">-b</span>, <span class="option">--debugfile  
<var>&lt;file&gt;</var></span></kbd></td>
 </tr>
@@ -16181,32 +16176,31 @@
 <tr><td class="option-group" colspan="2">
 <kbd><span class="option">--runemptysuite</span></kbd></td>
 </tr>
-<tr><td>&nbsp;</td><td>Executes tests also if the top level <a  
class="reference internal" href="#when-no-tests-match-selection">test suite  
is
-empty</a>.</td></tr>
+<tr><td>&nbsp;</td><td>Executes tests also if the selected <a  
class="reference internal" href="#when-no-tests-match-selection">test  
suites are empty</a>.</td></tr>
 <tr><td class="option-group">
 <kbd><span class="option">--dryrun</span></kbd></td>
-<td>When <a class="reference internal" href="#dry-run">dry run</a>,  
keywords coming from the test
-libraries are not executed at all.</td></tr>
+<td>In the <a class="reference internal" href="#dry-run">dry run</a> mode  
tests are run without executing
+keywords originating from test libraries. Useful for
+validating test data syntax.</td></tr>
 <tr><td class="option-group" colspan="2">
 <kbd><span class="option">--exitonfailure</span></kbd></td>
 </tr>
-<tr><td>&nbsp;</td><td><a class="reference internal"  
href="#exitonfailure-mode">Stops execution</a> immediately if a critical  
test fails.</td></tr>
+<tr><td>&nbsp;</td><td><a class="reference internal"  
href="#stopping-when-first-test-case-fails">Stops execution</a> immediately  
if a critical test fails.</td></tr>
 <tr><td class="option-group" colspan="2">
 <kbd><span class="option">--skipteardownonexit</span></kbd></td>
 </tr>
-<tr><td>&nbsp;</td><td><a class="reference internal"  
href="#handling-teardowns">Skips teardowns</a> when the execution is  
stopped.</td></tr>
+<tr><td>&nbsp;</td><td><a class="reference internal"  
href="#handling-teardowns">Skips teardowns</a> is test execution is  
prematurely stopped.</td></tr>
 <tr><td class="option-group" colspan="2">
-<kbd><span class="option">--randomize  
<var>&lt;what&gt;</var></span></kbd></td>
+<kbd><span class="option">--randomize <var>&lt;all|suites|tests| 
none&gt;</var></span></kbd></td>
 </tr>
-<tr><td>&nbsp;</td><td><a class="reference internal"  
href="#randomizing-execution-order">Randomizes the test execution  
order</a>.</td></tr>
+<tr><td>&nbsp;</td><td><a class="reference internal"  
href="#randomizing-execution-order">Randomizes</a> test execution  
order.</td></tr>
 <tr><td class="option-group" colspan="2">
 <kbd><span class="option">--runmode  
<var>&lt;mode&gt;</var></span></kbd></td>
 </tr>
-<tr><td>&nbsp;</td><td>Deprecated in Robot Framework 2.8, please use the
-the respective options above.
-Sets the execution mode for this test run.
-Valid modes are <a class="reference internal"  
href="#exitonfailure-mode">ExitOnFailure</a>, <a class="reference internal"  
href="#handling-teardowns">SkipTeardownOnExit</a>,
-<a class="reference internal" href="#dry-run">DryRun</a>, and <a  
class="reference internal"  
href="#randomizing-execution-order">Random</a>:&lt;what&gt;.</td></tr>
+<tr><td>&nbsp;</td><td>Deprecated in Robot Framework 2.8. Use separate
+<span class="opt">--dryrun</span>, <span  
class="opt">--exitonfailure</span>,
+<span class="opt">--skipteardownonexit</span> and <span  
class="opt">--randomize</span>
+options instead.</td></tr>
 <tr><td class="option-group" colspan="2">
 <kbd><span class="option">-W</span>, <span class="option">--monitorwidth  
<var>&lt;chars&gt;</var></span></kbd></td>
 </tr>
@@ -16308,11 +16302,11 @@
 <tr><td class="option-group" colspan="2">
 <kbd><span class="option">-x</span>, <span class="option">--xunitfile  
<var>&lt;file&gt;</var></span></kbd></td>
 </tr>
-<tr><td>&nbsp;</td><td>Sets the path to the generated <a class="reference  
internal" href="#xunit-compatible-result-file">XUnit compatible result  
file</a>.</td></tr>
+<tr><td>&nbsp;</td><td>Sets the path to the generated <a class="reference  
internal" href="#xunit-compatible-result-file">xUnit compatible result  
file</a>.</td></tr>
 <tr><td class="option-group" colspan="2">
 <kbd><span class="option">--xunitskipnoncritical</span></kbd></td>
 </tr>
-<tr><td>&nbsp;</td><td>Mark non-critical tests on <a class="reference  
internal" href="#xunit-compatible-result-file">XUnit compatible result  
file</a> as skipped.</td></tr>
+<tr><td>&nbsp;</td><td>Mark non-critical tests on <a class="reference  
internal" href="#xunit-compatible-result-file">xUnit compatible result  
file</a> as skipped.</td></tr>
 <tr><td class="option-group" colspan="2">
 <kbd><span class="option">-T</span>, <span  
class="option">--timestampoutputs</span></kbd></td>
 </tr>
@@ -16387,8 +16381,8 @@
 <tr><td class="option-group" colspan="2">
 <kbd><span class="option">--processemptysuite</span></kbd></td>
 </tr>
-<tr><td>&nbsp;</td><td>Processes an output file even if the top level <a  
class="reference internal" href="#when-no-tests-match-selection">test suite  
is
-empty</a>.</td></tr>
+<tr><td>&nbsp;</td><td>Processes output files even if files contain
+<a class="reference internal" href="#when-no-tests-match-selection">empty  
test suites</a>.</td></tr>
 <tr><td class="option-group" colspan="2">
 <kbd><span class="option">-E</span>, <span class="option">--escape  
<var>&lt;what:with&gt;</var></span></kbd></td>
 </tr>
@@ -16944,7 +16938,7 @@
 <div class="footer">
 <hr class="footer" />
 <p>Generated by <a class="reference external"  
href="http://docutils.sourceforge.net/rst.html";>reStructuredText</a>.  
Syntax highlighting by <a class="reference external"  
href="http://pygments.org/";>Pygments</a>.</p>
-<p>Generated on: 2013-05-31 09:35 UTC.
+<p>Generated on: 2013-05-31 10:57 UTC.
 </p>

 </div>

--

--- 
You received this message because you are subscribed to the Google Groups "robotframework-commit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to robotframework-commit+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.