<commit_before>## Poncho
[![Build Status](https://secure.travis-ci.org/deepsweet/poncho.png)](https://travis-ci.org/deepsweet/poncho) <a href="http://badge.fury.io/js/poncho"><img src="https://badge.fury.io/js/poncho@2x.png" alt="NPM version" height="18"></a> [![Dependency Status](https://gemnasium.com/deepsweet/poncho.png)](https://gemnasium.com/deepsweet/poncho) [![license MIT](http://b.repl.ca/v1/license-MIT-brightgreen.png)](https://github.com/deepsweet/poncho/blob/master/LICENSE)

Client-side JS code coverage using [PhantomJS](https://github.com/ariya/phantomjs), [Mocha](https://github.com/visionmedia/mocha) and [Blanket](https://github.com/alex-seville/blanket).


### Install

```sh
$ npm i --save-dev poncho
```

```
Usage: poncho [options] <file>

Options:

  -h, --help             output usage information
  -V, --version          output the version number
  -R, --reporter [type]  reporter: plain (default) | lcov | json
```


### Usage

Let's imagine that you already have PhantomJS + Mocha client-side tests (with [mocha-phantomjs](https://github.com/metaskills/mocha-phantomjs), for example), something like this `test/test.html`:

```html
<!DOCTYPE html>

<head>
    <meta charset="utf-8"/>
    <title>Mocha Test</title>
    <link rel="stylesheet" href="mocha/mocha.css"/>
</head>

<body>
    <div id="mocha"></div>

    <!-- mocha -->
    <script src="mocha/mocha.js"></script>
    <script>mocha.setup('bdd');</script>

    <!-- target script -->
    <script src="script.js"></script>
    <!-- test file -->
    <script src="test.js"></script>

    <!-- run -->
    <script>(window.mochaPhantomJS || mocha)run();</script>
</body>
```

All you need to do is add `data-cover` attribute to the target script tag:
<commit_msg>fix a typo<commit_after>## Poncho
[![Build Status](https://secure.travis-ci.org/deepsweet/poncho.png)](https://travis-ci.org/deepsweet/poncho) <a href="http://badge.fury.io/js/poncho"><img src="https://badge.fury.io/js/poncho@2x.png" alt="NPM version" height="18"></a> [![Dependency Status](https://gemnasium.com/deepsweet/poncho.png)](https://gemnasium.com/deepsweet/poncho) [![license MIT](http://b.repl.ca/v1/license-MIT-brightgreen.png)](https://github.com/deepsweet/poncho/blob/master/LICENSE)

Client-side JS code coverage using [PhantomJS](https://github.com/ariya/phantomjs), [Mocha](https://github.com/visionmedia/mocha) and [Blanket](https://github.com/alex-seville/blanket).


### Install

```sh
$ npm i --save-dev poncho
```

```
Usage: poncho [options] <file>

Options:

  -h, --help             output usage information
  -V, --version          output the version number
  -R, --reporter [type]  reporter: plain (default) | lcov | json
```


### Usage

Let's imagine that you already have PhantomJS + Mocha client-side tests (with [mocha-phantomjs](https://github.com/metaskills/mocha-phantomjs), for example), something like this `test/test.html`:

```html
<!DOCTYPE html>

<head>
    <meta charset="utf-8"/>
    <title>Mocha Test</title>
    <link rel="stylesheet" href="mocha/mocha.css"/>
</head>

<body>
    <div id="mocha"></div>

    <!-- mocha -->
    <script src="mocha/mocha.js"></script>
    <script>mocha.setup('bdd');</script>

    <!-- target script -->
    <script src="script.js"></script>
    <!-- test file -->
    <script src="test.js"></script>

    <!-- run -->
    <script>(window.mochaPhantomJS || mocha).run();</script>
</body>
```

All you need to do is add `data-cover` attribute to the target script tag:

{'fraction_non_alphanumeric': 0.20303550973654066, 'fraction_numerical': 0.0028636884306987398, 'mean_word_length': 3.745923913043478, 'pattern_counts': {'":': 0, '<': 61, '<?xml version=': 0, '>': 61, 'https://': 20, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 2, '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': '4770249', 'n_tokens_mistral': 1294, 'n_tokens_neox': 1225, 'n_words': 236}