<commit_before>tt-record(1)
============

Name
----
tt-record - run automated tests of text user interfaces

Synopsis
--------
tt-record [-f] [-x] <script> <command>

Introduction
------------

tuitest is a tool to create an run automated tests of text user interfaces.  It
is meant as a complement to the widespread use of unit tests, and uses concepts
known from GUI testing tools with the difference that it applies them
specifically to text- and terminal-based user interfaces.

tt-record is the binary to run a console tool (being the 'command' in the
command line) and generate a ruby script (being 'script') which can be used to
replay the recorded session.

Options and environment variables
---------------------------------

*-f*
  Enable fast mode. Do not respect exact timings but execute it as fast as
  possible.

*-x*
  Provide a junit compatible XML file (RESULT-$script.xml) when running the recorded session.
  The XML file can then be used in tools like for example hudson.

Usage examples
---------------

  tt-record output.rb vim

Run the console editor Vim and save the unit testing script as output.rb.
Then execute 'ruby ./output.rb' to replay the recorded session.
<commit_msg>Slightly improve manpage<commit_after>tt-record(1)
============

Name
----
tt-record - run automated tests of text user interfaces

Synopsis
--------
tt-record [-f] [-x] <script> <command>

Introduction
------------

tuitest is a tool to create an run automated tests of text user interfaces.  It
is meant as a complement to the widespread use of unit tests, and uses concepts
known from GUI testing tools with the difference that it applies them
specifically to text- and terminal-based user interfaces.

tt-record is the binary to run a console tool (being the 'command' in the
command line) and generate a ruby script (being 'script') which can be used to
replay the recorded session.

Options and environment variables
---------------------------------

*-f*::
    Enable fast mode. Do not respect exact timings but execute it as fast as
    possible.

*-x*::
    Provide a junit compatible XML file (RESULT-$script.xml) when running the recorded session.
    The XML file can then be used in tools like for example hudson.

Usage examples
---------------

  % tt-record output.rb vim

Run the console editor Vim and save the unit testing script as output.rb.
Then execute 'ruby ./output.rb' to replay the recorded session.

{'fraction_non_alphanumeric': 0.11970382558617852, 'fraction_numerical': 0.0008227067050596463, 'mean_word_length': 2.973856209150327, 'pattern_counts': {'":': 0, '<': 7, '<?xml version=': 0, '>': 7, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 2}, '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': '298503', 'n_tokens_mistral': 635, 'n_tokens_neox': 611, 'n_words': 344}