<commit_before>## grunt-ensure v0.1

>Ensures production files have associated best practice files which typically include Unit Tests, Documentation etc.
A Alpha feature includes the ability to process templates that can update and create test runners, and create js tests skeletons
for QUnit, JUnit, and Jasmine

## Installation
This plugin requires Grunt `~0.4.0`

If you haven't used [Grunt](http://gruntjs.com/) before, be sure to check out the [Getting Started](http://gruntjs.com/getting-started)
guide, as it explains how to create a [Gruntfile](http://gruntjs.com/sample-gruntfile) as well as install and use Grunt plugins.
Once you're familiar with that process, you may install this plugin with this command:

```shell
npm install grunt-ensure --save-dev
```

Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:

```js
grunt.loadNpmTasks('grunt-ensure');
```

## Ensure task
_Run this task using the `grunt ensure` command._

- Matches production files to best practice files (QUnit, Doc's etc)
- If templating information is present any missing best practice files will be created
- If any production files cannot be matched to best practice files the task will abort grunt

## How ensure works
Ensure is a multi-task grunt plugin that allows you to match production files to best practice files. Ensure accepts 1:n
targets so that it can look for different types of practice files

### Matching Production to Practice Files
Ensure expects practice files to be at least a substring of the associated production file.  An exact match is not required
since ensure can normalize the names by removing prefix or suffix information from the practice or production files before
comparing them, for instance any of these practice files could be matched using ensures normalization settings
<commit_msg>Update Source Code<commit_after>## grunt-ensure v0.1

>Ensures production files have associated best practice files which typically include Unit Tests, Documentation etc.
A Alpha feature includes the ability to process templates that can update and create test runners, and create js tests skeletons
for QUnit, JUnit, and Jasmine

## Installation
This plugin requires Grunt `~0.4.0`

If you haven't used [Grunt](http://gruntjs.com/) before, be sure to check out the [Getting Started](http://gruntjs.com/getting-started)
guide, as it explains how to create a [Gruntfile](http://gruntjs.com/sample-gruntfile) as well as install and use Grunt plugins.
Once you're familiar with that process, you may install this plugin with this command:

```shell
npm install grunt-ensure --save-dev
```

Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:

```js
grunt.loadNpmTasks('grunt-ensure');
```

## Ensure task
_Run this task using the `grunt ensure` command._

- Matches production files to best practice files (QUnit, Doc's etc)
- If templating information is present any missing best practice files will be created
- If any production files cannot be matched to best practice files the task will abort grunt

## How ensure works
Ensure is a multi-task grunt plugin that allows you to match production files to best practice files. Ensure accepts 1:n
targets so that it can look for different types of practice files such as

- QUnit javascript files
- JUnit javascript files
- JSDoc files
- Etc.

### Matching Production to Practice Files
Ensure expects practice files to be at least a substring of the associated production file.  An exact match is not required
since ensure can normalize the names by removing prefix or suffix information from the practice or production files before
comparing them, for instance any of these practice files could be matched using ensures normalization settings

{'fraction_non_alphanumeric': 0.05545335085413929, 'fraction_numerical': 0.0031537450722733244, 'mean_word_length': 4.766666666666667, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 5, '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': '1607660', 'n_tokens_mistral': 973, 'n_tokens_neox': 940, 'n_words': 545}