{"_id":"grunt-vows-runner","_rev":"35-a9869740518b8539a93eb67669afd04a","name":"grunt-vows-runner","description":"An alternative test-runner for vows using grunt.  Adds new capabilities such as running test suites concurrently.","dist-tags":{"latest":"0.6.0"},"versions":{"0.1.0":{"name":"grunt-vows-runner","version":"0.1.0","description":"A test-runner for vows using grunt.  Adds new capabilities such as running test suites concurrently.","keywords":["vows","test","testing","runner","task","gruntplugin","grunt","bdd","concurrent","asynchronous","parallel"],"author":{"name":"Adam Stallard","email":"adam@goalzen.org","url":"goalzen.org"},"directories":{"test":"test"},"dependencies":{"vows":"*","grunt":"~0.4","underscore":"*"},"license":{"type":"MIT","url":"https://github.com/goalzen/grunt-vows-runner/blob/master/LICENSE-MIT"},"engines":{"node":">=0.8.0"},"scripts":{"test":"grunt"},"repository":{"type":"git","url":"https://github.com/goalzen/grunt-vows-runner.git"},"bugs":{"url":"https://github.com/goalzen/grunt-vows-runner/issues"},"homepage":"https://github.com/goalzen/grunt-vows-runner.git","readme":"##grunt-vows-runner\n\nA test-runner for vows using [grunt](http://gruntjs.com/).\n\n###Philosophy\n\nFile and directory matching, file watching, coverage reporting, etc. should be supplied by third-party tools where possible.\nGrunt is a great source of such third-party-tools.  These are much more likely to continue development than the equivalent\ntools built into vows, since they are used by many other packages as well.\n\n###Additions\n\nWith grunt-vows-runner you can\n\n* Use grunt [tasks](http://gruntjs.com/configuring-tasks) and [templates](http://gruntjs.com/configuring-tasks#templates).\n* Run suites in the same [target](http://gruntjs.com/configuring-tasks#task-configuration-and-targets)\nconcurrently.\n* Set options at the target level.\n* Set the ``isolate`` option at the suite and target level, and run isolated and non-isolated suites concurrently.\n* Disable groups of tests at the target level\n\n###Differences from the vows command-line runner\n\n* Uses grunt to specify which [files](http://gruntjs.com/configuring-tasks#files) to run\n* Uses grunt's ``watch`` task instead of vows' built-in watch implementation\n* No shuffle option (if you want this, let me know--it is easy to implement)\n* No built-in js-coverage support\n * I highly recommend [istanbul](https://github.com/yahoo/istanbul), which does not need the cooperation of the test-runner\n (simply ``istanbul cover bin/vows`` will work ); and it is written in javascript, not java\n\n###Installation\n\n1. Change directories to the root directory of your project\n2. ``npm install grunt-vows-runner``\n\n###Usage\n\nAdd the following line to your ``Gruntfile.js``\n\n    grunt.loadNpmTasks('grunt-vows-runner');\n\nThe ``vows`` task is now available; for example\n\n    grunt vows\n\n###Configuration\n\nConfiguration is placed in the ``grunt.initConfig`` section of your ``Gruntfile.js`` file in the ``vows`` object.\n\n``vows`` is a [multitask](http://gruntjs.com/creating-tasks#multi-tasks).\n\nEach target references one or more source files containing suites and may contain options which will be applied to all of those\nsuites.\n\nAn example ``vows`` configuration with two targets:\n\n    ...\n    vows : {\n      all : {\n        src : \"<%= allTests %>\",\n        options : {\n          reporter : \"spec\"\n        }\n      },\n      allXunit : {\n        src : \"<%= allTests %>\",\n        dest : \"testResults.xml\"\n        options : {\n          reporter : \"xunit\"\n        }\n      }\n    },\n    allTests : \"tests/*\"\n    ...\n\nThe example above uses the [_compact format_ for specifying files](http://gruntjs.com/configuring-tasks#compact-format)\nas well as [templates](http://gruntjs.com/configuring-tasks#templates).\n\nOne destination file (``dest``) can be specified per target.  It will contain the output of all the suites in the target.  If no\ndestination file is specified, the output will go to the console.\n\nPaths for both source and destination files are relative to the directory that the ``Gruntfile.js`` is in.\n\nResults are summed by target.  Grunt-vows-runner doesn't combine the results of multiple targets.\n\nSuites within a target are run concurrently; faster suites will finish first.  Targets in grunt are always run sequentially.\n\n####Options\n\nOptions can be placed at the task (``vows``), target, or suite level.\n\nHere is an example of each:\n\n_Gruntfile.js_ (task- and target-level options)\n\n    ...\n    vows : {\n      options : {\n        reporter : \"spec\"\n      },\n      most : {\n        src : [\"test/*\", \"!test/chattyTests.js\"]\n      },\n      chatty : {\n        src : \"test/chattyTests.js\",\n        options : {\n          reporter : \"silent\"\n        }\n      }\n    }\n    ...\n\n_test/errorTests.js_ (suite-level options)\n\n    ...\n    vows.describe('Error Handling').addBatch({\n    ...\n    }).export(module, {error : false});\n    ...\n\nThe following options are available:\n\n* ``error``\n * Whether or not vows should handle errors in topics for you.  Set ``error : false`` if you want to handle your own errors.\n The first argument to your vows will be reserved for errors.\n* ``reporter``\n * silent, spec, json, tap, xunit, dot-matrix.  (Look in [vows/lib/vows/reporters](https://github.com/cloudhead/vows/tree/master/lib/vows/reporters)\n  for a complete list.)\n* ``matcher``\n * a javascript [RegExp object](http://www.w3schools.com/jsref/jsref_obj_regexp.asp); only run tests whose titles match this\n object.\n* ``isolate``\n * Run each suite in its own process.  This is useful if the system-under-test uses the node process object internally.\n* ``disabled``\n * Temporarily disable tests for a target.\n\n###Command-Line Options\n\ngrunt-vows-runner incorporates the following grunt command-line options, if present:\n\n* ``--no-color``\n* ``--verbose``\n\n###Alternatives\n\nIf you would like a grunt plugin that simply forwards options to the existing vows command-line runner,\nsee [grunt-vows](https://github.com/CMTegner/grunt-vows).\n\n","readmeFilename":"README.md","_id":"grunt-vows-runner@0.1.0","dist":{"shasum":"50098240d769c2674033fd2286fb487aa0263ea9","tarball":"https://registry.npmjs.org/grunt-vows-runner/-/grunt-vows-runner-0.1.0.tgz","integrity":"sha512-/Fo6W6Q7o8rw17f7cEBUEjm412kVagWxy/4DkuL7/6r9GqpzdgQIv9kdgAYccBxYTLTun4aqMk1mQu+AEvUFfQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCbeNdaj/Sw31HXUXGA3qm0MeFmjxnZRMUTdU72qDGUqgIhAIx1YJR86t1vDF5BMnVJmIQYgWVBFQqkTm7NPJMPTWVB"}]},"_npmVersion":"1.1.69","_npmUser":{"name":"adamstallard","email":"adam@sweedl.com"},"maintainers":[{"name":"adamstallard","email":"adam@sweedl.com"}]},"0.1.1":{"name":"grunt-vows-runner","version":"0.1.1","description":"A test-runner for vows using grunt.  Adds new capabilities such as running test suites concurrently.","keywords":["vows","test","testing","runner","task","gruntplugin","grunt","bdd","concurrent","asynchronous","parallel"],"author":{"name":"Adam Stallard","email":"adam@goalzen.org","url":"goalzen.org"},"directories":{"test":"test"},"dependencies":{"vows":"*","grunt":"~0.4","underscore":"*"},"license":{"type":"MIT","url":"https://github.com/goalzen/grunt-vows-runner/blob/master/LICENSE-MIT"},"engines":{"node":">=0.8.0"},"scripts":{"test":"grunt"},"repository":{"type":"git","url":"https://github.com/goalzen/grunt-vows-runner.git"},"bugs":{"url":"https://github.com/goalzen/grunt-vows-runner/issues"},"homepage":"https://github.com/goalzen/grunt-vows-runner.git","readme":"##grunt-vows-runner\n\nA test-runner for vows using [grunt](http://gruntjs.com/).\n\n###Philosophy\n\nFile and directory matching, file watching, coverage reporting, etc. should be supplied by third-party tools where possible.\nGrunt is a great source of such third-party-tools.  These are much more likely to continue development than the equivalent\ntools built into vows, since they are used by many other packages as well.\n\n###Additions\n\nWith grunt-vows-runner you can\n\n* Use grunt [tasks](http://gruntjs.com/configuring-tasks) and [templates](http://gruntjs.com/configuring-tasks#templates).\n* Run suites in the same [target](http://gruntjs.com/configuring-tasks#task-configuration-and-targets)\nconcurrently.\n* Set options at the target level.\n* Disable groups of tests at the target level\n\n###Differences from the vows command-line runner\n\n* Uses grunt to specify which [files](http://gruntjs.com/configuring-tasks#files) to run\n* Uses grunt's ``watch`` task instead of vows' built-in watch implementation\n* No shuffle option (if you want this, let me know--it is easy to implement)\n* No built-in js-coverage support\n * I highly recommend [istanbul](https://github.com/yahoo/istanbul), which does not need the cooperation of the test-runner\n (simply ``istanbul cover bin/vows`` will work ); and it is written in javascript, not java\n* No 'isolate' option.  If your system-under-test uses process.cwd, process.argv, or process.exit,\nit is best to create a [child process](http://nodejs.org/api/child_process.html) in the test topic.\n\n###Installation\n\n1. Change directories to the root directory of your project\n2. ``npm install grunt-vows-runner``\n\n###Usage\n\nAdd the following line to your ``Gruntfile.js``\n\n    grunt.loadNpmTasks('grunt-vows-runner');\n\nThe ``vows`` task is now available; for example\n\n    grunt vows\n\n###Configuration\n\nConfiguration is placed in the ``grunt.initConfig`` section of your ``Gruntfile.js`` file in the ``vows`` object.\n\n``vows`` is a [multitask](http://gruntjs.com/creating-tasks#multi-tasks).\n\nEach target references one or more source files containing suites and may contain options which will be applied to all of those\nsuites.\n\nAn example ``vows`` configuration with two targets:\n\n    ...\n    vows : {\n      all : {\n        src : \"<%= allTests %>\",\n        options : {\n          reporter : \"spec\"\n        }\n      },\n      allXunit : {\n        src : \"<%= allTests %>\",\n        dest : \"testResults.xml\"\n        options : {\n          reporter : \"xunit\"\n        }\n      }\n    },\n    allTests : \"tests/*\"\n    ...\n\nThe example above uses the [_compact format_ for specifying files](http://gruntjs.com/configuring-tasks#compact-format)\nas well as [templates](http://gruntjs.com/configuring-tasks#templates).\n\nOne destination file (``dest``) can be specified per target.  It will contain the output of all the suites in the target.  If no\ndestination file is specified, the output will go to the console.\n\nPaths for both source and destination files are relative to the directory that the ``Gruntfile.js`` is in.\n\nResults are summed by target.  Grunt-vows-runner doesn't combine the results of multiple targets.\n\nSuites within a target are run concurrently; faster suites will finish first.  Targets in grunt are always run sequentially.\n\n####Options\n\nOptions can be placed at the task (``vows``), target, or suite level.\n\nHere is an example of each:\n\n_Gruntfile.js_ (task- and target-level options)\n\n    ...\n    vows : {\n      options : {\n        reporter : \"spec\"\n      },\n      most : {\n        src : [\"test/*\", \"!test/chattyTests.js\"]\n      },\n      chatty : {\n        src : \"test/chattyTests.js\",\n        options : {\n          reporter : \"silent\"\n        }\n      }\n    }\n    ...\n\n_test/errorTests.js_ (suite-level options)\n\n    ...\n    vows.describe('Error Handling').addBatch({\n    ...\n    }).export(module, {error : false});\n    ...\n\nThe following options are available:\n\n* ``error``\n * Whether or not vows should handle errors in topics for you.  Set ``error : false`` if you want to handle your own errors.\n The first argument to your vows will be reserved for errors.\n* ``reporter``\n * silent, spec, json, tap, xunit, dot-matrix.  (Look in [vows/lib/vows/reporters](https://github.com/cloudhead/vows/tree/master/lib/vows/reporters)\n  for a complete list.)\n* ``matcher``\n * a javascript [RegExp object](http://www.w3schools.com/jsref/jsref_obj_regexp.asp); only run tests whose titles match this\n object.\n* ``disabled``\n * Temporarily disable tests for a target.\n\n###Command-Line Options\n\ngrunt-vows-runner incorporates the following grunt command-line options, if present:\n\n* ``--no-color``\n* ``--verbose``\n\n###Alternatives\n\nIf you would like a grunt plugin that simply forwards options to the existing vows command-line runner,\nsee [grunt-vows](https://github.com/CMTegner/grunt-vows).\n\n","readmeFilename":"README.md","_id":"grunt-vows-runner@0.1.1","dist":{"shasum":"d2b229fe75ee38bb8dda030acd4bb2e38c29b5f9","tarball":"https://registry.npmjs.org/grunt-vows-runner/-/grunt-vows-runner-0.1.1.tgz","integrity":"sha512-Wxz99YKRdIi9b/2uhra1THlXDg5tpWLNUw/Q/CPwkZ4mD02Leoo8uE6nHleYYN45wzRxHufuBXYfAn5uIts1hA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQC5kTIVVTSGbXa9zgDBKdRltdDMgfBh/10+Xv7stWaSTQIgcfoAiSyKf08TN44RlUf/lE10V7ad5keynyyB2HyMSl4="}]},"_npmVersion":"1.1.69","_npmUser":{"name":"adamstallard","email":"adam@sweedl.com"},"maintainers":[{"name":"adamstallard","email":"adam@sweedl.com"}]},"0.1.2":{"name":"grunt-vows-runner","version":"0.1.2","description":"An alternative test-runner for vows using grunt.  Adds new capabilities such as running test suites concurrently.","keywords":["vows","test","testing","runner","task","gruntplugin","grunt","bdd","concurrent","asynchronous","parallel"],"author":{"name":"Adam Stallard","email":"adam@goalzen.org","url":"goalzen.org"},"directories":{"test":"test"},"dependencies":{"vows":"*","grunt":"~0.4","underscore":"*"},"license":{"type":"MIT","url":"https://github.com/goalzen/grunt-vows-runner/blob/master/LICENSE-MIT"},"engines":{"node":">=0.8.0"},"scripts":{"test":"grunt"},"repository":{"type":"git","url":"https://github.com/goalzen/grunt-vows-runner.git"},"bugs":{"url":"https://github.com/goalzen/grunt-vows-runner/issues"},"homepage":"https://github.com/goalzen/grunt-vows-runner.git","readme":"##grunt-vows-runner\n\n[![Build Status](https://travis-ci.org/goalzen/grunt-vows-runner.png?branch=master)](https://travis-ci.org/goalzen/grunt-vows-runner)\n\nAn alternative test-runner for vows using [grunt](http://gruntjs.com/).\n\n###Philosophy\n\nFile and directory matching, file watching, coverage reporting, etc. should be supplied by third-party tools where possible.\nGrunt is a great source of such third-party-tools.  These are much more likely to continue development than the equivalent\ntools built into vows, since they are used by many other packages as well.\n\n###Additions\n\nWith grunt-vows-runner you can\n\n* Use grunt [targets](http://gruntjs.com/configuring-tasks#task-configuration-and-targets) and\n[templates](http://gruntjs.com/configuring-tasks#templates).\n* Run suites in the same target concurrently.\n* Set different options for each target.\n* Have each target output to a different file (or the console).\n* Disable groups of tests at the target level.\n\n###Differences from the vows command-line runner\n\n* Uses grunt to specify which [files](http://gruntjs.com/configuring-tasks#files) to run.\n* Uses grunt's ``watch`` task instead of vows' built-in watch implementation.\n* No shuffle option (if you want this, let me know--it is easy to implement).\n* No built-in js-coverage support.\n * I highly recommend [istanbul](https://github.com/yahoo/istanbul), which does not need the cooperation of the test-runner\n (simply ``istanbul cover bin/vows`` will work ); and it is written in javascript, not java.\n* No 'isolate' option.  If your system-under-test uses process.cwd, process.argv, or process.exit,\nit is best to create a [child process](http://nodejs.org/api/child_process.html) in the test topic.\n\n###Installation\n\n1. Change directories to the root directory of your project\n2. ``npm install grunt-vows-runner``\n\n###Usage\n\nAdd the following line to your ``Gruntfile.js``\n\n    grunt.loadNpmTasks('grunt-vows-runner');\n\nThe ``vows`` task is now available; for example\n\n    grunt vows\n\n###Configuration\n\nConfiguration is placed in the ``grunt.initConfig`` section of your ``Gruntfile.js`` file in the ``vows`` object.\n\n``vows`` is a [multitask](http://gruntjs.com/creating-tasks#multi-tasks).\n\nEach target references one or more source files containing suites and may contain options which will be applied to all of those\nsuites.\n\nAn example ``vows`` configuration with two targets:\n\n    ...\n    vows : {\n      all : {\n        src : \"<%= allTests %>\",\n        options : {\n          reporter : \"spec\"\n        }\n      },\n      allXunit : {\n        src : \"<%= allTests %>\",\n        dest : \"testResults.xml\"\n        options : {\n          reporter : \"xunit\"\n        }\n      }\n    },\n    allTests : \"tests/*\"\n    ...\n\nThe example above uses the [_compact format_ for specifying files](http://gruntjs.com/configuring-tasks#compact-format)\nas well as [templates](http://gruntjs.com/configuring-tasks#templates).\n\nOne destination file (``dest``) can be specified per target.  It will contain the output of all the suites in the target.  If no\ndestination file is specified, the output will go to the console.\n\nPaths for both source and destination files are relative to the location of ``Gruntfile.js``.\n\nResults are summed by target.  Grunt-vows-runner doesn't combine the results of multiple targets.\n\nSuites within a target are run concurrently; faster suites will finish first.  Targets in grunt are always run sequentially.\n\n####Options\n\nOptions can be placed at the task (``vows``), target, or suite level.\n\nHere is an example of each:\n\n_Gruntfile.js_ (task- and target-level options)\n\n    ...\n    vows : {\n      options : {\n        reporter : \"spec\"\n      },\n      most : {\n        src : [\"test/*\", \"!test/chattyTests.js\"]\n      },\n      chatty : {\n        src : \"test/chattyTests.js\",\n        options : {\n          reporter : \"silent\"\n        }\n      }\n    }\n    ...\n\n_test/errorTests.js_ (suite-level options)\n\n    ...\n    vows.describe('Error Handling').addBatch({\n    ...\n    }).export(module, {error : false});\n    ...\n\nThe following options are available:\n\n* ``error``\n * Whether or not vows should handle errors in topics for you.  Set ``error : false`` if you want to handle your own errors.\n The first argument to your vows will be reserved for errors.\n* ``reporter``\n * silent, spec, json, tap, xunit, dot-matrix.  (Look in [vows/lib/vows/reporters](https://github.com/cloudhead/vows/tree/master/lib/vows/reporters)\n  for a complete list.)\n* ``matcher``\n * a javascript [RegExp object](http://www.w3schools.com/jsref/jsref_obj_regexp.asp); only run tests whose titles match this\n object.\n* ``disabled``\n * Temporarily disable tests for a target.\n\n###Command-Line Options\n\ngrunt-vows-runner incorporates the following grunt command-line options, if present:\n\n* ``--no-color``\n* ``--verbose``\n\n###Alternatives\n\nIf you would like a grunt plugin that forwards options to the existing vows command-line runner,\nsee [grunt-vows](https://github.com/CMTegner/grunt-vows).\n\n","readmeFilename":"README.md","_id":"grunt-vows-runner@0.1.2","dist":{"shasum":"bd5c40f8e5fa6ad351664e7e3ac0d40701f87b25","tarball":"https://registry.npmjs.org/grunt-vows-runner/-/grunt-vows-runner-0.1.2.tgz","integrity":"sha512-gsdX0eOvZcqhUEGe2q1zK5Z63w4PfUD358PMWauMezp9COcA3Abk4KPBqVITVPtHhqsZIwb0hrnAEO47n2BbHA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIC5B6hB85je8nqca6ZVwJ7BWIwUsFtBpQkb55TR8BuhhAiEA2rSJPqFwlw0yRlTPmAacLtm1rFDxvX0X7eYWrm6jd9A="}]},"_npmVersion":"1.1.69","_npmUser":{"name":"adamstallard","email":"adam@sweedl.com"},"maintainers":[{"name":"adamstallard","email":"adam@sweedl.com"}]},"0.1.3":{"name":"grunt-vows-runner","version":"0.1.3","description":"An alternative test-runner for vows using grunt.  Adds new capabilities such as running test suites concurrently.","keywords":["vows","test","testing","runner","task","gruntplugin","grunt","bdd","concurrent","asynchronous","parallel"],"author":{"name":"Adam Stallard","email":"adam@goalzen.org","url":"goalzen.org"},"directories":{"test":"test"},"dependencies":{"vows":"*","grunt":"~0.4","underscore":"*","vows-reporters":"*"},"license":{"type":"MIT","url":"https://github.com/goalzen/grunt-vows-runner/blob/master/LICENSE-MIT"},"engines":{"node":">=0.8.0"},"scripts":{"test":"grunt"},"repository":{"type":"git","url":"https://github.com/goalzen/grunt-vows-runner.git"},"bugs":{"url":"https://github.com/goalzen/grunt-vows-runner/issues"},"homepage":"https://github.com/goalzen/grunt-vows-runner.git","readme":"##grunt-vows-runner\n\n[![Build Status](https://travis-ci.org/goalzen/grunt-vows-runner.png?branch=master)](https://travis-ci.org/goalzen/grunt-vows-runner)\n\nAn alternative test-runner for vows using [grunt](http://gruntjs.com/).\n\n###Philosophy\n\nFile and directory matching, file watching, coverage reporting, etc. should be supplied by third-party tools where possible.\nGrunt is a great source of such third-party-tools.  These are much more likely to continue development than the equivalent\ntools built into vows, since they are used by many other packages as well.\n\n###Additions\n\nWith grunt-vows-runner you can\n\n* Use grunt [targets](http://gruntjs.com/configuring-tasks#task-configuration-and-targets) and\n[templates](http://gruntjs.com/configuring-tasks#templates).\n* Run suites in the same target concurrently.\n* Set different options for each target.\n* Have each target output to a different file (or the console).\n* Disable groups of tests at the target level.\n\n###Differences from the vows command-line runner\n\n* Uses grunt to specify which [files](http://gruntjs.com/configuring-tasks#files) to run.\n* Uses grunt's ``watch`` task instead of vows' built-in watch implementation.\n* No shuffle option (if you want this, let me know--it is easy to implement).\n* No built-in js-coverage support.\n * I highly recommend [istanbul](https://github.com/yahoo/istanbul), which does not need the cooperation of the test-runner\n (simply ``istanbul cover bin/vows`` will work ); and it is written in javascript, not java.\n* No 'isolate' option.  If your system-under-test uses process.cwd, process.argv, or process.exit,\nit is best to create a [child process](http://nodejs.org/api/child_process.html) in the test topic.\n\n###Installation\n\n1. Change directories to the root directory of your project\n2. ``npm install grunt-vows-runner``\n\n###Usage\n\nAdd the following line to your ``Gruntfile.js``\n\n    grunt.loadNpmTasks('grunt-vows-runner');\n\nThe ``vows`` task is now available; for example\n\n    grunt vows\n\n###Configuration\n\nConfiguration is placed in the ``grunt.initConfig`` section of your ``Gruntfile.js`` file in the ``vows`` object.\n\n``vows`` is a [multitask](http://gruntjs.com/creating-tasks#multi-tasks).\n\nEach target references one or more source files containing suites and may contain options which will be applied to all of those\nsuites.\n\nAn example ``vows`` configuration with two targets:\n\n    ...\n    vows : {\n      all : {\n        src : \"<%= allTests %>\",\n        options : {\n          reporter : \"spec\"\n        }\n      },\n      allXunit : {\n        src : \"<%= allTests %>\",\n        dest : \"testResults.xml\"\n        options : {\n          reporter : \"xunit\"\n        }\n      }\n    },\n    allTests : \"tests/*\"\n    ...\n\nThe example above uses the [_compact format_ for specifying files](http://gruntjs.com/configuring-tasks#compact-format)\nas well as [templates](http://gruntjs.com/configuring-tasks#templates).\n\nOne destination file (``dest``) can be specified per target.  It will contain the output of all the suites in the target.  If no\ndestination file is specified, the output will go to the console.\n\nPaths for both source and destination files are relative to the location of ``Gruntfile.js``.\n\nResults are summed by target.  Grunt-vows-runner doesn't combine the results of multiple targets.\n\nSuites within a target are run concurrently; faster suites will finish first.  Targets in grunt are always run sequentially.\n\n####Options\n\nOptions can be placed at the task (``vows``), target, or suite level.\n\nHere is an example of each:\n\n_Gruntfile.js_ (task- and target-level options)\n\n    ...\n    vows : {\n      options : {\n        reporter : \"spec\"\n      },\n      most : {\n        src : [\"test/*\", \"!test/chattyTests.js\"]\n      },\n      chatty : {\n        src : \"test/chattyTests.js\",\n        options : {\n          reporter : \"silent\"\n        }\n      }\n    }\n    ...\n\n_test/errorTests.js_ (suite-level options)\n\n    ...\n    vows.describe('Error Handling').addBatch({\n    ...\n    }).export(module, {error : false});\n    ...\n\nThe following options are available:\n\n* ``error``\n * Whether or not vows should handle errors in topics for you.  Set ``error : false`` if you want to handle your own errors.\n The first argument to your vows will be reserved for errors.\n* ``reporter``\n * silent, spec, json, tap, xunit, dot-matrix.  (Look in [vows/lib/vows/reporters](https://github.com/cloudhead/vows/tree/master/lib/vows/reporters)\n  for a complete list.)\n* ``matcher``\n * a javascript [RegExp object](http://www.w3schools.com/jsref/jsref_obj_regexp.asp); only run tests whose titles match this\n object.\n* ``disabled``\n * Temporarily disable tests for a target.\n\n###Command-Line Options\n\ngrunt-vows-runner incorporates the following grunt command-line options, if present:\n\n* ``--no-color``\n* ``--verbose``\n\n###Alternatives\n\nIf you would like a grunt plugin that forwards options to the existing vows command-line runner,\nsee [grunt-vows](https://github.com/CMTegner/grunt-vows).\n\n","readmeFilename":"README.md","_id":"grunt-vows-runner@0.1.3","dist":{"shasum":"cfac00b477bb036214dc63058458d7b79b9d9a86","tarball":"https://registry.npmjs.org/grunt-vows-runner/-/grunt-vows-runner-0.1.3.tgz","integrity":"sha512-AjvanH4BQVuXkSVpTGr1E2pPqOBYCAVdAqntuqkDkk1ljMPylrAaGcypzOOul1EYEk7M6XwVgjkRoJbDn/JU6w==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIGRmGI4J9PMGLK2+ed3VlIbT69nbxAnJvh9GlBok77r3AiEA8x+zS45WJPCjdOvAm0DI6WFD0h3wLkYCM9HtTVUTYZg="}]},"_npmVersion":"1.1.69","_npmUser":{"name":"adamstallard","email":"adam@sweedl.com"},"maintainers":[{"name":"adamstallard","email":"adam@sweedl.com"}]},"0.2.0":{"name":"grunt-vows-runner","version":"0.2.0","description":"An alternative test-runner for vows using grunt.  Adds new capabilities such as running test suites concurrently.","keywords":["vows","test","testing","runner","task","gruntplugin","grunt","bdd","concurrent","asynchronous","parallel"],"author":{"name":"Adam Stallard","email":"adam@goalzen.org","url":"goalzen.org"},"directories":{"test":"test"},"dependencies":{"vows":"*","grunt":"~0.4","underscore":"*","vows-reporters":"*"},"license":{"type":"MIT","url":"https://github.com/goalzen/grunt-vows-runner/blob/master/LICENSE-MIT"},"engines":{"node":">=0.8.0"},"scripts":{"test":"grunt"},"repository":{"type":"git","url":"https://github.com/goalzen/grunt-vows-runner.git"},"bugs":{"url":"https://github.com/goalzen/grunt-vows-runner/issues"},"homepage":"https://github.com/goalzen/grunt-vows-runner.git","readme":"##grunt-vows-runner\n\n[![Build Status](https://travis-ci.org/goalzen/grunt-vows-runner.png?branch=master)](https://travis-ci.org/goalzen/grunt-vows-runner)\n\nAn alternative test-runner for vows using [grunt](http://gruntjs.com/).\n\n###Philosophy\n\nFile and directory matching, file watching, coverage reporting, etc. should be supplied by third-party tools where possible.\nGrunt is a great source of such third-party-tools.  These are much more likely to continue development than the equivalent\ntools built into vows, since they are used by many other packages as well.\n\n###Additions\n\nWith grunt-vows-runner you can\n\n* Use grunt [targets](http://gruntjs.com/configuring-tasks#task-configuration-and-targets) and\n[templates](http://gruntjs.com/configuring-tasks#templates).\n* Run suites in the same target concurrently.\n* Set different options for each target.\n* Have each target output to a different file (or the console).\n* Disable groups of tests at the target level.\n\n###Differences from the vows command-line runner\n\n* Uses grunt to specify which [files](http://gruntjs.com/configuring-tasks#files) to run.\n* Uses grunt's ``watch`` task instead of vows' built-in watch implementation.\n* No shuffle option (if you want this, let me know--it is easy to implement).\n* No built-in js-coverage support.\n * I highly recommend [istanbul](https://github.com/yahoo/istanbul), which does not need the cooperation of the test-runner\n (simply ``istanbul cover bin/vows`` will work ); and it is written in javascript, not java.\n* No 'isolate' option.  If your system-under-test uses process.cwd, process.argv, or process.exit,\nit is best to create a [child process](http://nodejs.org/api/child_process.html) in the test topic.\n\n###Installation\n\n1. Change directories to the root directory of your project\n2. ``npm install grunt-vows-runner``\n\n###Usage\n\nAdd the following line to your ``Gruntfile.js``\n\n    grunt.loadNpmTasks('grunt-vows-runner');\n\nThe ``vows`` task is now available; for example\n\n    grunt vows\n\n###Configuration\n\nConfiguration is placed in the ``grunt.initConfig`` section of your ``Gruntfile.js`` file in the ``vows`` object.\n\n``vows`` is a [multitask](http://gruntjs.com/creating-tasks#multi-tasks).\n\nEach target references one or more source files containing suites and may contain options which will be applied to all of those\nsuites.\n\nAn example ``vows`` configuration with two targets:\n\n    ...\n    vows : {\n      all : {\n        src : \"<%= allTests %>\",\n        options : {\n          reporter : \"spec\"\n        }\n      },\n      allXunit : {\n        src : \"<%= allTests %>\",\n        dest : \"testResults.xml\"\n        options : {\n          reporter : \"xunit\"\n        }\n      }\n    },\n    allTests : \"tests/*\"\n    ...\n\nThe example above uses the [_compact format_ for specifying files](http://gruntjs.com/configuring-tasks#compact-format)\nas well as [templates](http://gruntjs.com/configuring-tasks#templates).\n\nOne destination file (``dest``) can be specified per target.  It will contain the output of all the suites in the target.  If no\ndestination file is specified, the output will go to the console.\n\nPaths for both source and destination files are relative to the location of ``Gruntfile.js``.\n\nResults are summed by target.  Grunt-vows-runner doesn't combine the results of multiple targets.\n\nSuites within a target are run concurrently; faster suites will finish first.  Targets in grunt are always run sequentially.\n\n####Options\n\nOptions can be placed at the task (``vows``), target, or suite level.\n\nHere is an example of each:\n\n_Gruntfile.js_ (task- and target-level options)\n\n    ...\n    vows : {\n      options : {\n        reporter : \"spec\"\n      },\n      most : {\n        src : [\"test/*\", \"!test/chattyTests.js\"]\n      },\n      chatty : {\n        src : \"test/chattyTests.js\",\n        options : {\n          reporter : \"silent\"\n        }\n      }\n    }\n    ...\n\n_test/errorTests.js_ (suite-level options)\n\n    ...\n    vows.describe('Error Handling').addBatch({\n    ...\n    }).export(module, {error : false});\n    ...\n\nThe following options are available:\n\n* ``error``\n * Whether or not vows should handle errors in topics for you.  Set ``error : false`` if you want to handle your own errors.\n The first argument to your vows will be reserved for errors.\n* ``reporter``\n * silent, spec, json, tap, xunit, dot-matrix.  (Look in [vows/lib/vows/reporters](https://github.com/cloudhead/vows/tree/master/lib/vows/reporters)\n  for a complete list.)\n* ``matcher``\n * a javascript [RegExp object](http://www.w3schools.com/jsref/jsref_obj_regexp.asp); only run tests whose titles match this\n object.\n* ``disabled``\n * Temporarily disable tests for a target.\n\n###Command-Line Options\n\ngrunt-vows-runner incorporates the following grunt command-line options, if present:\n\n* ``--no-color``\n* ``--verbose``\n\n###Alternatives\n\nIf you would like a grunt plugin that forwards options to the existing vows command-line runner,\nsee [grunt-vows](https://github.com/CMTegner/grunt-vows).\n\n","readmeFilename":"README.md","_id":"grunt-vows-runner@0.2.0","dist":{"shasum":"cd8c91414409243166d1a454b55d6c4b1b7228b3","tarball":"https://registry.npmjs.org/grunt-vows-runner/-/grunt-vows-runner-0.2.0.tgz","integrity":"sha512-7oMMXen/YEAJzhAFp5v2vXc1ZQXLM6MFNSNY1rqq92lAeMBjkza9FE7Az63n+sR1Vcjhu1YextLRiRaR0sLm/g==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQC623BhuW2NFdZq1KnOJiuuYBLIDPwGtXET+t+Me7p2vgIhAKtGknqrGLb70ugk9pV2uBKSsi3dRQlWgb5Ry9FQp/EX"}]},"_npmVersion":"1.1.69","_npmUser":{"name":"adamstallard","email":"adam@sweedl.com"},"maintainers":[{"name":"adamstallard","email":"adam@sweedl.com"}]},"0.2.1":{"name":"grunt-vows-runner","version":"0.2.1","description":"An alternative test-runner for vows using grunt.  Adds new capabilities such as running test suites concurrently.","keywords":["vows","test","testing","runner","task","gruntplugin","grunt","bdd","concurrent","asynchronous","parallel"],"author":{"name":"Adam Stallard","email":"adam@goalzen.org","url":"goalzen.org"},"directories":{"test":"test"},"dependencies":{"vows":"*","grunt":"~0.4","underscore":"*","vows-reporters":"*"},"license":{"type":"MIT","url":"https://github.com/goalzen/grunt-vows-runner/blob/master/LICENSE-MIT"},"engines":{"node":">=0.8.0"},"scripts":{"test":"grunt"},"repository":{"type":"git","url":"https://github.com/goalzen/grunt-vows-runner.git"},"bugs":{"url":"https://github.com/goalzen/grunt-vows-runner/issues"},"homepage":"https://github.com/goalzen/grunt-vows-runner.git","readme":"##grunt-vows-runner\n\n[![Build Status](https://travis-ci.org/goalzen/grunt-vows-runner.png?branch=master)](https://travis-ci.org/goalzen/grunt-vows-runner)\n\nAn alternative test-runner for vows using [grunt](http://gruntjs.com/).\n\n###Philosophy\n\nFile and directory matching, file watching, coverage reporting, etc. should be supplied by third-party tools where possible.\nGrunt is a great source of such third-party-tools.  These are much more likely to continue development than the equivalent\ntools built into vows, since they are used by many other packages as well.\n\n###Additions\n\nWith grunt-vows-runner you can\n\n* Use grunt [targets](http://gruntjs.com/configuring-tasks#task-configuration-and-targets) and\n[templates](http://gruntjs.com/configuring-tasks#templates).\n* [Match files](http://gruntjs.com/configuring-tasks#globbing-patterns) using grunt's node-glob and minimatch support.\n* Run suites in the same target concurrently.\n* Set different options for each target.\n* Have each target output to a different file (or the console).\n* Disable groups of tests at the target level.\n\n###Differences from the vows command-line runner\n\n* Use grunt to specify which [files](http://gruntjs.com/configuring-tasks#files) to run.\n* Use grunt's ``watch`` task.\n* No shuffle option (if you want this, let me know--it is easy to implement).\n* No built-in js-coverage support.\n * I highly recommend [istanbul](https://github.com/yahoo/istanbul), which does not need the cooperation of the test-runner\n (simply ``istanbul cover bin/vows`` will work ); and it is written in javascript, not java.\n* No 'isolate' option.  If your system-under-test uses process.cwd, process.argv, or process.exit,\nit is best to create a [child process](http://nodejs.org/api/child_process.html) in the test topic.\n\n###Installation\n\n1. Change directories to the root directory of your project\n2. ``npm install grunt``\n3. ``npm install grunt-vows-runner``\n4. Add the following line to your ``Gruntfile.js``\n   \n   ``grunt.loadNpmTasks('grunt-vows-runner');``\n\nThe ``vows`` task is now available; for example\n\n    grunt vows\n\n###Configuration\n\nConfiguration is placed in the ``grunt.initConfig`` section of your ``Gruntfile.js`` file in the ``vows`` object.\n\n``vows`` is a [multitask](http://gruntjs.com/creating-tasks#multi-tasks).\n\nEach target references one or more source files containing suites and may contain options which will be applied to all of those\nsuites.\n\nAn example ``vows`` configuration with two targets:\n\n    ...\n    vows : {\n      all : {\n        src : \"<%= allTests %>\",\n        options : {\n          reporter : \"spec\"\n        }\n      },\n      allXunit : {\n        src : \"<%= allTests %>\",\n        dest : \"testResults.xml\"\n        options : {\n          reporter : \"Xunit\"\n        }\n      }\n    },\n    allTests : \"tests/*\"\n    ...\n\nThe example above uses the [_compact format_ for specifying files](http://gruntjs.com/configuring-tasks#compact-format)\nas well as [templates](http://gruntjs.com/configuring-tasks#templates).\n\nOne destination file (``dest``) can be specified per target.  It will contain the output of all the suites in the target.  If no\ndestination file is specified, the output will go to the console.\n\nPaths for both source and destination files are relative to the location of ``Gruntfile.js``.\n\nResults are summed by target.  Grunt-vows-runner doesn't combine the results of multiple targets.\n\nSuites within a target are run concurrently; faster suites will finish first.  Targets in grunt are always run sequentially.\n\n####Options\n\nOptions can be placed at the task (``vows``), target, or suite level.\n\nHere is an example of each:\n\n_Gruntfile.js_ (task- and target-level options) -- the reporter is set at the task-level\n\n    ...\n    vows : {\n      options : {\n        reporter : \"spec\"\n      },\n      most : {\n        src : [\"test/*\", \"!test/errorTests.js\"]\n      },\n      error : {\n        src : \"test/errorTests.js\",\n        options : {\n          error : false\n        }\n      }\n    }\n    ...\n\n_test/errorTests.js_ (suite-level options) -- this is a different way to accomplish the same as above\n\n    ...\n    vows.describe('Error Handling').addBatch({\n    ...\n    }).export(module, {error : false});\n    ...\n\nThe following options are available:\n\n* ``error``\n * Whether or not vows should handle errors in topics for you.  Set ``error : false`` if you want to handle your own errors.\n The first argument to your vows will be reserved for errors.\n* ``reporter``\n * [See the list of reporters](#reporters)\n* ``matcher``\n * a javascript [RegExp object](http://www.w3schools.com/jsref/jsref_obj_regexp.asp); only run tests whose titles match this\n object.\n* ``disabled``\n * Temporarily disable tests for a target.\n\n####Reporters<a id=\"reporters\"/>\n\nFrom the [vows-reporters package](https://github.com/goalzen/vows-reporters):\n\n* spec\n* Xunit\n\nFrom [vows](https://github.com/cloudhead/vows/tree/master/lib/vows/reporters)\n\n* tap\n* dot-matrix\n\n###Command-Line Options\n\ngrunt-vows-runner incorporates the following grunt command-line options, if present:\n\n* ``--no-color``\n* ``--verbose``\n\n###Bugs, etc.\n\nPlease report any bugs, feature requests, etc. to [grunt-vows-runner's github issue tracker](https://github.com/goalzen/grunt-vows-runner/issues).\n\n","readmeFilename":"README.md","_id":"grunt-vows-runner@0.2.1","dist":{"shasum":"6daa7e74f913996c273745e4edc8e2eacef9d0ef","tarball":"https://registry.npmjs.org/grunt-vows-runner/-/grunt-vows-runner-0.2.1.tgz","integrity":"sha512-rIc0qDAg1e+VzqwlFhtGFA2+xeTXcJl49u4N7HAGoKn/YUxBbbAU+JJs6i7Fw1ZBQFSuwhg2KqsKEpUtNkz4zw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCqT9S7Aql7fy0ed0LbJ2hH6AKT1FqXxszky9tr7J/JaQIhALMaLvnsqkxFMLunCTP7+0Jk+3olD0/Lf8pOukVbJdfa"}]},"_npmVersion":"1.1.69","_npmUser":{"name":"adamstallard","email":"adam@sweedl.com"},"maintainers":[{"name":"adamstallard","email":"adam@sweedl.com"}]},"0.3.0":{"name":"grunt-vows-runner","version":"0.3.0","description":"An alternative test-runner for vows using grunt.  Adds new capabilities such as running test suites concurrently.","keywords":["vows","test","testing","runner","task","gruntplugin","grunt","bdd","concurrent","asynchronous","parallel"],"author":{"name":"Adam Stallard","email":"adam@goalzen.org","url":"goalzen.org"},"directories":{"test":"test"},"dependencies":{"vows":"*","grunt":"~0.4","underscore":"*","vows-reporters":">=0.7.0"},"license":{"type":"MIT","url":"https://github.com/goalzen/grunt-vows-runner/blob/master/LICENSE-MIT"},"engines":{"node":">=0.8.0"},"scripts":{"test":"grunt"},"repository":{"type":"git","url":"https://github.com/goalzen/grunt-vows-runner.git"},"bugs":{"url":"https://github.com/goalzen/grunt-vows-runner/issues"},"homepage":"https://github.com/goalzen/grunt-vows-runner.git","readme":"##grunt-vows-runner\n\n[![Build Status](https://travis-ci.org/goalzen/grunt-vows-runner.png?branch=master)](https://travis-ci.org/goalzen/grunt-vows-runner)\n\nAn alternative test-runner for vows using [grunt](http://gruntjs.com/).\n\n###Philosophy\n\nFile and directory matching, file watching, coverage reporting, etc. should be supplied by third-party tools where possible.\nGrunt is a great source of such third-party-tools.  These are much more likely to continue development than the equivalent\ntools built into vows, since they are used by many other packages as well.\n\n###Additions\n\nWith grunt-vows-runner you can\n\n* Use grunt [targets](http://gruntjs.com/configuring-tasks#task-configuration-and-targets) and\n[templates](http://gruntjs.com/configuring-tasks#templates).\n* [Match files](http://gruntjs.com/configuring-tasks#globbing-patterns) using grunt's node-glob and minimatch support.\n* Run suites in the same target concurrently.\n* Set different options for each target.\n* Have each target output to a different file (or the console).\n* Disable groups of tests at the target level.\n\n###Differences from the vows command-line runner\n\n* Use grunt to specify which [files](http://gruntjs.com/configuring-tasks#files) to run.\n* Use grunt's ``watch`` task.\n* No shuffle option (if you want this, let me know--it is easy to implement).\n* No built-in js-coverage support.\n * I highly recommend [istanbul](https://github.com/yahoo/istanbul), which does not need the cooperation of the test-runner\n (simply ``istanbul cover bin/vows`` will work ); and it is written in javascript, not java.\n* No 'isolate' option.  If your system-under-test uses process.cwd, process.argv, or process.exit,\nit is best to create a [child process](http://nodejs.org/api/child_process.html) in the test topic.\n\n###Installation\n\n1. Change directories to the root directory of your project\n2. ``npm install grunt``\n3. ``npm install grunt-vows-runner``\n4. Add the following line to your ``Gruntfile.js``\n   \n   ``grunt.loadNpmTasks('grunt-vows-runner');``\n\nThe ``vows`` task is now available; for example\n\n    grunt vows\n\n###Configuration\n\nConfiguration is placed in the ``grunt.initConfig`` section of your ``Gruntfile.js`` file in the ``vows`` object.\n\n``vows`` is a [multitask](http://gruntjs.com/creating-tasks#multi-tasks).\n\nEach target references one or more source files containing suites and may contain options which will be applied to all of those\nsuites.\n\nAn example ``vows`` configuration with two targets:\n\n    ...\n    vows : {\n      all : {\n        src : \"<%= allTests %>\",\n        options : {\n          reporter : \"spec\"\n        }\n      },\n      allXunit : {\n        src : \"<%= allTests %>\",\n        dest : \"testResults.xml\"\n        options : {\n          reporter : \"Xunit\"\n        }\n      }\n    },\n    allTests : \"tests/*\"\n    ...\n\nThe example above uses the [_compact format_ for specifying files](http://gruntjs.com/configuring-tasks#compact-format)\nas well as [templates](http://gruntjs.com/configuring-tasks#templates).\n\nOne destination file (``dest``) can be specified per target.  It will contain the output of all the suites in the target.  If no\ndestination file is specified, the output will go to the console.\n\nPaths for both source and destination files are relative to the location of ``Gruntfile.js``.\n\nResults are summed by target.  Grunt-vows-runner doesn't combine the results of multiple targets.\n\nSuites within a target are run concurrently; faster suites will finish first.  Targets in grunt are always run sequentially.\n\n####Options\n\nOptions can be placed at the task (``vows``), target, or suite level.\n\nHere is an example of each:\n\n_Gruntfile.js_ (task- and target-level options) -- the reporter is set at the task-level\n\n    ...\n    vows : {\n      options : {\n        reporter : \"spec\"\n      },\n      most : {\n        src : [\"test/*\", \"!test/errorTests.js\"]\n      },\n      error : {\n        src : \"test/errorTests.js\",\n        options : {\n          error : false\n        }\n      }\n    }\n    ...\n\n_test/errorTests.js_ (suite-level options) -- this is a different way to accomplish the same as above\n\n    ...\n    vows.describe('Error Handling').addBatch({\n    ...\n    }).export(module, {error : false});\n    ...\n\nThe following options are available:\n\n* ``error``\n * Whether or not vows should handle errors in topics for you.  Set ``error : false`` if you want to handle your own errors.\n The first argument to your vows will be reserved for errors.\n* ``reporter``\n * [See the list of reporters](#reporters)\n* ``matcher``\n * a javascript [RegExp object](http://www.w3schools.com/jsref/jsref_obj_regexp.asp); only run tests whose titles match this\n object.\n* ``disabled``\n * Temporarily disable tests for a target.\n\n####Reporters<a id=\"reporters\"/>\n\nFrom the [vows-reporters package](https://github.com/goalzen/vows-reporters):\n\n* spec\n* Xunit\n\nFrom [vows](https://github.com/cloudhead/vows/tree/master/lib/vows/reporters)\n\n* tap\n* dot-matrix\n\n###Command-Line Options\n\ngrunt-vows-runner incorporates the following grunt command-line options, if present:\n\n* ``--no-color``\n* ``--verbose``\n\n###Bugs, etc.\n\nPlease report any bugs, feature requests, etc. to [grunt-vows-runner's github issue tracker](https://github.com/goalzen/grunt-vows-runner/issues).\n\n","readmeFilename":"README.md","_id":"grunt-vows-runner@0.3.0","dist":{"shasum":"95e2e9394475cb2701f620ca4930ac9d0ca25cc2","tarball":"https://registry.npmjs.org/grunt-vows-runner/-/grunt-vows-runner-0.3.0.tgz","integrity":"sha512-5tcrvuRrlY3wMaoiWVjrZGsU77gD2vPabvKU6TvbN/cbjruOGpscbFBePBwLKXoooRhoaFyfC3VMpjR2KQL/iA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQD7HpZsXGTGkkTzcVV/4ov65RLCRU671anjURXTbcg7dgIgXNbBuRkPWNg1RF4/XCtsHvs0jIIVg9MjR2PDUM7KOnQ="}]},"_from":".","_npmVersion":"1.2.14","_npmUser":{"name":"adamstallard","email":"adam@sweedl.com"},"maintainers":[{"name":"adamstallard","email":"adam@sweedl.com"}]},"0.4.0":{"name":"grunt-vows-runner","version":"0.4.0","description":"An alternative test-runner for vows using grunt.  Adds new capabilities such as running test suites concurrently.","keywords":["vows","test","testing","runner","task","gruntplugin","grunt","bdd","concurrent","asynchronous","parallel"],"author":{"name":"Adam Stallard","email":"adam@goalzen.org","url":"goalzen.org"},"directories":{"test":"test"},"dependencies":{"vows":"*","underscore":"*"},"peerDependencies":{"grunt":"~0.4"},"devDependencies":{"chai":"*","grunt-contrib-jshint":"*"},"license":{"type":"MIT","url":"https://github.com/goalzen/grunt-vows-runner/blob/master/LICENSE-MIT"},"engines":{"node":">=0.8.0"},"scripts":{"test":"grunt"},"repository":{"type":"git","url":"https://github.com/goalzen/grunt-vows-runner.git"},"bugs":{"url":"https://github.com/goalzen/grunt-vows-runner/issues"},"homepage":"https://github.com/goalzen/grunt-vows-runner.git","readme":"##grunt-vows-runner\n\n[![Build Status](https://travis-ci.org/goalzen/grunt-vows-runner.png?branch=master)](https://travis-ci.org/goalzen/grunt-vows-runner)\n\nAn alternative test-runner for vows using [grunt](http://gruntjs.com/).\n\n###Philosophy\n\nFile and directory matching, file watching, coverage reporting, etc. should be supplied by third-party tools where possible.\nGrunt is a great source of such third-party-tools.  These are much more likely to continue development than the equivalent\ntools built into vows, since they are used by many other packages as well.\n\n###Additions\n\nWith grunt-vows-runner you can\n\n* Use grunt [targets](http://gruntjs.com/configuring-tasks#task-configuration-and-targets) and\n[templates](http://gruntjs.com/configuring-tasks#templates).\n* Run suites in the same target concurrently.\n* Set different options for each target.\n* Have each target output to a different file (or the console).\n* Disable groups of tests at the target level.\n\n###Differences from the vows command-line runner\n\n* Use grunt to specify which [files](http://gruntjs.com/configuring-tasks#files) to run.\n* Use grunt's ``watch`` task.\n* No shuffle option (if you want this, let me know--it is easy to implement).\n* No built-in js-coverage support.\n * I highly recommend [istanbul](https://github.com/yahoo/istanbul), which does not need the cooperation of the test-runner\n (simply ``istanbul cover bin/vows`` will work ); and it is written in javascript, not java.\n* No 'isolate' option.  If your system-under-test uses process.cwd, process.argv, or process.exit,\nit is best to create a [child process](http://nodejs.org/api/child_process.html) in the test topic.\n\n###Installation\n\n1. Change directories to the root directory of your project\n2. ``npm install grunt``\n3. ``npm install grunt-vows-runner``\n4. Add the following line to your ``Gruntfile.js``\n   \n   ``grunt.loadNpmTasks('grunt-vows-runner');``\n\nThe ``vows`` task is now available; for example\n\n    grunt vows\n\n###Configuration\n\nConfiguration is placed in the ``grunt.initConfig`` section of your ``Gruntfile.js`` file in the ``vows`` object.\n\n``vows`` is a [multitask](http://gruntjs.com/creating-tasks#multi-tasks).\n\nEach target references one or more source files containing suites and may contain options which will be applied to all of those\nsuites.\n\nAn example ``vows`` configuration with two targets:\n\n    ...\n    vows : {\n      all : {\n        src : \"<%= allTests %>\",\n        options : {\n          reporter : \"spec\"\n        }\n      },\n      allXunit : {\n        src : \"<%= allTests %>\",\n        dest : \"testResults.xml\"\n        options : {\n          reporter : \"Xunit\"\n        }\n      }\n    },\n    allTests : \"tests/*\"\n    ...\n\nThe example above uses the [_compact format_ for specifying files](http://gruntjs.com/configuring-tasks#compact-format)\nas well as [templates](http://gruntjs.com/configuring-tasks#templates).\n\nOne destination file (``dest``) can be specified per target.  It will contain the output of all the suites in the target.  If no\ndestination file is specified, the output will go to the console.\n\nPaths for both source and destination files are relative to the location of ``Gruntfile.js``.\n\nResults are summed by target.  Grunt-vows-runner doesn't combine the results of multiple targets.\n\nSuites within a target are run concurrently; faster suites will finish first.  Targets in grunt are always run sequentially.\n\n####Options\n\nOptions can be placed at the task (``vows``), target, or suite level.\n\nHere is an example of each:\n\n_Gruntfile.js_ (task- and target-level options) -- the reporter is set at the task-level\n\n    ...\n    vows : {\n      options : {\n        reporter : \"spec\"\n      },\n      most : {\n        src : [\"test/*\", \"!test/errorTests.js\"]\n      },\n      error : {\n        src : \"test/errorTests.js\",\n        options : {\n          error : false\n        }\n      }\n    }\n    ...\n\n_test/errorTests.js_ (suite-level options) -- this is a different way to accomplish the same as above\n\n    ...\n    vows.describe('Error Handling').addBatch({\n    ...\n    }).export(module, {error : false});\n    ...\n\nThe following options are available:\n\n* ``error``\n * Whether or not vows should handle errors in topics for you.  Set ``error : false`` if you want to handle your own errors.\n The first argument to your vows will be reserved for errors.\n* ``reporter``\n * [See the list of reporters](#reporters)\n* ``matcher``\n * a javascript [RegExp object](http://www.w3schools.com/jsref/jsref_obj_regexp.asp); only run tests whose titles match this\n object.\n* ``disabled``\n * Temporarily disable tests for a target.\n\n####Reporters<a id=\"reporters\"/>\n\nFrom grunt-vows-runner:\n\n* spec\n* xunit\n  * Produces output meant for [Jenkins CI](http://jenkins-ci.org/). It tries to divide the tests into a hierarchy of levels\n   for easier navigation in the Jenkins test report.\n  * Use the colon (':') character to separate levels.  For example if you had a topic (or a subtopic,\n   or combination) that looked like this:\n\n        ``Monkeys: grooming``\n\n        then there would be a \"Monkeys\" folder in Jenkins with a \"grooming\" folder inside of it, containing the test results.\n\nFrom [vows](https://github.com/cloudhead/vows/tree/master/lib/vows/reporters)\n\n* tap\n* dot-matrix\n* json\n\nRequest any other reporters [here](https://github.com/goalzen/grunt-vows-runner/issues)\n\n###Command-Line Options\n\ngrunt-vows-runner incorporates the following grunt command-line options, if present:\n\n* ``--no-color``\n* ``--verbose``\n\n###Bugs, etc.\n\nPlease report any bugs, feature requests, etc. to [grunt-vows-runner's github issue tracker](https://github.com/goalzen/grunt-vows-runner/issues).\n\n","readmeFilename":"README.md","_id":"grunt-vows-runner@0.4.0","dist":{"shasum":"b67516a7c2f2aaa4228cf6aff35eb025d03f5b0a","tarball":"https://registry.npmjs.org/grunt-vows-runner/-/grunt-vows-runner-0.4.0.tgz","integrity":"sha512-lJzFebNez1hRpm4ft+Jk09c+fet+C8OGN59hdaTq8h/Xgw4qFrselwl0YS9UR6mUf0hZpN1qEyfkJKAYI9vjhQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCUvfaJbHSxUq6RXA5X0sLuBSBule1wMvvjC2cKZC2xtgIhAL+FwrfbzEOa6xIPW83BiKQWcR6D6xRy8IT6YlbNwfSF"}]},"_from":".","_npmVersion":"1.2.14","_npmUser":{"name":"adamstallard","email":"adam@sweedl.com"},"maintainers":[{"name":"adamstallard","email":"adam@sweedl.com"}]},"0.4.1":{"name":"grunt-vows-runner","version":"0.4.1","description":"An alternative test-runner for vows using grunt.  Adds new capabilities such as running test suites concurrently.","keywords":["vows","test","testing","runner","task","gruntplugin","grunt","bdd","concurrent","asynchronous","parallel"],"author":{"name":"Adam Stallard","email":"adam@goalzen.org","url":"goalzen.org"},"directories":{"test":"test"},"dependencies":{"vows":"*","underscore":"*"},"peerDependencies":{"grunt":"~0.4"},"devDependencies":{"chai":"*","grunt-contrib-jshint":"*"},"license":{"type":"MIT","url":"https://github.com/goalzen/grunt-vows-runner/blob/master/LICENSE-MIT"},"engines":{"node":">=0.8.0"},"scripts":{"test":"grunt"},"repository":{"type":"git","url":"https://github.com/goalzen/grunt-vows-runner.git"},"bugs":{"url":"https://github.com/goalzen/grunt-vows-runner/issues"},"homepage":"https://github.com/goalzen/grunt-vows-runner.git","readme":"##grunt-vows-runner\n\n[![Build Status](https://travis-ci.org/goalzen/grunt-vows-runner.png?branch=master)](https://travis-ci.org/goalzen/grunt-vows-runner)\n\nAn alternative test-runner for vows using [grunt](http://gruntjs.com/).\n\n###Philosophy\n\nFile and directory matching, file watching, coverage reporting, etc. should be supplied by third-party tools where possible.\nGrunt is a great source of such third-party-tools.  These are much more likely to continue development than the equivalent\ntools built into vows, since they are used by many other packages as well.\n\n###Additions\n\nWith grunt-vows-runner you can\n\n* Use grunt [targets](http://gruntjs.com/configuring-tasks#task-configuration-and-targets) and\n[templates](http://gruntjs.com/configuring-tasks#templates).\n* Run suites in the same target concurrently.\n* Set different options for each target.\n* Have each target output to a different file (or the console).\n* Disable groups of tests at the target level.\n\n###Differences from the vows command-line runner\n\n* Use grunt to specify which [files](http://gruntjs.com/configuring-tasks#files) to run.\n* Use grunt's ``watch`` task.\n* No shuffle option (if you want this, let me know--it is easy to implement).\n* No built-in js-coverage support.\n * I highly recommend [istanbul](https://github.com/yahoo/istanbul), which does not need the cooperation of the test-runner\n (simply ``istanbul cover bin/vows`` will work ); and it is written in javascript, not java.\n* No 'isolate' option.  If your system-under-test uses process.cwd, process.argv, or process.exit,\nit is best to create a [child process](http://nodejs.org/api/child_process.html) in the test topic.\n\n###Installation\n\n1. Change directories to the root directory of your project\n2. ``npm install grunt``\n3. ``npm install grunt-vows-runner``\n4. Add the following line to your ``Gruntfile.js``\n   \n   ``grunt.loadNpmTasks('grunt-vows-runner');``\n\nThe ``vows`` task is now available; for example\n\n    grunt vows\n\n###Configuration\n\nConfiguration is placed in the ``grunt.initConfig`` section of your ``Gruntfile.js`` file in the ``vows`` object.\n\n``vows`` is a [multitask](http://gruntjs.com/creating-tasks#multi-tasks).\n\nEach target references one or more source files containing suites and may contain options which will be applied to all of those\nsuites.\n\nAn example ``vows`` configuration with two targets:\n\n    ...\n    vows : {\n      all : {\n        src : \"<%= allTests %>\",\n        options : {\n          reporter : \"spec\"\n        }\n      },\n      allXunit : {\n        src : \"<%= allTests %>\",\n        dest : \"testResults.xml\"\n        options : {\n          reporter : \"Xunit\"\n        }\n      }\n    },\n    allTests : \"tests/*\"\n    ...\n\nThe example above uses the [_compact format_ for specifying files](http://gruntjs.com/configuring-tasks#compact-format)\nas well as [templates](http://gruntjs.com/configuring-tasks#templates).\n\nOne destination file (``dest``) can be specified per target.  It will contain the output of all the suites in the target.  If no\ndestination file is specified, the output will go to the console.\n\nPaths for both source and destination files are relative to the location of ``Gruntfile.js``.\n\nResults are summed by target.  Grunt-vows-runner doesn't combine the results of multiple targets.\n\nSuites within a target are run concurrently; faster suites will finish first.  Targets in grunt are always run sequentially.\n\n####Options\n\nOptions can be placed at the task (``vows``), target, or suite level.\n\nHere is an example of each:\n\n_Gruntfile.js_ (task- and target-level options) -- the reporter is set at the task-level\n\n    ...\n    vows : {\n      options : {\n        reporter : \"spec\"\n      },\n      most : {\n        src : [\"test/*\", \"!test/errorTests.js\"]\n      },\n      error : {\n        src : \"test/errorTests.js\",\n        options : {\n          error : false\n        }\n      }\n    }\n    ...\n\n_test/errorTests.js_ (suite-level options) -- this is a different way to accomplish the same as above\n\n    ...\n    vows.describe('Error Handling').addBatch({\n    ...\n    }).export(module, {error : false});\n    ...\n\nThe following options are available:\n\n* ``error``\n * Whether or not vows should handle errors in topics for you.  Set ``error : false`` if you want to handle your own errors.\n The first argument to your vows will be reserved for errors.\n* ``reporter``\n * [See the list of reporters](#reporters)\n* ``matcher``\n * a javascript [RegExp object](http://www.w3schools.com/jsref/jsref_obj_regexp.asp); only run tests whose titles match this\n object.\n* ``disabled``\n * Temporarily disable tests for a target.\n\n####Reporters<a id=\"reporters\"/>\n\nFrom grunt-vows-runner:\n\n* spec\n* xunit\n  * Produces output meant for [Jenkins CI](http://jenkins-ci.org/). It tries to divide the tests into a hierarchy of levels\n   for easier navigation in the Jenkins test report.\n  * Use the colon (':') character to separate levels.  For example if you had a topic (or a subtopic,\n   or combination) that looked like this:\n\n        ``Monkeys: grooming``\n\n        then there would be a \"Monkeys\" folder in Jenkins with a \"grooming\" folder inside of it, containing the test results.\n\nFrom [vows](https://github.com/cloudhead/vows/tree/master/lib/vows/reporters)\n\n* tap\n* dot-matrix\n* json\n\nRequest any other reporters [here](https://github.com/goalzen/grunt-vows-runner/issues)\n\n###Command-Line Options\n\ngrunt-vows-runner incorporates the following grunt command-line options, if present:\n\n* ``--no-color``\n* ``--verbose``\n\n###Bugs, etc.\n\nPlease report any bugs, feature requests, etc. to [grunt-vows-runner's github issue tracker](https://github.com/goalzen/grunt-vows-runner/issues).\n\n","readmeFilename":"README.md","_id":"grunt-vows-runner@0.4.1","dist":{"shasum":"568a4e3c5433ffa39830c142ee56e2c1309efbb0","tarball":"https://registry.npmjs.org/grunt-vows-runner/-/grunt-vows-runner-0.4.1.tgz","integrity":"sha512-4IRVEl4WvX5QPnp8Eao3+XVNNv6Mk3NpVVaLMsY/uJpxjEaQS5/PMIXlFYGdOhkYuejSxaGsls4HxKtimDBTvg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDB8rEr284cATsPyoemeARW18Dc70ouAnF79Q569N/7aQIhALAo+IPeGwjy1IrNCoEzOa/QszPSsUbE6XceR9bd9I/3"}]},"_from":".","_npmVersion":"1.2.14","_npmUser":{"name":"adamstallard","email":"adam@sweedl.com"},"maintainers":[{"name":"adamstallard","email":"adam@sweedl.com"}]},"0.4.2":{"name":"grunt-vows-runner","version":"0.4.2","description":"An alternative test-runner for vows using grunt.  Adds new capabilities such as running test suites concurrently.","keywords":["vows","test","testing","runner","task","gruntplugin","grunt","bdd","concurrent","asynchronous","parallel"],"author":{"name":"Adam Stallard","email":"adam@goalzen.org","url":"goalzen.org"},"directories":{"test":"test"},"dependencies":{"vows":"*","underscore":"*"},"peerDependencies":{"grunt":"~0.4"},"devDependencies":{"chai":"*","grunt-contrib-jshint":"*"},"license":{"type":"MIT","url":"https://github.com/goalzen/grunt-vows-runner/blob/master/LICENSE-MIT"},"engines":{"node":">=0.8.0"},"scripts":{"test":"grunt"},"repository":{"type":"git","url":"https://github.com/goalzen/grunt-vows-runner.git"},"bugs":{"url":"https://github.com/goalzen/grunt-vows-runner/issues"},"homepage":"https://github.com/goalzen/grunt-vows-runner.git","readme":"##grunt-vows-runner\n\n[![Build Status](https://travis-ci.org/goalzen/grunt-vows-runner.png?branch=master)](https://travis-ci.org/goalzen/grunt-vows-runner)\n\nAn alternative test-runner for vows using [grunt](http://gruntjs.com/).\n\n###Philosophy\n\nFile and directory matching, file watching, coverage reporting, etc. should be supplied by third-party tools where possible.\nGrunt is a great source of such third-party-tools.  These are much more likely to continue development than the equivalent\ntools built into vows, since they are used by many other packages as well.\n\n###Additions\n\nWith grunt-vows-runner you can\n\n* Use grunt [targets](http://gruntjs.com/configuring-tasks#task-configuration-and-targets) and\n[templates](http://gruntjs.com/configuring-tasks#templates).\n* Run suites in the same target concurrently.\n* Set different options for each target.\n* Have each target output to a different file (or the console).\n* Disable groups of tests at the target level.\n\n###Differences from the vows command-line runner\n\n* Use grunt to specify which [files](http://gruntjs.com/configuring-tasks#files) to run.\n* Use grunt's ``watch`` task.\n* No shuffle option (if you want this, let me know--it is easy to implement).\n* No built-in js-coverage support.\n * I highly recommend [istanbul](https://github.com/yahoo/istanbul), which does not need the cooperation of the test-runner\n (simply ``istanbul cover bin/vows`` will work ); and it is written in javascript, not java.\n* No 'isolate' option.  If your system-under-test uses process.cwd, process.argv, or process.exit,\nit is best to create a [child process](http://nodejs.org/api/child_process.html) in the test topic.\n\n###Installation\n\n1. Change directories to the root directory of your project\n2. ``npm install grunt``\n3. ``npm install grunt-vows-runner``\n4. Add the following line to your ``Gruntfile.js``\n   \n   ``grunt.loadNpmTasks('grunt-vows-runner');``\n\nThe ``vows`` task is now available; for example\n\n    grunt vows\n\n###Configuration\n\nConfiguration is placed in the ``grunt.initConfig`` section of your ``Gruntfile.js`` file in the ``vows`` object.\n\n``vows`` is a [multitask](http://gruntjs.com/creating-tasks#multi-tasks).\n\nEach target references one or more source files containing suites and may contain options which will be applied to all of those\nsuites.\n\nAn example ``vows`` configuration with two targets:\n\n    ...\n    vows : {\n      all : {\n        src : \"<%= allTests %>\",\n        options : {\n          reporter : \"spec\"\n        }\n      },\n      allXunit : {\n        src : \"<%= allTests %>\",\n        dest : \"testResults.xml\"\n        options : {\n          reporter : \"Xunit\"\n        }\n      }\n    },\n    allTests : \"tests/*\"\n    ...\n\nThe example above uses the [_compact format_ for specifying files](http://gruntjs.com/configuring-tasks#compact-format)\nas well as [templates](http://gruntjs.com/configuring-tasks#templates).\n\nOne destination file (``dest``) can be specified per target.  It will contain the output of all the suites in the target.  If no\ndestination file is specified, the output will go to the console.\n\nPaths for both source and destination files are relative to the location of ``Gruntfile.js``.\n\nResults are summed by target.  Grunt-vows-runner doesn't combine the results of multiple targets.\n\nSuites within a target are run concurrently; faster suites will finish first.  Targets in grunt are always run sequentially.\n\n####Options\n\nOptions can be placed at the task (``vows``), target, or suite level.\n\nHere is an example of each:\n\n_Gruntfile.js_ (task- and target-level options) -- the reporter is set at the task-level\n\n    ...\n    vows : {\n      options : {\n        reporter : \"spec\"\n      },\n      most : {\n        src : [\"test/*\", \"!test/errorTests.js\"]\n      },\n      error : {\n        src : \"test/errorTests.js\",\n        options : {\n          error : false\n        }\n      }\n    }\n    ...\n\n_test/errorTests.js_ (suite-level options) -- this is a different way to accomplish the same as above\n\n    ...\n    vows.describe('Error Handling').addBatch({\n    ...\n    }).export(module, {error : false});\n    ...\n\nThe following options are available:\n\n* ``error``\n * Whether or not vows should handle errors in topics for you.  Set ``error : false`` if you want to handle your own errors.\n The first argument to your vows will be reserved for errors.\n* ``reporter``\n * [See the list of reporters](#reporters)\n* ``matcher``\n * a javascript [RegExp object](http://www.w3schools.com/jsref/jsref_obj_regexp.asp); only run tests whose titles match this\n object.\n* ``disabled``\n * Temporarily disable tests for a target.\n\n####Reporters<a id=\"reporters\"/>\n\nFrom grunt-vows-runner:\n\n* spec\n* xunit\n  * Produces output meant for [Jenkins CI](http://jenkins-ci.org/). It tries to divide the tests into a hierarchy of levels\n   for easier navigation in the Jenkins test report.\n  * Use the colon (':') character to separate levels.  For example if you had a topic (or a subtopic,\n   or combination) that looked like this:\n\n        ``Monkeys: grooming``\n\n        then there would be a \"Monkeys\" folder in Jenkins with a \"grooming\" folder inside of it, containing the test results.\n\nFrom [vows](https://github.com/cloudhead/vows/tree/master/lib/vows/reporters)\n\n* tap\n* dot-matrix\n* json\n\nRequest any other reporters [here](https://github.com/goalzen/grunt-vows-runner/issues)\n\n###Command-Line Options\n\ngrunt-vows-runner incorporates the following grunt command-line options, if present:\n\n* ``--no-color``\n* ``--verbose``\n\n###Bugs, etc.\n\nPlease report any bugs, feature requests, etc. to [grunt-vows-runner's github issue tracker](https://github.com/goalzen/grunt-vows-runner/issues).\n\n","readmeFilename":"README.md","_id":"grunt-vows-runner@0.4.2","dist":{"shasum":"dd565628263e0e71c116ffc34f940f63abcf4caf","tarball":"https://registry.npmjs.org/grunt-vows-runner/-/grunt-vows-runner-0.4.2.tgz","integrity":"sha512-bxaIBgsNDge+YWSfffqJm/rgq/bN9HtvZz3XvGc1X/8UiJNgljJYAsmjqH4Njt0UrzoXWUepmhJTGS9Sg0rcZw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIDOgOdli1C5Mbz68j/BYK29DMqwJSlzyWrPPyNSwCOlcAiBQ9JE/mpmPfwp8fwHFUBydH3xjYUDH6ukoicZ10+9UsQ=="}]},"_from":".","_npmVersion":"1.2.14","_npmUser":{"name":"adamstallard","email":"adam@sweedl.com"},"maintainers":[{"name":"adamstallard","email":"adam@sweedl.com"}]},"0.4.3":{"name":"grunt-vows-runner","version":"0.4.3","description":"An alternative test-runner for vows using grunt.  Adds new capabilities such as running test suites concurrently.","keywords":["vows","test","testing","runner","task","gruntplugin","grunt","bdd","concurrent","asynchronous","parallel"],"author":{"name":"Adam Stallard","email":"adam@goalzen.org","url":"goalzen.org"},"directories":{"test":"test"},"dependencies":{"vows":"*","underscore":"*"},"peerDependencies":{"grunt":"~0.4"},"devDependencies":{"chai":"*","grunt-contrib-jshint":"*"},"license":{"type":"MIT","url":"https://github.com/goalzen/grunt-vows-runner/blob/master/LICENSE-MIT"},"engines":{"node":">=0.8.0"},"scripts":{"test":"grunt"},"repository":{"type":"git","url":"https://github.com/goalzen/grunt-vows-runner.git"},"bugs":{"url":"https://github.com/goalzen/grunt-vows-runner/issues"},"homepage":"https://github.com/goalzen/grunt-vows-runner.git","readme":"##grunt-vows-runner\n\n[![Build Status](https://travis-ci.org/goalzen/grunt-vows-runner.png?branch=master)](https://travis-ci.org/goalzen/grunt-vows-runner)\n\nAn alternative test-runner for vows using [grunt](http://gruntjs.com/).\n\n###Philosophy\n\nFile and directory matching, file watching, coverage reporting, etc. should be supplied by third-party tools where possible.\nGrunt is a great source of such third-party-tools.  These are much more likely to continue development than the equivalent\ntools built into vows, since they are used by many other packages as well.\n\n###Additions\n\nWith grunt-vows-runner you can\n\n* Use grunt [targets](http://gruntjs.com/configuring-tasks#task-configuration-and-targets) and\n[templates](http://gruntjs.com/configuring-tasks#templates).\n* Run suites in the same target concurrently.\n* Set different options for each target.\n* Have each target output to a different file (or the console).\n* Disable groups of tests at the target level.\n\n###Differences from the vows command-line runner\n\n* Use grunt to specify which [files](http://gruntjs.com/configuring-tasks#files) to run.\n* Use grunt's ``watch`` task.\n* No shuffle option (if you want this, let me know--it is easy to implement).\n* No built-in js-coverage support.\n * I highly recommend [istanbul](https://github.com/yahoo/istanbul), which does not need the cooperation of the test-runner\n (simply ``istanbul cover bin/vows`` will work ); and it is written in javascript, not java.\n* No 'isolate' option.  If your system-under-test uses process.cwd, process.argv, or process.exit,\nit is best to create a [child process](http://nodejs.org/api/child_process.html) in the test topic.\n\n###Installation\n\n1. Change directories to the root directory of your project\n2. ``npm install grunt``\n3. ``npm install grunt-vows-runner``\n4. Add the following line to your ``Gruntfile.js``\n   \n   ``grunt.loadNpmTasks('grunt-vows-runner');``\n\nThe ``vows`` task is now available; for example\n\n    grunt vows\n\n###Configuration\n\nConfiguration is placed in the ``grunt.initConfig`` section of your ``Gruntfile.js`` file in the ``vows`` object.\n\n``vows`` is a [multitask](http://gruntjs.com/creating-tasks#multi-tasks).\n\nEach target references one or more source files containing suites and may contain options which will be applied to all of those\nsuites.\n\nAn example ``vows`` configuration with two targets:\n\n    ...\n    vows : {\n      all : {\n        src : \"<%= allTests %>\",\n        options : {\n          reporter : \"spec\"\n        }\n      },\n      allXunit : {\n        src : \"<%= allTests %>\",\n        dest : \"testResults.xml\"\n        options : {\n          reporter : \"Xunit\"\n        }\n      }\n    },\n    allTests : \"tests/*\"\n    ...\n\nThe example above uses the [_compact format_ for specifying files](http://gruntjs.com/configuring-tasks#compact-format)\nas well as [templates](http://gruntjs.com/configuring-tasks#templates).\n\nOne destination file (``dest``) can be specified per target.  It will contain the output of all the suites in the target.  If no\ndestination file is specified, the output will go to the console.\n\nPaths for both source and destination files are relative to the location of ``Gruntfile.js``.\n\nResults are summed by target.  Grunt-vows-runner doesn't combine the results of multiple targets.\n\nSuites within a target are run concurrently; faster suites will finish first.  Targets in grunt are always run sequentially.\n\n####Options\n\nOptions can be placed at the task (``vows``), target, or suite level.\n\nHere is an example of each:\n\n_Gruntfile.js_ (task- and target-level options) -- the reporter is set at the task-level\n\n    ...\n    vows : {\n      options : {\n        reporter : \"spec\"\n      },\n      most : {\n        src : [\"test/*\", \"!test/errorTests.js\"]\n      },\n      error : {\n        src : \"test/errorTests.js\",\n        options : {\n          error : false\n        }\n      }\n    }\n    ...\n\n_test/errorTests.js_ (suite-level options) -- this is a different way to accomplish the same as above\n\n    ...\n    vows.describe('Error Handling').addBatch({\n    ...\n    }).export(module, {error : false});\n    ...\n\nThe following options are available:\n\n* ``error``\n * Whether or not vows should handle errors in topics for you.  Set ``error : false`` if you want to handle your own errors.\n The first argument to your vows will be reserved for errors.\n* ``reporter``\n * [See the list of reporters](#reporters)\n* ``matcher``\n * a javascript [RegExp object](http://www.w3schools.com/jsref/jsref_obj_regexp.asp); only run tests whose titles match this\n object.\n* ``disabled``\n * Temporarily disable tests for a target.\n\n####Reporters<a id=\"reporters\"/>\n\nFrom grunt-vows-runner:\n\n* spec\n* xunit\n  * Produces output meant for [Jenkins CI](http://jenkins-ci.org/). It tries to divide the tests into a hierarchy of levels\n   for easier navigation in the Jenkins test report.\n  * Use the colon (':') character to separate levels.  For example if you had a topic (or a subtopic,\n   or combination) that looked like this:\n\n        ``Monkeys: grooming``\n\n        then there would be a \"Monkeys\" folder in Jenkins with a \"grooming\" folder inside of it, containing the test results.\n\nFrom [vows](https://github.com/cloudhead/vows/tree/master/lib/vows/reporters)\n\n* tap\n* dot-matrix\n* json\n\nRequest any other reporters [here](https://github.com/goalzen/grunt-vows-runner/issues)\n\n###Command-Line Options\n\ngrunt-vows-runner incorporates the following grunt command-line options, if present:\n\n* ``--no-color``\n* ``--verbose``\n\n###Bugs, etc.\n\nPlease report any bugs, feature requests, etc. to [grunt-vows-runner's github issue tracker](https://github.com/goalzen/grunt-vows-runner/issues).\n\n","readmeFilename":"README.md","_id":"grunt-vows-runner@0.4.3","dist":{"shasum":"48a0e127fae1cd0c0d8ef2213f9ba85eae0f12e2","tarball":"https://registry.npmjs.org/grunt-vows-runner/-/grunt-vows-runner-0.4.3.tgz","integrity":"sha512-BllYPNQ5rgSO21h5cbZQ5nTT1/u4X7OfLw0oSYCVZLhcfJs2tNobyR0Bc1deT9JOk3SimVbGgebQdUuddue23A==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIAQ2d4rbpUW6bVHrxqMrY+2Z3do3bCzRE/30wTAPh0v0AiEAvSrIC5dbFUc3UsDOil+J0ZToCp92mF7bRefdsbhavE0="}]},"_from":".","_npmVersion":"1.2.14","_npmUser":{"name":"adamstallard","email":"adam@sweedl.com"},"maintainers":[{"name":"adamstallard","email":"adam@sweedl.com"}]},"0.4.4":{"name":"grunt-vows-runner","version":"0.4.4","description":"An alternative test-runner for vows using grunt.  Adds new capabilities such as running test suites concurrently.","keywords":["vows","test","testing","runner","task","gruntplugin","grunt","bdd","concurrent","asynchronous","parallel"],"author":{"name":"Adam Stallard","email":"adam@goalzen.org","url":"goalzen.org"},"directories":{"test":"test"},"dependencies":{"vows":"*","underscore":"*"},"peerDependencies":{"grunt":"~0.4"},"devDependencies":{"chai":"*","grunt-contrib-jshint":"*"},"license":{"type":"MIT","url":"https://github.com/goalzen/grunt-vows-runner/blob/master/LICENSE-MIT"},"engines":{"node":">=0.8.0"},"scripts":{"test":"grunt"},"repository":{"type":"git","url":"https://github.com/goalzen/grunt-vows-runner.git"},"bugs":{"url":"https://github.com/goalzen/grunt-vows-runner/issues"},"homepage":"https://github.com/goalzen/grunt-vows-runner.git","readme":"##grunt-vows-runner\n\n[![Build Status](https://travis-ci.org/goalzen/grunt-vows-runner.png?branch=master)](https://travis-ci.org/goalzen/grunt-vows-runner)\n\nAn alternative test-runner for vows using [grunt](http://gruntjs.com/).\n\n###Philosophy\n\nFile and directory matching, file watching, coverage reporting, etc. should be supplied by third-party tools where possible.\nGrunt is a great source of such third-party-tools.  These are much more likely to continue development than the equivalent\ntools built into vows, since they are used by many other packages as well.\n\n###Additions\n\nWith grunt-vows-runner you can\n\n* Use grunt [targets](http://gruntjs.com/configuring-tasks#task-configuration-and-targets) and\n[templates](http://gruntjs.com/configuring-tasks#templates).\n* Run suites in the same target concurrently.\n* Set different options for each target.\n* Have each target output to a different file (or the console).\n* Disable groups of tests at the target level.\n\n###Differences from the vows command-line runner\n\n* Use grunt to specify which [files](http://gruntjs.com/configuring-tasks#files) to run.\n* Use grunt's ``watch`` task.\n* No shuffle option (if you want this, let me know--it is easy to implement).\n* No built-in js-coverage support.\n * I highly recommend [istanbul](https://github.com/yahoo/istanbul), which does not need the cooperation of the test-runner\n (simply ``istanbul cover bin/vows`` will work ); and it is written in javascript, not java.\n* No 'isolate' option.  If your system-under-test uses process.cwd, process.argv, or process.exit,\nit is best to create a [child process](http://nodejs.org/api/child_process.html) in the test topic.\n\n###Installation\n\n1. Change directories to the root directory of your project\n2. ``npm install grunt``\n3. ``npm install grunt-vows-runner``\n4. Add the following line to your ``Gruntfile.js``\n   \n   ``grunt.loadNpmTasks('grunt-vows-runner');``\n\nThe ``vows`` task is now available; for example\n\n    grunt vows\n\n###Configuration\n\nConfiguration is placed in the ``grunt.initConfig`` section of your ``Gruntfile.js`` file in the ``vows`` object.\n\n``vows`` is a [multitask](http://gruntjs.com/creating-tasks#multi-tasks).\n\nEach target references one or more source files containing suites and may contain options which will be applied to all of those\nsuites.\n\nAn example ``vows`` configuration with two targets:\n\n    ...\n    vows : {\n      all : {\n        src : \"<%= allTests %>\",\n        options : {\n          reporter : \"spec\"\n        }\n      },\n      allXunit : {\n        src : \"<%= allTests %>\",\n        dest : \"testResults.xml\"\n        options : {\n          reporter : \"Xunit\"\n        }\n      }\n    },\n    allTests : \"tests/*\"\n    ...\n\nThe example above uses the [_compact format_ for specifying files](http://gruntjs.com/configuring-tasks#compact-format)\nas well as [templates](http://gruntjs.com/configuring-tasks#templates).\n\nOne destination file (``dest``) can be specified per target.  It will contain the output of all the suites in the target.  If no\ndestination file is specified, the output will go to the console.\n\nPaths for both source and destination files are relative to the location of ``Gruntfile.js``.\n\nResults are summed by target.  Grunt-vows-runner doesn't combine the results of multiple targets.\n\nSuites within a target are run concurrently; faster suites will finish first.  Targets in grunt are always run sequentially.\n\n####Options\n\nOptions can be placed at the task (``vows``), target, or suite level.\n\nHere is an example of each:\n\n_Gruntfile.js_ (task- and target-level options) -- the reporter is set at the task-level\n\n    ...\n    vows : {\n      options : {\n        reporter : \"spec\"\n      },\n      most : {\n        src : [\"test/*\", \"!test/errorTests.js\"]\n      },\n      error : {\n        src : \"test/errorTests.js\",\n        options : {\n          error : false\n        }\n      }\n    }\n    ...\n\n_test/errorTests.js_ (suite-level options) -- this is a different way to accomplish the same as above\n\n    ...\n    vows.describe('Error Handling').addBatch({\n    ...\n    }).export(module, {error : false});\n    ...\n\nThe following options are available:\n\n* ``error``\n * Whether or not vows should handle errors in topics for you.  Set ``error : false`` if you want to handle your own errors.\n The first argument to your vows will be reserved for errors.\n* ``reporter``\n * [See the list of reporters](#reporters)\n* ``matcher``\n * a javascript [RegExp object](http://www.w3schools.com/jsref/jsref_obj_regexp.asp); only run tests whose titles match this\n object.\n* ``disabled``\n * Temporarily disable tests for a target.\n\n####Reporters<a id=\"reporters\"/>\n\nFrom grunt-vows-runner:\n\n* spec\n* xunit\n  * Produces output meant for [Jenkins CI](http://jenkins-ci.org/). It tries to divide the tests into a hierarchy of levels\n   for easier navigation in the Jenkins test report.\n  * Use the colon (':') character to separate levels.  For example if you had a topic (or a subtopic,\n   or combination) that looked like this:\n\n        ``Monkeys: grooming``\n\n        then there would be a \"Monkeys\" folder in Jenkins with a \"grooming\" folder inside of it, containing the test results.\n\nFrom [vows](https://github.com/cloudhead/vows/tree/master/lib/vows/reporters)\n\n* tap\n* dot-matrix\n* json\n\nRequest any other reporters [here](https://github.com/goalzen/grunt-vows-runner/issues)\n\n###Command-Line Options\n\ngrunt-vows-runner incorporates the following grunt command-line options, if present:\n\n* ``--no-color``\n* ``--verbose``\n\n###Bugs, etc.\n\nPlease report any bugs, feature requests, etc. to [grunt-vows-runner's github issue tracker](https://github.com/goalzen/grunt-vows-runner/issues).\n\n","readmeFilename":"README.md","_id":"grunt-vows-runner@0.4.4","dist":{"shasum":"80744c2837b652414436ff7654ff999b55cd4bf0","tarball":"https://registry.npmjs.org/grunt-vows-runner/-/grunt-vows-runner-0.4.4.tgz","integrity":"sha512-d9Gh47+hjNybHUbKc4c1xsKGNRMgf12iTAmg5a3M+14jpj26fMI/eYONv+z1r0oII5IGGlMZxCy7cUKmJuJ0iA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCICpLUVtCktQ0bhwmnolqqQ5Cojw3uyH192nlVj0uxrweAiEAjpXQi1oL2ktp8QNLA98ClvR73Gd6ViUvNKxTGJTczZ0="}]},"_from":".","_npmVersion":"1.2.14","_npmUser":{"name":"adamstallard","email":"adam@sweedl.com"},"maintainers":[{"name":"adamstallard","email":"adam@sweedl.com"}]},"0.5.0":{"name":"grunt-vows-runner","version":"0.5.0","description":"An alternative test-runner for vows using grunt.  Adds new capabilities such as running test suites concurrently.","keywords":["vows","test","testing","runner","task","gruntplugin","grunt","bdd","concurrent","asynchronous","parallel"],"author":{"name":"Adam Stallard","email":"adam@goalzen.org","url":"goalzen.org"},"directories":{"test":"test"},"dependencies":{"underscore":"*"},"peerDependencies":{"grunt":"~0.4","vows":"*"},"devDependencies":{"chai":"*","grunt-contrib-jshint":"*"},"license":{"type":"MIT","url":"https://github.com/goalzen/grunt-vows-runner/blob/master/LICENSE-MIT"},"engines":{"node":">=0.8.0"},"scripts":{"test":"grunt"},"repository":{"type":"git","url":"https://github.com/goalzen/grunt-vows-runner.git"},"bugs":{"url":"https://github.com/goalzen/grunt-vows-runner/issues"},"homepage":"https://github.com/goalzen/grunt-vows-runner.git","readme":"##grunt-vows-runner\n\n[![Build Status](https://travis-ci.org/goalzen/grunt-vows-runner.png?branch=master)](https://travis-ci.org/goalzen/grunt-vows-runner)\n\nAn alternative test-runner for vows using [grunt](http://gruntjs.com/).\n\n###Philosophy\n\nFile and directory matching, file watching, coverage reporting, etc. should be supplied by third-party tools where possible.\nGrunt is a great source of such third-party-tools.  These are much more likely to continue development than the equivalent\ntools built into vows, since they are used by many other packages as well.\n\n###Additions\n\nWith grunt-vows-runner you can\n\n* Use grunt [targets](http://gruntjs.com/configuring-tasks#task-configuration-and-targets) and\n[templates](http://gruntjs.com/configuring-tasks#templates).\n* Run suites in the same target concurrently.\n* Set different options for each target.\n* Have each target output to a different file (or the console).\n* Disable groups of tests at the target level.\n\n###Differences from the vows command-line runner\n\n* Use grunt to specify which [files](http://gruntjs.com/configuring-tasks#files) to run.\n* Use grunt's ``watch`` task.\n* No shuffle option (if you want this, let me know--it is easy to implement).\n* No built-in js-coverage support.\n * I highly recommend [istanbul](https://github.com/yahoo/istanbul), which does not need the cooperation of the test-runner\n (simply ``istanbul cover bin/vows`` will work ); and it is written in javascript, not java.\n* No 'isolate' option.  If your system-under-test uses process.cwd, process.argv, or process.exit,\nit is best to create a [child process](http://nodejs.org/api/child_process.html) in the test topic.\n\n###Installation\n\n1. Change directories to the root directory of your project\n2. ``npm install grunt``\n3. ``npm install grunt-vows-runner``\n4. Add the following line to your ``Gruntfile.js``\n   \n   ``grunt.loadNpmTasks('grunt-vows-runner');``\n\nThe ``vows`` task is now available; for example\n\n    grunt vows\n\n###Configuration\n\nConfiguration is placed in the ``grunt.initConfig`` section of your ``Gruntfile.js`` file in the ``vows`` object.\n\n``vows`` is a [multitask](http://gruntjs.com/creating-tasks#multi-tasks).\n\nEach target references one or more source files containing suites and may contain options which will be applied to all of those\nsuites.\n\nAn example ``vows`` configuration with two targets:\n\n    ...\n    vows : {\n      all : {\n        src : \"<%= allTests %>\",\n        options : {\n          reporter : \"spec\"\n        }\n      },\n      allXunit : {\n        src : \"<%= allTests %>\",\n        dest : \"testResults.xml\"\n        options : {\n          reporter : \"Xunit\"\n        }\n      }\n    },\n    allTests : \"tests/*\"\n    ...\n\nThe example above uses the [_compact format_ for specifying files](http://gruntjs.com/configuring-tasks#compact-format)\nas well as [templates](http://gruntjs.com/configuring-tasks#templates).\n\nOne destination file (``dest``) can be specified per target.  It will contain the output of all the suites in the target.  If no\ndestination file is specified, the output will go to the console.\n\nPaths for both source and destination files are relative to the location of ``Gruntfile.js``.\n\nResults are summed by target.  Grunt-vows-runner doesn't combine the results of multiple targets.\n\nSuites within a target are run concurrently; faster suites will finish first.  Targets in grunt are always run sequentially.\n\n####Options\n\nOptions can be placed at the task (``vows``), target, or suite level.\n\nHere is an example of each:\n\n_Gruntfile.js_ (task- and target-level options) -- the reporter is set at the task-level\n\n    ...\n    vows : {\n      options : {\n        reporter : \"spec\"\n      },\n      most : {\n        src : [\"test/*\", \"!test/errorTests.js\"]\n      },\n      error : {\n        src : \"test/errorTests.js\",\n        options : {\n          error : false\n        }\n      }\n    }\n    ...\n\n_test/errorTests.js_ (suite-level options) -- this is a different way to accomplish the same as above\n\n    ...\n    vows.describe('Error Handling').addBatch({\n    ...\n    }).export(module, {error : false});\n    ...\n\nThe following options are available:\n\n* ``error``\n * Whether or not vows should handle errors in topics for you.  Set ``error : false`` if you want to handle your own errors.\n The first argument to your vows will be reserved for errors.\n* ``reporter``\n * [See the list of reporters](#reporters)\n* ``matcher``\n * a javascript [RegExp object](http://www.w3schools.com/jsref/jsref_obj_regexp.asp); only run tests whose titles match this\n object.\n* ``disabled``\n * Temporarily disable tests for a target.\n\n####Reporters<a id=\"reporters\"/>\n\nFrom grunt-vows-runner:\n\n* spec\n* xunit\n  * Produces output meant for [Jenkins CI](http://jenkins-ci.org/). It tries to divide the tests into a hierarchy of levels\n   for easier navigation in the Jenkins test report.\n  * Use the colon (':') character to separate levels.  For example if you had a topic (or a subtopic,\n   or combination) that looked like this:\n\n        ``Monkeys: grooming``\n\n        then there would be a \"Monkeys\" folder in Jenkins with a \"grooming\" folder inside of it, containing the test results.\n\nFrom [vows](https://github.com/cloudhead/vows/tree/master/lib/vows/reporters)\n\n* tap\n* dot-matrix\n* json\n\nRequest any other reporters [here](https://github.com/goalzen/grunt-vows-runner/issues)\n\n###Command-Line Options\n\ngrunt-vows-runner incorporates the following grunt command-line options, if present:\n\n* ``--no-color``\n* ``--verbose``\n\n###Bugs, etc.\n\nPlease report any bugs, feature requests, etc. to [grunt-vows-runner's github issue tracker](https://github.com/goalzen/grunt-vows-runner/issues).\n\n","readmeFilename":"README.md","_id":"grunt-vows-runner@0.5.0","dist":{"shasum":"f0f5bf98702228bb6271093df8d09c67bb188a22","tarball":"https://registry.npmjs.org/grunt-vows-runner/-/grunt-vows-runner-0.5.0.tgz","integrity":"sha512-IscyG1g+bZqxij/+SpnhnZrgGe8Qb91jMZIeIn0tT8c77jiiXJgnUmMZ62hDjNW08XN/iM5Z5R4Ng2ZhjBpllQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQD3L6bRSD26jxpAEnOVMcJDlRBswEEY3TUJXLyC842MaQIhAMV5QH7lmYwNiJYevSx8Awn/8sl6IeoUQ8BwuHSodWnv"}]},"_from":".","_npmVersion":"1.2.14","_npmUser":{"name":"adamstallard","email":"adam@sweedl.com"},"maintainers":[{"name":"adamstallard","email":"adam@sweedl.com"}]},"0.5.1":{"name":"grunt-vows-runner","version":"0.5.1","description":"An alternative test-runner for vows using grunt.  Adds new capabilities such as running test suites concurrently.","keywords":["vows","test","testing","runner","task","gruntplugin","grunt","bdd","concurrent","asynchronous","parallel"],"author":{"name":"Adam Stallard","email":"adam@goalzen.org","url":"goalzen.org"},"directories":{"test":"test"},"dependencies":{"underscore":"*","vows":"*"},"peerDependencies":{"grunt":"~0.4","vows":"*"},"devDependencies":{"chai":"*","grunt-contrib-jshint":"*"},"license":{"type":"MIT","url":"https://github.com/goalzen/grunt-vows-runner/blob/master/LICENSE-MIT"},"engines":{"node":">=0.8.0"},"scripts":{"test":"grunt"},"repository":{"type":"git","url":"https://github.com/goalzen/grunt-vows-runner.git"},"bugs":{"url":"https://github.com/goalzen/grunt-vows-runner/issues"},"homepage":"https://github.com/goalzen/grunt-vows-runner.git","readme":"##grunt-vows-runner\n\n[![Build Status](https://travis-ci.org/goalzen/grunt-vows-runner.png?branch=master)](https://travis-ci.org/goalzen/grunt-vows-runner)\n\nAn alternative test-runner for vows using [grunt](http://gruntjs.com/).\n\n###Philosophy\n\nFile and directory matching, file watching, coverage reporting, etc. should be supplied by third-party tools where possible.\nGrunt is a great source of such third-party-tools.  These are much more likely to continue development than the equivalent\ntools built into vows, since they are used by many other packages as well.\n\n###Additions\n\nWith grunt-vows-runner you can\n\n* Use grunt [targets](http://gruntjs.com/configuring-tasks#task-configuration-and-targets) and\n[templates](http://gruntjs.com/configuring-tasks#templates).\n* Run suites in the same target concurrently.\n* Set different options for each target.\n* Have each target output to a different file (or the console).\n* Disable groups of tests at the target level.\n\n###Differences from the vows command-line runner\n\n* Use grunt to specify which [files](http://gruntjs.com/configuring-tasks#files) to run.\n* Use grunt's ``watch`` task.\n* No shuffle option (if you want this, let me know--it is easy to implement).\n* No built-in js-coverage support.\n * I highly recommend [istanbul](https://github.com/yahoo/istanbul), which does not need the cooperation of the test-runner\n (simply ``istanbul cover bin/vows`` will work ); and it is written in javascript, not java.\n* No 'isolate' option.  If your system-under-test uses process.cwd, process.argv, or process.exit,\nit is best to create a [child process](http://nodejs.org/api/child_process.html) in the test topic.\n\n###Installation\n\n1. Change directories to the root directory of your project\n2. ``npm install grunt``\n3. ``npm install grunt-vows-runner``\n4. Add the following line to your ``Gruntfile.js``\n   \n   ``grunt.loadNpmTasks('grunt-vows-runner');``\n\nThe ``vows`` task is now available; for example\n\n    grunt vows\n\n###Configuration\n\nConfiguration is placed in the ``grunt.initConfig`` section of your ``Gruntfile.js`` file in the ``vows`` object.\n\n``vows`` is a [multitask](http://gruntjs.com/creating-tasks#multi-tasks).\n\nEach target references one or more source files containing suites and may contain options which will be applied to all of those\nsuites.\n\nAn example ``vows`` configuration with two targets:\n\n    ...\n    vows : {\n      all : {\n        src : \"<%= allTests %>\",\n        options : {\n          reporter : \"spec\"\n        }\n      },\n      allXunit : {\n        src : \"<%= allTests %>\",\n        dest : \"testResults.xml\"\n        options : {\n          reporter : \"Xunit\"\n        }\n      }\n    },\n    allTests : \"tests/*\"\n    ...\n\nThe example above uses the [_compact format_ for specifying files](http://gruntjs.com/configuring-tasks#compact-format)\nas well as [templates](http://gruntjs.com/configuring-tasks#templates).\n\nOne destination file (``dest``) can be specified per target.  It will contain the output of all the suites in the target.  If no\ndestination file is specified, the output will go to the console.\n\nPaths for both source and destination files are relative to the location of ``Gruntfile.js``.\n\nResults are summed by target.  Grunt-vows-runner doesn't combine the results of multiple targets.\n\nSuites within a target are run concurrently; faster suites will finish first.  Targets in grunt are always run sequentially.\n\n####Options\n\nOptions can be placed at the task (``vows``), target, or suite level.\n\nHere is an example of each:\n\n_Gruntfile.js_ (task- and target-level options) -- the reporter is set at the task-level\n\n    ...\n    vows : {\n      options : {\n        reporter : \"spec\"\n      },\n      most : {\n        src : [\"test/*\", \"!test/errorTests.js\"]\n      },\n      error : {\n        src : \"test/errorTests.js\",\n        options : {\n          error : false\n        }\n      }\n    }\n    ...\n\n_test/errorTests.js_ (suite-level options) -- this is a different way to accomplish the same as above\n\n    ...\n    vows.describe('Error Handling').addBatch({\n    ...\n    }).export(module, {error : false});\n    ...\n\nThe following options are available:\n\n* ``error``\n * Whether or not vows should handle errors in topics for you.  Set ``error : false`` if you want to handle your own errors.\n The first argument to your vows will be reserved for errors.\n* ``reporter``\n * [See the list of reporters](#reporters)\n* ``matcher``\n * a javascript [RegExp object](http://www.w3schools.com/jsref/jsref_obj_regexp.asp); only run tests whose titles match this\n object.\n* ``disabled``\n * Temporarily disable tests for a target.\n\n####Reporters<a id=\"reporters\"/>\n\nFrom grunt-vows-runner:\n\n* spec\n* xunit\n  * Produces output meant for [Jenkins CI](http://jenkins-ci.org/). It tries to divide the tests into a hierarchy of levels\n   for easier navigation in the Jenkins test report.\n  * Use the colon (':') character to separate levels.  For example if you had a topic (or a subtopic,\n   or combination) that looked like this:\n\n        ``Monkeys: grooming``\n\n        then there would be a \"Monkeys\" folder in Jenkins with a \"grooming\" folder inside of it, containing the test results.\n\nFrom [vows](https://github.com/cloudhead/vows/tree/master/lib/vows/reporters)\n\n* tap\n* dot-matrix\n* json\n\nRequest any other reporters [here](https://github.com/goalzen/grunt-vows-runner/issues)\n\n###Command-Line Options\n\ngrunt-vows-runner incorporates the following grunt command-line options, if present:\n\n* ``--no-color``\n* ``--verbose``\n\n###Bugs, etc.\n\nPlease report any bugs, feature requests, etc. to [grunt-vows-runner's github issue tracker](https://github.com/goalzen/grunt-vows-runner/issues).\n\n","readmeFilename":"README.md","_id":"grunt-vows-runner@0.5.1","dist":{"shasum":"ad962ec9d2927972f4afabd30e7dd3b13146c0e4","tarball":"https://registry.npmjs.org/grunt-vows-runner/-/grunt-vows-runner-0.5.1.tgz","integrity":"sha512-TaHlSsWWf5r0bYYVweyAI5lpWBgViVfsVqH8l90b8bfKa+JinIoUKiRVadlIwRpASgnPs8LerQstge0Yuksj7w==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDHMtMORlS+NSGPWQLBmJOt4wmQ3FiM9XvlNXzPc9Qa0gIgTpSnWvi+4FBTumbPALyqOX49GY0sjlzhBOztdMOzwpQ="}]},"_from":".","_npmVersion":"1.2.14","_npmUser":{"name":"adamstallard","email":"adam@sweedl.com"},"maintainers":[{"name":"adamstallard","email":"adam@sweedl.com"}]},"0.5.2":{"name":"grunt-vows-runner","version":"0.5.2","description":"An alternative test-runner for vows using grunt.  Adds new capabilities such as running test suites concurrently.","keywords":["vows","test","testing","runner","task","gruntplugin","grunt","bdd","concurrent","asynchronous","parallel"],"author":{"name":"Adam Stallard","email":"adam@goalzen.org","url":"goalzen.org"},"directories":{"test":"test"},"dependencies":{"underscore":"*"},"peerDependencies":{"grunt":"~0.4","vows":"*"},"devDependencies":{"vows":"*","chai":"*","grunt":"~0.4","grunt-contrib-jshint":"*"},"license":{"type":"MIT","url":"https://github.com/goalzen/grunt-vows-runner/blob/master/LICENSE-MIT"},"engines":{"node":">=0.8.0"},"scripts":{"test":"grunt"},"repository":{"type":"git","url":"https://github.com/goalzen/grunt-vows-runner.git"},"bugs":{"url":"https://github.com/goalzen/grunt-vows-runner/issues"},"homepage":"https://github.com/goalzen/grunt-vows-runner.git","readme":"##grunt-vows-runner\n\n[![Build Status](https://travis-ci.org/goalzen/grunt-vows-runner.png?branch=master)](https://travis-ci.org/goalzen/grunt-vows-runner)\n\nAn alternative test-runner for vows using [grunt](http://gruntjs.com/).\n\n###Philosophy\n\nFile and directory matching, file watching, coverage reporting, etc. should be supplied by third-party tools where possible.\nGrunt is a great source of such third-party-tools.  These are much more likely to continue development than the equivalent\ntools built into vows, since they are used by many other packages as well.\n\n###Additions\n\nWith grunt-vows-runner you can\n\n* Use grunt [targets](http://gruntjs.com/configuring-tasks#task-configuration-and-targets) and\n[templates](http://gruntjs.com/configuring-tasks#templates).\n* Run suites in the same target concurrently.\n* Set different options for each target.\n* Have each target output to a different file (or the console).\n* Disable groups of tests at the target level.\n\n###Differences from the vows command-line runner\n\n* Use grunt to specify which [files](http://gruntjs.com/configuring-tasks#files) to run.\n* Use grunt's ``watch`` task.\n* No shuffle option (if you want this, let me know--it is easy to implement).\n* No built-in js-coverage support.\n * I highly recommend [istanbul](https://github.com/yahoo/istanbul), which does not need the cooperation of the test-runner\n (simply ``istanbul cover bin/vows`` will work ); and it is written in javascript, not java.\n* No 'isolate' option.  If your system-under-test uses process.cwd, process.argv, or process.exit,\nit is best to create a [child process](http://nodejs.org/api/child_process.html) in the test topic.\n\n###Installation\n\n1. Change directories to the root directory of your project\n2. ``npm install grunt``\n3. ``npm install grunt-vows-runner``\n4. Add the following line to your ``Gruntfile.js``\n   \n   ``grunt.loadNpmTasks('grunt-vows-runner');``\n\nThe ``vows`` task is now available; for example\n\n    grunt vows\n\n###Configuration\n\nConfiguration is placed in the ``grunt.initConfig`` section of your ``Gruntfile.js`` file in the ``vows`` object.\n\n``vows`` is a [multitask](http://gruntjs.com/creating-tasks#multi-tasks).\n\nEach target references one or more source files containing suites and may contain options which will be applied to all of those\nsuites.\n\nAn example ``vows`` configuration with two targets:\n\n    ...\n    vows : {\n      all : {\n        src : \"<%= allTests %>\",\n        options : {\n          reporter : \"spec\"\n        }\n      },\n      allXunit : {\n        src : \"<%= allTests %>\",\n        dest : \"testResults.xml\"\n        options : {\n          reporter : \"Xunit\"\n        }\n      }\n    },\n    allTests : \"tests/*\"\n    ...\n\nThe example above uses the [_compact format_ for specifying files](http://gruntjs.com/configuring-tasks#compact-format)\nas well as [templates](http://gruntjs.com/configuring-tasks#templates).\n\nOne destination file (``dest``) can be specified per target.  It will contain the output of all the suites in the target.  If no\ndestination file is specified, the output will go to the console.\n\nPaths for both source and destination files are relative to the location of ``Gruntfile.js``.\n\nResults are summed by target.  Grunt-vows-runner doesn't combine the results of multiple targets.\n\nSuites within a target are run concurrently; faster suites will finish first.  Targets in grunt are always run sequentially.\n\n####Options\n\nOptions can be placed at the task (``vows``), target, or suite level.\n\nHere is an example of each:\n\n_Gruntfile.js_ (task- and target-level options) -- the reporter is set at the task-level\n\n    ...\n    vows : {\n      options : {\n        reporter : \"spec\"\n      },\n      most : {\n        src : [\"test/*\", \"!test/errorTests.js\"]\n      },\n      error : {\n        src : \"test/errorTests.js\",\n        options : {\n          error : false\n        }\n      }\n    }\n    ...\n\n_test/errorTests.js_ (suite-level options) -- this is a different way to accomplish the same as above\n\n    ...\n    vows.describe('Error Handling').addBatch({\n    ...\n    }).export(module, {error : false});\n    ...\n\nThe following options are available:\n\n* ``error``\n * Whether or not vows should handle errors in topics for you.  Set ``error : false`` if you want to handle your own errors.\n The first argument to your vows will be reserved for errors.\n* ``reporter``\n * [See the list of reporters](#reporters)\n* ``matcher``\n * a javascript [RegExp object](http://www.w3schools.com/jsref/jsref_obj_regexp.asp); only run tests whose titles match this\n object.\n* ``disabled``\n * Temporarily disable tests for a target.\n\n####Reporters<a id=\"reporters\"/>\n\nFrom grunt-vows-runner:\n\n* spec\n* xunit\n  * Produces output meant for [Jenkins CI](http://jenkins-ci.org/). It tries to divide the tests into a hierarchy of levels\n   for easier navigation in the Jenkins test report.\n  * Use the colon (':') character to separate levels.  For example if you had a topic (or a subtopic,\n   or combination) that looked like this:\n\n        ``Monkeys: grooming``\n\n        then there would be a \"Monkeys\" folder in Jenkins with a \"grooming\" folder inside of it, containing the test results.\n\nFrom [vows](https://github.com/cloudhead/vows/tree/master/lib/vows/reporters)\n\n* tap\n* dot-matrix\n* json\n\nRequest any other reporters [here](https://github.com/goalzen/grunt-vows-runner/issues)\n\n###Command-Line Options\n\ngrunt-vows-runner incorporates the following grunt command-line options, if present:\n\n* ``--no-color``\n* ``--verbose``\n\n###Bugs, etc.\n\nPlease report any bugs, feature requests, etc. to [grunt-vows-runner's github issue tracker](https://github.com/goalzen/grunt-vows-runner/issues).\n\n","readmeFilename":"README.md","_id":"grunt-vows-runner@0.5.2","dist":{"shasum":"7072b5562a01315228bd37170df606c1fa441677","tarball":"https://registry.npmjs.org/grunt-vows-runner/-/grunt-vows-runner-0.5.2.tgz","integrity":"sha512-uk34mSKzz2bjINOwg0/LHDb2DhzJqbELQfSM1mNKujhnf+cx1s9vFNMVri5qMoz4fYhFcZJTwqrhEB6EdfIyRQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDqc7WwxF/dLfR0tFBKo8XIWID4gPyiw94QFJDir6VW4QIhANXgC9MR0XMpzJVMACNqAWj+Uf3EC5CAcVoetITS+mPz"}]},"_from":".","_npmVersion":"1.2.14","_npmUser":{"name":"adamstallard","email":"adam@sweedl.com"},"maintainers":[{"name":"adamstallard","email":"adam@sweedl.com"}]},"0.6.0":{"name":"grunt-vows-runner","version":"0.6.0","description":"An alternative test-runner for vows using grunt.  Adds new capabilities such as running test suites concurrently.","keywords":["vows","test","testing","runner","task","gruntplugin","grunt","bdd","concurrent","asynchronous","parallel"],"author":{"name":"Adam Stallard","email":"adam@goalzen.org","url":"goalzen.org"},"directories":{"test":"test"},"dependencies":{"lodash":"*"},"peerDependencies":{"grunt":"~0.4","vows":"*"},"devDependencies":{"vows":"*","chai":"*","grunt":"~0.4","grunt-contrib-jshint":"*"},"license":{"type":"MIT","url":"https://github.com/goalzen/grunt-vows-runner/blob/master/LICENSE-MIT"},"engines":{"node":">=0.8.0"},"scripts":{"test":"grunt"},"repository":{"type":"git","url":"https://github.com/goalzen/grunt-vows-runner.git"},"bugs":{"url":"https://github.com/goalzen/grunt-vows-runner/issues"},"homepage":"https://github.com/goalzen/grunt-vows-runner.git","readme":"##grunt-vows-runner\n\n[![Build Status](https://travis-ci.org/goalzen/grunt-vows-runner.png?branch=master)](https://travis-ci.org/goalzen/grunt-vows-runner)\n\nAn alternative test-runner for vows using [grunt](http://gruntjs.com/).\n\n###Philosophy\n\nFile and directory matching, file watching, coverage reporting, etc. should be supplied by third-party tools where possible.\nGrunt is a great source of such third-party-tools.  These are much more likely to continue development than the equivalent\ntools built into vows, since they are used by many other packages as well.\n\n###Additions\n\nWith grunt-vows-runner you can\n\n* Use grunt [targets](http://gruntjs.com/configuring-tasks#task-configuration-and-targets) and\n[templates](http://gruntjs.com/configuring-tasks#templates).\n* Run suites in the same target concurrently.\n* Set different options for each target.\n* Have each target output to a different file (or the console).\n* Disable groups of tests at the target level.\n\n###Differences from the vows command-line runner\n\n* Use grunt to specify which [files](http://gruntjs.com/configuring-tasks#files) to run.\n* Use grunt's ``watch`` task.\n* No shuffle option (if you want this, let me know--it is easy to implement).\n* No built-in js-coverage support.\n * I highly recommend [istanbul](https://github.com/yahoo/istanbul), which does not need the cooperation of the test-runner\n (simply ``istanbul cover bin/vows`` will work ); and it is written in javascript, not java.\n* No 'isolate' option.  If your system-under-test uses process.cwd, process.argv, or process.exit,\nit is best to create a [child process](http://nodejs.org/api/child_process.html) in the test topic.\n\n###Installation\n\n1. Change directories to the root directory of your project\n2. ``npm install grunt-vows-runner``\n3. Add the following line to your ``Gruntfile.js``\n\n```javascript\ngrunt.loadNpmTasks('grunt-vows-runner');\n```\n\n###Configuration\n\nConfiguration is placed in the ``grunt.initConfig`` section of your ``Gruntfile.js`` file in the ``vows`` object.\n\n``vows`` is a [multitask](http://gruntjs.com/creating-tasks#multi-tasks).\n\nEach target references one or more source files containing suites and may contain options which will be applied to all of those\nsuites.\n\nAn example ``vows`` configuration with two targets:\n\n    ...\n    vows : {\n      all : {\n        src : \"<%= allTests %>\",\n        options : {\n          reporter : \"spec\"\n        }\n      },\n      allXunit : {\n        src : \"<%= allTests %>\",\n        dest : \"testResults.xml\"\n        options : {\n          reporter : \"Xunit\"\n        }\n      }\n    },\n    allTests : \"tests/*\"\n    ...\n\nThe example above uses the [_compact format_ for specifying files](http://gruntjs.com/configuring-tasks#compact-format)\nas well as [templates](http://gruntjs.com/configuring-tasks#templates).\n\nOne destination file (``dest``) can be specified per target.  It will contain the output of all the suites in the target.  If no\ndestination file is specified, the output will go to the console.\n\nPaths for both source and destination files are relative to the location of ``Gruntfile.js``.\n\nResults are summed by target.  Grunt-vows-runner doesn't combine the results of multiple targets.\n\nSuites within a target are run concurrently; faster suites will finish first.  Targets in grunt are always run sequentially.\n\n####Options\n\nOptions can be placed at the task (``vows``), target, or suite level.\n\nHere is an example of each:\n\n_Gruntfile.js_ (task- and target-level options) -- the reporter is set at the task-level\n\n    ...\n    vows : {\n      options : {\n        reporter : \"spec\"\n      },\n      most : {\n        src : [\"test/*\", \"!test/errorTests.js\"]\n      },\n      error : {\n        src : \"test/errorTests.js\",\n        options : {\n          error : false\n        }\n      }\n    }\n    ...\n\n_test/errorTests.js_ (suite-level options) -- this is a different way to accomplish the same as above\n\n    ...\n    vows.describe('Error Handling').addBatch({\n    ...\n    }).export(module, {error : false});\n    ...\n\nThe following options are available:\n\n* ``error``\n * Whether or not vows should handle errors in topics for you.  Set ``error : false`` if you want to handle your own errors.\n The first argument to your vows will be reserved for errors.\n* ``reporter``\n * [See the list of reporters](#reporters)\n* ``matcher``\n * a javascript [RegExp object](http://www.w3schools.com/jsref/jsref_obj_regexp.asp); only run tests whose titles match this\n object.\n* ``disabled``\n * Temporarily disable tests for a target.\n\n####Reporters<a id=\"reporters\"/>\n\nFrom grunt-vows-runner:\n\n* spec\n* xunit\n  * Produces output meant for [Jenkins CI](http://jenkins-ci.org/). It tries to divide the tests into a hierarchy of levels\n   for easier navigation in the Jenkins test report.\n  * Use the colon (':') character to separate levels.  For example if you had a topic (or a subtopic,\n   or combination) that looked like this:\n\n        ``Monkeys: grooming``\n\n        then there would be a \"Monkeys\" folder in Jenkins with a \"grooming\" folder inside of it, containing the test results.\n\nFrom [vows](https://github.com/cloudhead/vows/tree/master/lib/vows/reporters)\n\n* tap\n* dot-matrix\n* json\n\nRequest any other reporters [here](https://github.com/goalzen/grunt-vows-runner/issues)\n\n###Command-Line Options\n\ngrunt-vows-runner incorporates the following grunt command-line options, if present:\n\n* ``--no-color``\n* ``--verbose``\n\n###Bugs, etc.\n\nPlease report any bugs, feature requests, etc. to [grunt-vows-runner's github issue tracker](https://github.com/goalzen/grunt-vows-runner/issues).\n\n","readmeFilename":"README.md","_id":"grunt-vows-runner@0.6.0","dist":{"shasum":"a32cca22c0b93f00e6e1d1f33225d74096ee6e3c","tarball":"https://registry.npmjs.org/grunt-vows-runner/-/grunt-vows-runner-0.6.0.tgz","integrity":"sha512-8YIAYgztk2de6qrTYJrBpxhVRsyeeblT0nR8RH8OOd/SjTcBvFQ6hgjXQxrnijWxbGqpDqFlvaAqepivP8eM2w==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCevoUaCVCidpg87tS267/1Rw3KlUyDNQ5k2O2wq5vjxAIgMwi/4ekL/7Ho8FgY8DXjdeIcyRchWb5tGtzDMj5Zs9g="}]},"_from":".","_npmVersion":"1.2.25","_npmUser":{"name":"adamstallard","email":"adam@goalzen.org"},"maintainers":[{"name":"adamstallard","email":"adam@sweedl.com"}]}},"readme":"##grunt-vows-runner\n\nA test-runner for vows using [grunt](http://gruntjs.com/).\n\n###Philosophy\n\nFile and directory matching, file watching, coverage reporting, etc. should be supplied by third-party tools where possible.\nGrunt is a great source of such third-party-tools.  These are much more likely to continue development than the equivalent\ntools built into vows, since they are used by many other packages as well.\n\n###Additions\n\nWith grunt-vows-runner you can\n\n* Use grunt [tasks](http://gruntjs.com/configuring-tasks) and [templates](http://gruntjs.com/configuring-tasks#templates).\n* Run suites in the same [target](http://gruntjs.com/configuring-tasks#task-configuration-and-targets)\nconcurrently.\n* Set options at the target level.\n* Set the ``isolate`` option at the suite and target level, and run isolated and non-isolated suites concurrently.\n* Disable groups of tests at the target level\n\n###Differences from the vows command-line runner\n\n* Uses grunt to specify which [files](http://gruntjs.com/configuring-tasks#files) to run\n* Uses grunt's ``watch`` task instead of vows' built-in watch implementation\n* No shuffle option (if you want this, let me know--it is easy to implement)\n* No built-in js-coverage support\n * I highly recommend [istanbul](https://github.com/yahoo/istanbul), which does not need the cooperation of the test-runner\n (simply ``istanbul cover bin/vows`` will work ); and it is written in javascript, not java\n\n###Installation\n\n1. Change directories to the root directory of your project\n2. ``npm install grunt-vows-runner``\n\n###Usage\n\nAdd the following line to your ``Gruntfile.js``\n\n    grunt.loadNpmTasks('grunt-vows-runner');\n\nThe ``vows`` task is now available; for example\n\n    grunt vows\n\n###Configuration\n\nConfiguration is placed in the ``grunt.initConfig`` section of your ``Gruntfile.js`` file in the ``vows`` object.\n\n``vows`` is a [multitask](http://gruntjs.com/creating-tasks#multi-tasks).\n\nEach target references one or more source files containing suites and may contain options which will be applied to all of those\nsuites.\n\nAn example ``vows`` configuration with two targets:\n\n    ...\n    vows : {\n      all : {\n        src : \"<%= allTests %>\",\n        options : {\n          reporter : \"spec\"\n        }\n      },\n      allXunit : {\n        src : \"<%= allTests %>\",\n        dest : \"testResults.xml\"\n        options : {\n          reporter : \"xunit\"\n        }\n      }\n    },\n    allTests : \"tests/*\"\n    ...\n\nThe example above uses the [_compact format_ for specifying files](http://gruntjs.com/configuring-tasks#compact-format)\nas well as [templates](http://gruntjs.com/configuring-tasks#templates).\n\nOne destination file (``dest``) can be specified per target.  It will contain the output of all the suites in the target.  If no\ndestination file is specified, the output will go to the console.\n\nPaths for both source and destination files are relative to the directory that the ``Gruntfile.js`` is in.\n\nResults are summed by target.  Grunt-vows-runner doesn't combine the results of multiple targets.\n\nSuites within a target are run concurrently; faster suites will finish first.  Targets in grunt are always run sequentially.\n\n####Options\n\nOptions can be placed at the task (``vows``), target, or suite level.\n\nHere is an example of each:\n\n_Gruntfile.js_ (task- and target-level options)\n\n    ...\n    vows : {\n      options : {\n        reporter : \"spec\"\n      },\n      most : {\n        src : [\"test/*\", \"!test/chattyTests.js\"]\n      },\n      chatty : {\n        src : \"test/chattyTests.js\",\n        options : {\n          reporter : \"silent\"\n        }\n      }\n    }\n    ...\n\n_test/errorTests.js_ (suite-level options)\n\n    ...\n    vows.describe('Error Handling').addBatch({\n    ...\n    }).export(module, {error : false});\n    ...\n\nThe following options are available:\n\n* ``error``\n * Whether or not vows should handle errors in topics for you.  Set ``error : false`` if you want to handle your own errors.\n The first argument to your vows will be reserved for errors.\n* ``reporter``\n * silent, spec, json, tap, xunit, dot-matrix.  (Look in [vows/lib/vows/reporters](https://github.com/cloudhead/vows/tree/master/lib/vows/reporters)\n  for a complete list.)\n* ``matcher``\n * a javascript [RegExp object](http://www.w3schools.com/jsref/jsref_obj_regexp.asp); only run tests whose titles match this\n object.\n* ``isolate``\n * Run each suite in its own process.  This is useful if the system-under-test uses the node process object internally.\n* ``disabled``\n * Temporarily disable tests for a target.\n\n###Command-Line Options\n\ngrunt-vows-runner incorporates the following grunt command-line options, if present:\n\n* ``--no-color``\n* ``--verbose``\n\n###Alternatives\n\nIf you would like a grunt plugin that simply forwards options to the existing vows command-line runner,\nsee [grunt-vows](https://github.com/CMTegner/grunt-vows).\n\n","maintainers":[{"name":"adamstallard","email":"adam@sweedl.com"}],"time":{"modified":"2022-06-18T16:16:07.475Z","created":"2013-02-20T06:22:23.538Z","0.1.0":"2013-02-20T06:22:26.214Z","0.1.1":"2013-02-21T14:51:19.267Z","0.1.2":"2013-02-21T15:54:06.899Z","0.1.3":"2013-02-26T06:53:34.712Z","0.2.0":"2013-02-28T16:59:17.615Z","0.2.1":"2013-03-07T07:24:31.526Z","0.3.0":"2013-03-20T15:50:33.044Z","0.4.0":"2013-04-24T00:50:45.442Z","0.4.1":"2013-04-24T01:13:25.033Z","0.4.2":"2013-04-24T01:15:30.112Z","0.4.3":"2013-04-24T01:18:25.933Z","0.4.4":"2013-04-24T01:26:41.339Z","0.5.0":"2013-05-05T06:38:29.054Z","0.5.1":"2013-05-05T06:50:47.558Z","0.5.2":"2013-05-10T14:16:56.406Z","0.6.0":"2013-07-11T04:47:12.267Z"},"author":{"name":"Adam Stallard","email":"adam@goalzen.org","url":"goalzen.org"},"repository":{"type":"git","url":"https://github.com/goalzen/grunt-vows-runner.git"}}