<commit_before>Post-processing outputs
-----------------------

`XML output files`_ that are generated during the test execution can be
post-processed afterwards by the :prog:`rebot` tool, which is an integral
part of Robot Framework. It is used automatically when test
reports and logs are generated during the test execution, but there
are also good grounds for using it separately after the execution.

.. contents::
   :depth: 2
   :local:

Using :prog:`rebot` tool
~~~~~~~~~~~~~~~~~~~~~~~~

The basic syntax for using :prog:`rebot` is exactly the same as when
`starting test execution`_, `return codes`_ are the same, and also
most of the command line options are identical. The main difference is
that arguments to :prog:`rebot` are XML output files instead of test
data files or directories.


Creating different reports and logs
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

You can use :prog:`rebot` for creating the same reports and logs that
are created automatically during the test execution. Of course, it is
not sensible to create the exactly same files, but, for example,
having one report with all test cases and another with only some
subset of tests can be useful. Another common usage is creating only
the output file when running tests (log and report generation can be
disabled with options :opt:`--log NONE` and :opt:`--report NONE`) and
generating logs and reports later. Tests can, for example, be executed
on different environments, output files collected to a central place,
and reports and logs created there. If generating reports and logs
takes a lot of time when running tests on Jython, it is a good idea to
try if using :prog:`rebot`, which always runs on Python, is any
faster.

::

   rebot output.xml
   rebot path/to/output_file.xml
   rebot --include smoke --name Smoke_Tests c:\results\output.xml

.. Note:: When running tests with Jython, the default JVM maximum
          memory size may not be enough for creating reports and logs
          if output files are very large. If that happens, you can
          either `increase the JVM's maximum memory`__, or disable
          creating reports and logs when tests are executed and use
          :prog:`rebot` to generate them afterwards.

__ `Modifying Java startup parameters`_

Combining outputs
~~~~~~~~~~~~~~~~~
<commit_msg>mention robot usage with jar distribution<commit_after>Post-processing outputs
-----------------------

`XML output files`_ that are generated during the test execution can be
post-processed afterwards by the :prog:`rebot` tool, which is an integral
part of Robot Framework. It is used automatically when test
reports and logs are generated during the test execution, but there
are also good grounds for using it separately after the execution.

.. contents::
   :depth: 2
   :local:

Using :prog:`rebot` tool
~~~~~~~~~~~~~~~~~~~~~~~~

The basic syntax for using :prog:`rebot` is exactly the same as when
`starting test execution`_, `return codes`_ are the same, and also
most of the command line options are identical. The main difference is
that arguments to :prog:`rebot` are XML output files instead of test
data files or directories.



Creating different reports and logs
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

You can use :prog:`rebot` for creating the same reports and logs that
are created automatically during the test execution. Of course, it is
not sensible to create the exactly same files, but, for example,
having one report with all test cases and another with only some
subset of tests can be useful. Another common usage is creating only
the output file when running tests (log and report generation can be
disabled with options :opt:`--log NONE` and :opt:`--report NONE`) and
generating logs and reports later. Tests can, for example, be executed
on different environments, output files collected to a central place,
and reports and logs created there. If generating reports and logs
takes a lot of time when running tests on Jython, it is a good idea to
try if using :prog:`rebot`, which always runs on Python, is any
faster.

::

   rebot output.xml
   rebot path/to/output_file.xml
   rebot --include smoke --name Smoke_Tests c:\results\output.xml

When using Robot Framework jar distribution, :prog:`rebot` is started with command:

::

    java -jar robotframework-<version>.jar rebot

.. Note:: When running tests with Jython, the default JVM maximum
          memory size may not be enough for creating reports and logs
          if output files are very large. If that happens, you can
          either `increase the JVM's maximum memory`__, or disable
          creating reports and logs when tests are executed and use
          :prog:`rebot` to generate them afterwards.

__ `Modifying Java startup parameters`_

Combining outputs
~~~~~~~~~~~~~~~~~

{'fraction_non_alphanumeric': 0.09130798161303803, 'fraction_numerical': 0.0004178854993731718, 'mean_word_length': 3.950361944157187, 'pattern_counts': {'":': 0, '<': 4, '<?xml version=': 0, '>': 4, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 6}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4819845', 'n_tokens_mistral': 1195, 'n_tokens_neox': 1146, 'n_words': 674}