<commit_before># Testify

TODO: Write a gem description

## Installation

Add this line to your application's Gemfile:

    gem 'testify'

And then execute:

    $ bundle

Or install it yourself as:

    $ gem install testify

## Usage

TODO: Write usage instructions here

## Contributing

1. Fork it
2. Create your feature branch (`git checkout -b my-new-feature`)
3. Commit your changes (`git commit -am 'Added some feature'`)
4. Push to the branch (`git push origin my-new-feature`)
5. Create new Pull Request<commit_msg>Added README<commit_after># Testify

Testify is an ongoing sketch of what I think a test framework should be.
Design goals include:

* Test::Unit / Minitest syntax
* Generic test result data structure
* Pluggable output formatters
* Master/worker architecture
* Lazy reloading of master process as hard dependencies change

In essence, Testify aims to replace the (test framework + guard +
parallel hacks) set of libraries in an elegant way without monkeypatches
everywhere to make gems higher up the stack perform in a way they
weren't intended to.

Stay tuned.

## Installation

Don't.

## Usage

Don't.

## Contributing

1. Fork it
2. Create your feature branch (`git checkout -b my-new-feature`)
3. Commit your changes (`git commit -am 'Added some feature'`)
4. Push to the branch (`git push origin my-new-feature`)
5. Create new Pull Request
{'fraction_non_alphanumeric': 0.07512764405543398, 'fraction_numerical': 0.007293946024799417, 'mean_word_length': 4.044117647058823, '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': '2780369', 'n_tokens_mistral': 409, 'n_tokens_neox': 385, 'n_words': 193}