{
  "name": "vows-si",
  "description": "Asynchronous BDD & continuous integration for node.js that works with node 0.10+",
  "url": "http://vowsjs.org",
  "keywords": [
    "testing",
    "spec",
    "test",
    "BDD"
  ],
  "author": {
    "name": "Alexis Sellier",
    "email": "self@cloudhead.net"
  },
  "contributors": [
    {
      "name": "Charlie Robbins",
      "email": "charlie.robbins@gmail.com"
    }
  ],
  "dependencies": {
    "eyes": ">=0.1.6",
    "diff": "~1.0.3",
    "glob": "3.1.x",
    "setimmediate": "1.0.1"
  },
  "main": "./lib/vows",
  "repository": {
    "type": "git",
    "url": "https://github.com/cloudhead/vows.git"
  },
  "bin": {
    "vows": "./bin/vows"
  },
  "directories": {
    "test": "./test",
    "bin": "./bin"
  },
  "version": "0.7.1",
  "scripts": {
    "test": "node ./bin/vows --spec"
  },
  "readme": "Vows\n====\n\n> Asynchronous BDD & continuous integration for node.js\n\n#### <http://vowsjs.org> #\n\nintroduction\n------------\nThere are two reasons why we might want asynchronous testing. The first, and obvious reason is that node.js is asynchronous, and therefore our tests need to be. The second reason is to make test suites which target I/O libraries run much faster.\n\n_Vows_ is an experiment in making this possible, while adding a minimum of overhead.\n\nsynopsis\n--------\n\n    var vows = require('vows'),\n        assert = require('assert');\n\n    vows.describe('Deep Thought').addBatch({\n        'An instance of DeepThought': {\n            topic: new DeepThought,\n\n            'should know the answer to the ultimate question of life': function (deepThought) {\n                assert.equal (deepThought.question('what is the answer to the universe?'), 42);\n            }\n        }\n    });\n\ncoverage reporting\n------------------\nCode coverage reporting is available if _instrumented_ code is detected.  Currently only _instrumentation_ via [node-jscoverage](https://github.com/visionmedia/node-jscoverage) is supported.  When _instrumented_ code is detected and coverage reporting is enabled using any of the `--cover-plain`, `--cover-html`, or `--cover-json` options a code coverage map is generated.\n\n### downloading and installing [node-jscoverage](https://github.com/visionmedia/node-jscoverage)\n[node-jscoverage](https://github.com/visionmedia/node-jscoverage) is a binary package that needs to be compiled from source:\n\n    $ git clone https://github.com/visionmedia/node-jscoverage.git\n    $ cd node-jscoverage/\n    $ ./configure\n    checking for a BSD-compatible install... /usr/bin/install -c\n    checking whether build environment is sane... yes\n    [...]\n    $ make && sudo make install\n\n### instrumenting with jscoverage\n\n    $ jscoverage myfile.js myfile-instrumented.js\n    \ninstallation\n------------\n\n    $ npm install vows\n\ndocumentation\n-------------\n\nHead over to <http://vowsjs.org>\n\nrun tests\n-------------\n\n```\n  npm test\n```\n\nauthors\n-------\n\nAlexis Sellier <<alexis@cloudhead.io>>, Charlie Robbins,\n\n*...and many others*\n\n",
  "readmeFilename": "README.md",
  "bugs": {
    "url": "https://github.com/cloudhead/vows/issues"
  },
  "_id": "vows-si@0.7.1",
  "dist": {
    "shasum": "65bf0e1c475a149483393fc30c1c0181e20ccd02"
  },
  "_from": "vows-si@~0.7",
  "_resolved": "https://registry.npmjs.org/vows-si/-/vows-si-0.7.1.tgz"
}
