| "description": "DOM-less simple JavaScript BDD testing framework for Node", |
| "name": "Chris Moultrie", |
| "email": "chris@moultrie.org" |
| "url": "https://github.com/mhevery/jasmine-node.git" |
| "email": "misko@hevery.com" |
| "maintainers": "Martin Häger <martin.haeger@gmail.com>", |
| "coffee-script": ">=1.0.1", |
| "jasmine-reporters": ">=0.2.0", |
| "underscore": ">= 1.3.1", |
| "jasmine-node": "bin/jasmine-node" |
| "main": "lib/jasmine-node", |
| "test": "node lib/jasmine-node/cli.js spec" |
| "readme": "jasmine-node\n======\n\n[](http://travis-ci.org/spaghetticode/jasmine-node)\n\nThis node.js module makes the wonderful Pivotal Lab's jasmine\n(http://github.com/pivotal/jasmine) spec framework available in\nnode.js.\n\njasmine\n-------\n\nVersion 1.3.1 of Jasmine is currently included with node-jasmine.\n\nwhat's new\n----------\n* Ability to test specs written in Literate Coffee-Script\n* Teamcity Reporter reinstated.\n* Ability to specify multiple files to test via list in command line\n* Ability to suppress stack trace with <code>--noStack</code>\n* Async tests now run in the expected context instead of the global one\n* --config flag that allows you to assign variables to process.env\n* Terminal Reporters are now available in the Jasmine Object #184\n* Done is now available in all timeout specs #199\n* <code>afterEach</code> is available in requirejs #179\n* Editors that replace instead of changing files should work with autotest #198\n* Jasmine Mock Clock now works!\n* Autotest now works!\n* Using the latest Jasmine!\n* Verbose mode tabs <code>describe</code> blocks much more accurately!\n* --coffee now allows specs written in Literate CoffeeScript (.litcoffee)\n\ninstall\n------\n\nTo install the latest official version, use NPM:\n\n npm install jasmine-node -g\n\nTo install the latest _bleeding edge_ version, clone this repository and check\nout the `beta` branch.\n\nusage\n------\n\nWrite the specifications for your code in \\*.js and \\*.coffee files in the\nspec/ directory (note: your specification files must end with either\n.spec.js, .spec.coffee or .spec.litcoffee; otherwise jasmine-node won't find them!). You can use sub-directories to better organise your specs.\n\nIf you have installed the npm package, you can run it with:\n\n jasmine-node spec/\n\nIf you aren't using npm, you should add `pwd`/lib to the $NODE_PATH\nenvironment variable, then run:\n\n node lib/jasmine-node/cli.js\n\n\nYou can supply the following arguments:\n\n * <code>--autotest</code>, provides automatic execution of specs after each change\n * <code>--coffee</code>, allow execution of .coffee and .litcoffee specs\n * <code>--color</code>, indicates spec output should uses color to\nindicates passing (green) or failing (red) specs\n * <code>--noColor</code>, do not use color in the output\n * <code>-m, --match REGEXP</code>, match only specs comtaining \"REGEXPspec\"\n * <code>--matchall</code>, relax requirement of \"spec\" in spec file names\n * <code>--verbose</code>, verbose output as the specs are run\n * <code>--junitreport</code>, export tests results as junitreport xml format\n * <code>--output FOLDER</code>, defines the output folder for junitreport files\n * <code>--teamcity</code>, converts all console output to teamcity custom test runner commands. (Normally auto detected.)\n * <code>--runWithRequireJs</code>, loads all specs using requirejs instead of node's native require method\n * <code>--requireJsSetup</code>, file run before specs to include and configure RequireJS\n * <code>--test-dir</code>, the absolute root directory path where tests are located\n * <code>--nohelpers</code>, does not load helpers\n * <code>--forceexit</code>, force exit once tests complete\n * <code>--captureExceptions</code>, listen to global exceptions, report them and exit (interferes with Domains in NodeJs, so do not use if using Domains as well\n * <code>--config NAME VALUE</code>, set a global variable in process.env\n * <code>--noStack</code>, suppress the stack trace generated from a test failure\n\nIndividual files to test can be added as bare arguments to the end of the args.\n\nExample:\n\n`jasmine-node --coffee spec/AsyncSpec.coffee spec/CoffeeSpec.coffee spec/SampleSpecs.js`\n\nasync tests\n-----------\n\njasmine-node includes an alternate syntax for writing asynchronous tests. Accepting\na done callback in the specification will trigger jasmine-node to run the test\nasynchronously waiting until the done() callback is called.\n\n```javascript\n it(\"should respond with hello world\", function(done) {\n request(\"http://localhost:3000/hello\", function(error, response, body){\n expect(body).toEqual(\"hello world\");\n done();\n });\n });\n```\n\nAn asynchronous test will fail after 5000 ms if done() is not called. This timeout\ncan be changed by setting jasmine.DEFAULT_TIMEOUT_INTERVAL or by passing a timeout\ninterval in the specification.\n\n it(\"should respond with hello world\", function(done) {\n request(\"http://localhost:3000/hello\", function(error, response, body){\n done();\n }, 250); // timeout after 250 ms\n });\n\nCheckout spec/SampleSpecs.js to see how to use it.\n\nrequirejs\n---------\n\nThere is a sample project in `/spec-requirejs`. It is comprised of:\n\n1. `requirejs-setup.js`, this pulls in our wrapper template (next)\n1. `requirejs-wrapper-template`, this builds up requirejs settings\n1. `requirejs.sut.js`, this is a __SU__bject To __T__est, something required by requirejs\n1. `requirejs.spec.js`, the actual jasmine spec for testing\n\ndevelopment\n-----------\n\nInstall the dependent packages by running:\n\n npm install\n\nRun the specs before you send your pull request:\n\n specs.sh\n\n__Note:__ Some tests are designed to fail in the specs.sh. After each of the\nindividual runs completes, there is a line that lists what the expected\nPass/Assert/Fail count should be. If you add/remove/edit tests, please be sure\nto update this with your PR.\n\n\nchangelog\n---------\n\n* _1.7.1 - Removed unneeded fs dependency (thanks to\n [kevinsawicki](https://github.com/kevinsawicki)) Fixed broken fs call in\n node 0.6 (thanks to [abe33](https://github.com/abe33))_\n* _1.7.0 - Literate Coffee-Script now testable (thanks to [magicmoose](https://github.com/magicmoose))_\n* _1.6.0 - Teamcity Reporter Reinstated (thanks to [bhcleek](https://github.com/bhcleek))_\n* _1.5.1 - Missing files and require exceptions will now report instead of failing silently_\n* _1.5.0 - Now takes multiple files for execution. (thanks to [abe33](https://github.com/abe33))_\n* _1.4.0 - Optional flag to suppress stack trace on test failure (thanks to [Lastalas](https://github.com/Lastalas))_\n* _1.3.1 - Fixed context for async tests (thanks to [omryn](https://github.com/omryn))_\n* _1.3.0 - Added --config flag for changeable testing environments_\n* _1.2.3 - Fixed #179, #184, #198, #199. Fixes autotest, afterEach in requirejs, terminal reporter is in jasmine object, done function missing in async tests_\n* _1.2.2 - Revert Exception Capturing to avoid Breaking Domain Tests_\n* _1.2.1 - Emergency fix for path reference missing_\n* _1.2.0 - Fixed #149, #152, #171, #181, #195. --autotest now works as expected, jasmine clock now responds to the fake ticking as requested, and removed the path.exists warning_\n* _1.1.1 - Fixed #173, #169 (Blocks were not indented in verbose properly, added more documentation to address #180_\n* _1.1.0 - Updated Jasmine to 1.3.1, fixed fs missing, catching uncaught exceptions, other fixes_\n", |
| "readmeFilename": "README.md", |
| "url": "https://github.com/mhevery/jasmine-node/issues" |
| "_id": "jasmine-node@1.7.1", |
| "shasum": "5df8182da5f9a4612d07089417248d4bc2a01a92" |
| "_from": "jasmine-node@1.7.1", |
| "_resolved": "https://registry.npmjs.org/jasmine-node/-/jasmine-node-1.7.1.tgz" |
