<commit_before># PureScript Spec [![Build Status](https://travis-ci.org/owickstrom/purescript-spec.svg?branch=master)](https://travis-ci.org/owickstrom/purescript-spec)

PureScript Spec is a simple testing framework for Purescript, inspired by
[hspec](http://hspec.github.io/).

<img src="https://raw.githubusercontent.com/owickstrom/purescript-spec/master/example.png" width="400" />

## Documentation

* [PureScript Spec - The Guide](https://owickstrom.github.io/purescript-spec/) explains in detail
  how to use purescript-spec. **You should probably start here.**
* [purescript-spec on Pursuit](https://pursuit.purescript.org/packages/purescript-spec)
  features version information and API documentation.
* [BUILD.md](BUILD.md) lists build instructions for this project. Most
  likely not interesting unless your hacking on PureScript Spec itself.

## Changelog

* **0.11.0**
  * Publish *The Guide* on GitHub pages
  * Collapse result entries in Maps to deduplicate describes, fixes #9
  * Reimplement Node reporters and runner using purescript-pipes. An upgrade
    might require a change in your `main` type signature. The type
    `Test.Spec.Runner.RunnerEffects` makes it more convenient to specify all
    effect rows:<commit_msg>Add changelog entries<commit_after># PureScript Spec [![Build Status](https://travis-ci.org/owickstrom/purescript-spec.svg?branch=master)](https://travis-ci.org/owickstrom/purescript-spec)

PureScript Spec is a simple testing framework for Purescript, inspired by
[hspec](http://hspec.github.io/).

<img src="https://raw.githubusercontent.com/owickstrom/purescript-spec/master/example.png" width="400" />

## Documentation

* [PureScript Spec - The Guide](https://owickstrom.github.io/purescript-spec/) explains in detail
  how to use purescript-spec. **You should probably start here.**
* [purescript-spec on Pursuit](https://pursuit.purescript.org/packages/purescript-spec)
  features version information and API documentation.
* [BUILD.md](BUILD.md) lists build instructions for this project. Most
  likely not interesting unless your hacking on PureScript Spec itself.

## Changelog

* **0.12.2**
  * Reexport common reporters in `Test.Spec.Reporter` module, fixes #37
  * Export and document `run'` function (for configuration), fixes #38
* **0.12.1**
  * Move array of results to runner event, fixes #36
* **0.12.0**
  * Again support multiple reporters, fixes #33
* **0.11.0**
  * Publish *The Guide* on GitHub pages
  * Collapse result entries in Maps to deduplicate describes, fixes #9
  * Reimplement Node reporters and runner using purescript-pipes. An upgrade
    might require a change in your `main` type signature. The type
    `Test.Spec.Runner.RunnerEffects` makes it more convenient to specify all
    effect rows:
{'fraction_non_alphanumeric': 0.1146772448611612, 'fraction_numerical': 0.01298232960692391, 'mean_word_length': 4.626774847870182, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 5, 'https://': 10, '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': '1934130', 'n_tokens_mistral': 864, 'n_tokens_neox': 829, 'n_words': 260}