UG: Use '.robot' extension in examples consistently.

pekkaklarck · pekkaklarck · commit f6ef2f698694 · 2015-12-30T19:45:51.000+02:00
diff --git a/doc/userguide/src/ExecutingTestCases/BasicUsage.rst b/doc/userguide/src/ExecutingTestCases/BasicUsage.rst
@@ -67,9 +67,9 @@ __ `Test suite name and documentation`_
 
 ::
 
-   robot test_cases.html
+   robot tests.robot
    robot path/to/my_tests/
-   robot c:\robot\tests.txt
+   robot c:\robot\tests.robot
 
 It is also possible to give paths to several test case files or
 directories at once, separated with spaces. In this case, Robot
@@ -83,8 +83,8 @@ often quite long and complicated. In most cases, it is thus better to
 use the :option:`--name` option for overriding it, as in the second
 example below::
 
-   robot my_tests.html your_tests.html
-   robot --name Example path/to/tests/pattern_*.html
+   robot my_tests.robot your_tests.robot
+   robot --name Example path/to/tests/pattern_*.robot
 
 Using command line options
 --------------------------
@@ -101,7 +101,7 @@ Using options
 When options are used, they must always be given between the runner
 script and the data sources. For example::
 
-   robot -L debug my_tests.txt
+   robot -L debug my_tests.robot
    robot --include smoke --variable HOST:10.0.0.42 path/to/tests/
 
 Short and long options
@@ -233,7 +233,7 @@ avoid the need to repeat them every time tests are run or ``rebot`` used.
 .. sourcecode:: bash
 
    export ROBOT_OPTIONS="--critical regression --tagdoc 'mytag:Example doc with spaces'"
-   robot tests.txt
+   robot tests.robot
    export REBOT_OPTIONS="--reportbackground green:yellow:red"
    rebot --name example output.xml
 
@@ -345,7 +345,7 @@ Example below illustrates how errors and warnings look like in the log file.
      <tr>
        <td class="time">20090322&nbsp;19:58:42.528</td>
        <td class="error level">ERROR</td>
-       <td class="msg">Error in file '/home/robot/tests.html' in table 'Setting' in element on row 2: Resource file 'resource.html' does not exist</td>
+       <td class="msg">Error in file '/home/robot/tests.robot' in table 'Setting' in element on row 2: Resource file 'resource.robot' does not exist</td>
      </tr>
      <tr>
        <td class="time">20090322&nbsp;19:58:43.931</td>
@@ -464,10 +464,10 @@ option was. This means that options in argument files can override options
 before it, and its options can be overridden by options after it. It is possible
 to use :option:`--argumentfile` option multiple times or even recursively::
 
-   robot --argumentfile all_arguments.txt
-   robot --name Example --argumentfile other_options_and_paths.txt
-   robot --argumentfile default_options.txt --name Example my_tests.html
-   robot -A first.txt -A second.txt -A third.txt tests.txt
+   robot --argumentfile all_arguments.robot
+   robot --name Example --argumentfile other_options_and_paths.robot
+   robot --argumentfile default_options.txt --name Example my_tests.robot
+   robot -A first.txt -A second.txt -A third.txt tests.robot
 
 Reading argument files from standard input
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -477,7 +477,7 @@ standard input stream instead of a file. This can be useful when generating
 arguments with a script::
 
    generate_arguments.sh | robot --argumentfile STDIN
-   generate_arguments.sh | robot --name Example --argumentfile STDIN tests.txt
+   generate_arguments.sh | robot --name Example --argumentfile STDIN tests.robot
 
 Getting help and version information
 ------------------------------------
@@ -606,7 +606,7 @@ outputs are very big. There are several ways to configure JVM options:
    script that will pass them forward to Java. This is especially easy when
    using `direct entry points`_::
 
-      jython -J-Xmx1024m -m robot.run some_tests.txt
+      jython -J-Xmx1024m -m robot some_tests.robot
 
 Debugging problems
 ------------------
diff --git a/doc/userguide/src/ExecutingTestCases/ConfiguringExecution.rst b/doc/userguide/src/ExecutingTestCases/ConfiguringExecution.rst
@@ -209,11 +209,11 @@ when `post-processing outputs`_ with ``rebot``, you need to
 use :option:`--critical` and/or :option:`--noncritical` also with it::
 
   # Use rebot to create new log and report from the output created during execution
-  robot --critical regression --outputdir all my_tests.html
+  robot --critical regression --outputdir all tests.robot
   rebot --name Smoke --include smoke --critical regression --outputdir smoke all/output.xml
 
   # No need to use --critical/--noncritical when no log or report is created
-  robot --log NONE --report NONE my_tests.html
+  robot --log NONE --report NONE tests.robot
   rebot --critical feature1 output.xml
 
 __ `By tag names`_
@@ -439,7 +439,7 @@ what was randomized and what seed was used.
 
 Examples::
 
-    robot --randomize tests my_test.txt
+    robot --randomize tests my_test.robot
     robot --randomize all:12345 path/to/tests
 
 __ `Free test suite metadata`_
diff --git a/doc/userguide/src/ExecutingTestCases/OutputFiles.rst b/doc/userguide/src/ExecutingTestCases/OutputFiles.rst
@@ -172,7 +172,7 @@ the extension and the base name of each file. The example below would,
 for example, create such output files as
 :file:`output-20080604-163225.xml` and :file:`mylog-20080604-163225.html`::
 
-   robot --timestampoutputs --log mylog.html --report NONE tests.html
+   robot --timestampoutputs --log mylog.html --report NONE tests.robot
 
 Setting titles
 ~~~~~~~~~~~~~~
@@ -501,9 +501,9 @@ or warnings`__ are not removed except when using the `ALL` mode.
 Examples::
 
    rebot --removekeywords all --output removed.xml output.xml
-   robot --removekeywords passed --removekeywords for tests.txt
-   robot --removekeywords name:HugeKeyword --removekeywords name:resource.* tests.txt
-   robot --removekeywords tag:huge tests.txt
+   robot --removekeywords passed --removekeywords for tests.robot
+   robot --removekeywords name:HugeKeyword --removekeywords name:resource.* tests.robot
+   robot --removekeywords tag:huge tests.robot
 
 Removing keywords is done after parsing the `output file`_ and generating
 an internal model based on it. Thus it does not reduce memory usage as much
@@ -543,7 +543,7 @@ supports the following modes:
 
 Examples::
 
-   robot --flattenkeywords name:HugeKeyword --flattenkeywords name:resource.* tests.txt
+   robot --flattenkeywords name:HugeKeyword --flattenkeywords name:resource.* tests.robot
    rebot --flattenkeywords foritem --output flattened.xml original.xml
 
 Flattening keywords is done already when the `output file`_ is parsed
