<commit_before># grunt-junit

A small alteration to grunt's default phantom.js and qunit.js files to render rudimentary junit compatible xml for use with Jenkins.

## Important

This plugin currently overrides the default phantom.js and qunit.js files that are included with grunt.

## Getting Started
Install the module with: `npm install grunt-junit`

```javascript
grunt.loadNpmTasks( "grunt-junit" );
```

Then from the command line:

    $ JUNIT_OUTPUT=test-output-dir grunt junt

The junit task is identical to the running qunit save for the additional xml rendering to the output directory. You can find information on configuring the qunit grunt task [here](https://github.com/cowboy/grunt/blob/master/docs/task_qunit.md).

## Contributing
In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using `grunt lint` from the project root.<commit_msg>more information on file output and names<commit_after># grunt-junit

A small alteration to grunt's default phantom.js and qunit.js files to render rudimentary junit compatible xml for use with Jenkins.

## Important

This plugin currently overrides the default phantom.js and qunit.js files that are included with grunt.

## Getting Started
Install the module with: `npm install grunt-junit`

```javascript
grunt.loadNpmTasks( "grunt-junit" );
```

Then from the command line:

    $ JUNIT_OUTPUT=test-output-dir grunt junt

All the xml can be found inside the `test-output-dir`.


## Futher Information

The file names will take the form `TEST-<dasherized-url>.xml` and can be globbed easily for use with a CI like Jenkins.

Please note that the "dasherizing" is most likely exceptionally fragile, so please do report issues with specific test urls and I'll make corrections

The junit task is identical to the running qunit save for the additional xml rendering to the output directory. You can find information on configuring the qunit grunt task [here](https://github.com/cowboy/grunt/blob/master/docs/task_qunit.md).

## Contributing
In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using `grunt lint` from the project root.
{'fraction_non_alphanumeric': 0.06309834638816363, 'fraction_numerical': 0.0, 'mean_word_length': 4.580097087378641, 'pattern_counts': {'":': 0, '<': 4, '<?xml version=': 0, '>': 4, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 6}, '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': '1904129', 'n_tokens_mistral': 646, 'n_tokens_neox': 620, 'n_words': 307}