<commit_before>Continuous Testing
==================

"Continous testing" means automatically running your tests whenever you save changes to your code. It's a nice approach. It gives you instant feedback, and it saves you a  lot of typing.

Usage
=====

It's super-simple. Open a terminal emulator and run

    ./autotest my-test-file

This will re-run your test file whenever you save it¹.

Also included is on-file-change-do, a more generic shell quickie for running some action when a file changes. It works like this:

    ./on-file-change-do file-to-monitor 'shell command to run'

Requirements
============
* A Unix environment.
* Bash. This comes preinstalled with your Unix environment if you're using
  Linux, OS X, or Cygwin.

Installation
============
1. Edit your shell init file and append this directory to PATH.
2. There is no step 2.

Footnotes
=========

1. This assumes you're able to execute your test file. You will be if you remember to 'chmod u+x my-test-file', and if you use the shebang syntax for tests in interpreted programming languages, that is, start the file with<commit_msg>Superscript footnotes display poorly. Use [1] notation.<commit_after>Continuous Testing
==================

"Continous testing" means automatically running your tests whenever you save changes to your code. It's a nice approach. It gives you instant feedback, and it saves you a  lot of typing.

Usage
=====

It's super-simple. Open a terminal emulator and run

    ./autotest my-test-file

This will re-run your test file whenever you save it[1].

Also included is on-file-change-do, a more generic shell quickie for running some action when a file changes. It works like this:

    ./on-file-change-do file-to-monitor 'shell command to run'

Requirements
============
* A Unix environment.
* Bash. This comes preinstalled with your Unix environment if you're using
  Linux, OS X, or Cygwin.

Installation
============
1. Edit your shell init file and append this directory to PATH.
2. There is no step 2.

Footnotes
=========

[1] This assumes you're able to execute your test file. You will be if you remember to 'chmod u+x my-test-file', and if you use the shebang syntax for tests in interpreted programming languages, that is, start the file with
{'fraction_non_alphanumeric': 0.10314298362107127, 'fraction_numerical': 0.004426737494466578, 'mean_word_length': 4.022222222222222, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, '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': '2027703', 'n_tokens_mistral': 627, 'n_tokens_neox': 592, 'n_words': 325}