2 new revisions:
Revision: bf8ef3a16dbc
Branch: default
Author: Anssi Syrjäsalo
Date: Wed May 29 05:51:32 2013
Log: Documented --runmode and the respective new options in the user
guide....
http://code.google.com/p/robotframework/source/detail?r=bf8ef3a16dbc
Revision: b58ac0eb619f
Branch: default
Author: Anssi Syrjäsalo
Date: Wed May 29 05:52:50 2013
Log: merge
http://code.google.com/p/robotframework/source/detail?r=b58ac0eb619f
==============================================================================
Revision: bf8ef3a16dbc
Branch: default
Author: Anssi Syrjäsalo
Date: Wed May 29 05:51:32 2013
Log: Documented --runmode and the respective new options in the user
guide.
Update issue 1445
Updated the user guide related to the deprecated --runmode option and added
documentation related to the respective new options.
http://code.google.com/p/robotframework/source/detail?r=bf8ef3a16dbc
Modified:
/doc/userguide/RobotFrameworkUserGuide.html
/doc/userguide/src/Appendices/CommandLineOptions.rst
/doc/userguide/src/ExecutingTestCases/ConfiguringExecution.rst
/doc/userguide/src/ExecutingTestCases/TestExecution.rst
=======================================
--- /doc/userguide/RobotFrameworkUserGuide.html Tue May 28 12:17:04 2013
+++ /doc/userguide/RobotFrameworkUserGuide.html Wed May 29 05:51:32 2013
@@ -10617,7 +10617,7 @@
required order. This easily leads to overly long start-up commands,
but <a class="reference internal" href="#argument-files">argument
files</a> allow listing files nicely one file per line.</p>
<p>It is also possible to <a class="reference internal"
href="#randomizing-execution-order">randomize the execution order</a> using
-the <span class="opt">--runmode</span> option.</p>
+the <span class="opt">--randomize</span> option.</p>
</div>
<div class="section" id="passing-execution">
<h4><a class="toc-backref" href="#id556">Passing execution</a></h4>
@@ -10744,18 +10744,33 @@
</div>
<div class="section" id="exitonfailure-mode">
<h4><a class="toc-backref" href="#id566"><span
class="opt">ExitOnFailure</span> mode</a></h4>
-<p>If option <span class="opt">--runmode</span> is used with value <span
class="opt">ExitOnFailure</span>
-(case-insensitive), the execution of tests stops immediately if
-a <a class="reference internal" href="#setting-criticality">critical
test</a> fails and the remaining tests are marked as failed.</p>
+<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
+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>
+</div>
</div>
<div class="section" id="handling-teardowns">
<h4><a class="toc-backref" href="#id567">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.5.2, teardowns are skipped when the
execution is
-stopped if the <span class="opt">--runmode SkipTeardownOnExit</span>
command line option is used.
-This can be useful if clean-up takes a lot of time.</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>
+<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>
+</div>
</div>
</div>
</div>
@@ -11198,9 +11213,15 @@
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">--runmode
DryRun</span>
-(case-insensitive) and it is supported starting from Robot Framework
-2.5.</p>
+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>
<p>The dry run execution may fail for following reasons:</p>
<blockquote>
<ul class="simple">
@@ -11220,24 +11241,34 @@
</div>
<div class="section" id="randomizing-execution-order">
<h3><a class="toc-backref"
href="#id592">3.4.7 Randomizing execution order</a></h3>
-<p>The <span class="opt">--runmode</span> option can also be used to
randomize the test
-execution order. This is done using the different values explained
-below.</p>
+<p>The test execution order can be randomized using option
+<span class="opt">--randomize <what></span>, where <span
class="opt"><what></span> is one of the following:</p>
<dl class="docutils">
-<dt><span class="opt">random:test</span></dt>
-<dd>Test cases inside each test suite are executed in random
-order.</dd>
-<dt><span class="opt">random:suite</span></dt>
+<dt><span class="opt">tests</span></dt>
+<dd>Test cases inside each test suite are executed in random order.</dd>
+<dt><span class="opt">suites</span></dt>
<dd>All test suites are executed in a random order, but test cases inside
suites are run in the order they are defined.</dd>
-<dt><span class="opt">random:all</span></dt>
-<dd>Both test cases and test suites are executed in a random
-order.</dd>
+<dt><span class="opt">all</span></dt>
+<dd>Both test cases and test suites are executed in a random order.</dd>
+<dt><span class="opt">none</span></dt>
+<dd>Neither execution order of test nor suites is randomized.
+This value can be used to override the earlier value set with
+<span class="opt">--randomize</span>.</dd>
</dl>
<p>Example:</p>
<pre class="literal-block">
-pybot --runmode random:test my_test.txt
+pybot --randomize tests my_test.txt
</pre>
+<div class="note">
+<p class="first admonition-title">Note</p>
+<p>Prior to Robot Framework 2.8, randomization is triggered using option
+<span class="opt">--runmode <mode></span>, where <mode> 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>
+<p class="last">Option <span class="opt">--runmode</span> is deprecated in
2.8 and will be removed
+in the future.</p>
+</div>
</div>
<div class="section" id="controlling-console-output">
<h3><a class="toc-backref"
href="#id593">3.4.8 Controlling console output</a></h3>
@@ -16143,10 +16174,28 @@
</tr>
<tr><td> </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 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>
+<tr><td class="option-group" colspan="2">
+<kbd><span class="option">--exitonfailure</span></kbd></td>
+</tr>
+<tr><td> </td><td><a class="reference internal"
href="#exitonfailure-mode">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> </td><td><a class="reference internal"
href="#handling-teardowns">Skips teardowns</a> when the execution is
stopped.</td></tr>
+<tr><td class="option-group" colspan="2">
+<kbd><span class="option">--randomize
<var><what></var></span></kbd></td>
+</tr>
+<tr><td> </td><td><a class="reference internal"
href="#randomizing-execution-order">Randomizes the test execution
order</a>.</td></tr>
<tr><td class="option-group" colspan="2">
<kbd><span class="option">--runmode
<var><mode></var></span></kbd></td>
</tr>
-<tr><td> </td><td>Sets the execution mode for this test run.
+<tr><td> </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>:<what>.</td></tr>
<tr><td class="option-group" colspan="2">
@@ -16887,7 +16936,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-28 19:14 UTC.
+<p>Generated on: 2013-05-29 12:48 UTC.
</p>
</div>
=======================================
--- /doc/userguide/src/Appendices/CommandLineOptions.rst Mon May 27
08:57:25 2013
+++ /doc/userguide/src/Appendices/CommandLineOptions.rst Wed May 29
05:51:32 2013
@@ -61,7 +61,14 @@
in test cases. Error codes are returned normally.
--runemptysuite Executes tests also if the top level `test suite
is
empty`_.
- --runmode <mode> Sets the execution mode for this test run.
+ --dryrun When `dry run`_, keywords coming from the test
+ libraries are not executed at all.
+ --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>.
-W, --monitorwidth <chars> `Sets the width`_ of the console output.
@@ -138,9 +145,12 @@
.. _considered critical: `Setting criticality`_
.. _not critical: `considered critical`_
.. _ContinueOnFailure: `Continue on failure`_
+.. _Stops execution: `ExitOnFailure mode`_
.. _ExitOnFailure: `ExitOnFailure mode`_
+.. _Skips teardowns: `Handling Teardowns`_
.. _SkipTeardownOnExit: `Handling Teardowns`_
.. _DryRun: `Dry run`_
+.. _Randomizes the test execution order: `Randomizing execution order`_
.. _Random: `Randomizing execution order`_
.. _individual variables: `Setting variables in command line`_
=======================================
--- /doc/userguide/src/ExecutingTestCases/ConfiguringExecution.rst Mon May
20 03:54:35 2013
+++ /doc/userguide/src/ExecutingTestCases/ConfiguringExecution.rst Wed May
29 05:51:32 2013
@@ -358,9 +358,14 @@
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:`--runmode DryRun`
-(case-insensitive) and it is supported starting from Robot Framework
-2.5.
+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.
The dry run execution may fail for following reasons:
@@ -380,25 +385,37 @@
Randomizing execution order
~~~~~~~~~~~~~~~~~~~~~~~~~~~
-The :opt:`--runmode` option can also be used to randomize the test
-execution order. This is done using the different values explained
-below.
+The test execution order can be randomized using option
+:opt:`--randomize <what>`, where :opt:`<what>` is one of the following:
-:opt:`random:test`
- Test cases inside each test suite are executed in random
- order.
+:opt:`tests`
+ Test cases inside each test suite are executed in random order.
-:opt:`random:suite`
+:opt:`suites`
All test suites are executed in a random order, but test cases inside
suites are run in the order they are defined.
-:opt:`random:all`
- Both test cases and test suites are executed in a random
- order.
+:opt:`all`
+ Both test cases and test suites are executed in a random order.
+
+:opt:`none`
+ Neither execution order of test nor suites is randomized.
+ This value can be used to override the earlier value set with
+ :opt:`--randomize`.
+
Example::
- pybot --runmode random:test my_test.txt
+ pybot --randomize tests my_test.txt
+
+
+.. 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`.
+
+ Option :opt:`--runmode` is deprecated in 2.8 and will be removed
+ in the future.
Controlling console output
~~~~~~~~~~~~~~~~~~~~~~~~~~
=======================================
--- /doc/userguide/src/ExecutingTestCases/TestExecution.rst Mon May 27
08:40:49 2013
+++ /doc/userguide/src/ExecutingTestCases/TestExecution.rst Wed May 29
05:51:32 2013
@@ -129,7 +129,7 @@
but `argument files`_ allow listing files nicely one file per line.
It is also possible to `randomize the execution order`__ using
-the :opt:`--runmode` option.
+the :opt:`--randomize` option.
__ `Randomizing execution order`_
@@ -287,9 +287,16 @@
:opt:`ExitOnFailure` mode
'''''''''''''''''''''''''
-If option :opt:`--runmode` is used with value :opt:`ExitOnFailure`
-(case-insensitive), the execution of tests stops immediately if
-a `critical test`_ fails and the remaining tests are marked as failed.
+If option :opt:`--exitonfailure` (case-insensitive) is used, the execution
of
+tests stops immediately if a `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.
+
Handling teardowns
''''''''''''''''''
@@ -298,6 +305,14 @@
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.5.2, teardowns are skipped when the
execution is
-stopped if the :opt:`--runmode SkipTeardownOnExit` command line option is
used.
+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.
+
+.. Note:: Prior to Robot Framework 2.8, this behaviour is achieved by
+ using :opt:`--runmode SkipTearDownOnExit` (case-insensitive).
+
+ Option :opt:`--runmode` is deprecated in 2.8 and will be removed
+ in the future.
==============================================================================
Revision: b58ac0eb619f
Branch: default
Author: Anssi Syrjäsalo
Date: Wed May 29 05:52:50 2013
Log: merge
http://code.google.com/p/robotframework/source/detail?r=b58ac0eb619f
Modified:
/doc/userguide/RobotFrameworkUserGuide.html
=======================================
--- /doc/userguide/RobotFrameworkUserGuide.html Wed May 29 05:48:38 2013
+++ /doc/userguide/RobotFrameworkUserGuide.html Wed May 29 05:52:50 2013
@@ -10617,7 +10617,7 @@
required order. This easily leads to overly long start-up commands,
but <a class="reference internal" href="#argument-files">argument
files</a> allow listing files nicely one file per line.</p>
<p>It is also possible to <a class="reference internal"
href="#randomizing-execution-order">randomize the execution order</a> using
-the <span class="opt">--runmode</span> option.</p>
+the <span class="opt">--randomize</span> option.</p>
</div>
<div class="section" id="passing-execution">
<h4><a class="toc-backref" href="#id556">Passing execution</a></h4>
@@ -10744,18 +10744,33 @@
</div>
<div class="section" id="exitonfailure-mode">
<h4><a class="toc-backref" href="#id566"><span
class="opt">ExitOnFailure</span> mode</a></h4>
-<p>If option <span class="opt">--runmode</span> is used with value <span
class="opt">ExitOnFailure</span>
-(case-insensitive), the execution of tests stops immediately if
-a <a class="reference internal" href="#setting-criticality">critical
test</a> fails and the remaining tests are marked as failed.</p>
+<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
+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>
+</div>
</div>
<div class="section" id="handling-teardowns">
<h4><a class="toc-backref" href="#id567">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.5.2, teardowns are skipped when the
execution is
-stopped if the <span class="opt">--runmode SkipTeardownOnExit</span>
command line option is used.
-This can be useful if clean-up takes a lot of time.</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>
+<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>
+</div>
</div>
</div>
</div>
@@ -11198,9 +11213,15 @@
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">--runmode
DryRun</span>
-(case-insensitive) and it is supported starting from Robot Framework
-2.5.</p>
+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>
<p>The dry run execution may fail for following reasons:</p>
<blockquote>
<ul class="simple">
@@ -11220,24 +11241,34 @@
</div>
<div class="section" id="randomizing-execution-order">
<h3><a class="toc-backref"
href="#id592">3.4.7 Randomizing execution order</a></h3>
-<p>The <span class="opt">--runmode</span> option can also be used to
randomize the test
-execution order. This is done using the different values explained
-below.</p>
+<p>The test execution order can be randomized using option
+<span class="opt">--randomize <what></span>, where <span
class="opt"><what></span> is one of the following:</p>
<dl class="docutils">
-<dt><span class="opt">random:test</span></dt>
-<dd>Test cases inside each test suite are executed in random
-order.</dd>
-<dt><span class="opt">random:suite</span></dt>
+<dt><span class="opt">tests</span></dt>
+<dd>Test cases inside each test suite are executed in random order.</dd>
+<dt><span class="opt">suites</span></dt>
<dd>All test suites are executed in a random order, but test cases inside
suites are run in the order they are defined.</dd>
-<dt><span class="opt">random:all</span></dt>
-<dd>Both test cases and test suites are executed in a random
-order.</dd>
+<dt><span class="opt">all</span></dt>
+<dd>Both test cases and test suites are executed in a random order.</dd>
+<dt><span class="opt">none</span></dt>
+<dd>Neither execution order of test nor suites is randomized.
+This value can be used to override the earlier value set with
+<span class="opt">--randomize</span>.</dd>
</dl>
<p>Example:</p>
<pre class="literal-block">
-pybot --runmode random:test my_test.txt
+pybot --randomize tests my_test.txt
</pre>
+<div class="note">
+<p class="first admonition-title">Note</p>
+<p>Prior to Robot Framework 2.8, randomization is triggered using option
+<span class="opt">--runmode <mode></span>, where <mode> 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>
+<p class="last">Option <span class="opt">--runmode</span> is deprecated in
2.8 and will be removed
+in the future.</p>
+</div>
</div>
<div class="section" id="controlling-console-output">
<h3><a class="toc-backref"
href="#id593">3.4.8 Controlling console output</a></h3>
@@ -16148,10 +16179,28 @@
</tr>
<tr><td> </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 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>
+<tr><td class="option-group" colspan="2">
+<kbd><span class="option">--exitonfailure</span></kbd></td>
+</tr>
+<tr><td> </td><td><a class="reference internal"
href="#exitonfailure-mode">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> </td><td><a class="reference internal"
href="#handling-teardowns">Skips teardowns</a> when the execution is
stopped.</td></tr>
+<tr><td class="option-group" colspan="2">
+<kbd><span class="option">--randomize
<var><what></var></span></kbd></td>
+</tr>
+<tr><td> </td><td><a class="reference internal"
href="#randomizing-execution-order">Randomizes the test execution
order</a>.</td></tr>
<tr><td class="option-group" colspan="2">
<kbd><span class="option">--runmode
<var><mode></var></span></kbd></td>
</tr>
-<tr><td> </td><td>Sets the execution mode for this test run.
+<tr><td> </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>:<what>.</td></tr>
<tr><td class="option-group" colspan="2">
@@ -16892,7 +16941,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-29 12:47 UTC.
+<p>Generated on: 2013-05-29 12:52 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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
