{
  "name": "qunitjs",
  "title": "QUnit",
  "description": "An easy-to-use JavaScript Unit Testing framework.",
  "version": "1.14.0",
  "homepage": "http://qunitjs.com",
  "author": {
    "name": "jQuery Foundation and other contributors",
    "url": "https://github.com/jquery/qunit/blob/1.14.0/AUTHORS.txt"
  },
  "repository": {
    "type": "git",
    "url": "git://github.com/jquery/qunit.git"
  },
  "keywords": [
    "testing",
    "unit",
    "jquery"
  ],
  "bugs": {
    "url": "https://github.com/jquery/qunit/issues"
  },
  "licenses": [
    {
      "type": "MIT",
      "url": "https://github.com/jquery/qunit/blob/1.14.0/MIT-LICENSE.txt"
    }
  ],
  "dependencies": {},
  "devDependencies": {
    "grunt": "0.4.2",
    "grunt-contrib-concat": "0.3.0",
    "grunt-contrib-jshint": "0.7.2",
    "grunt-contrib-qunit": "0.3.0",
    "grunt-contrib-watch": "0.5.3",
    "grunt-git-authors": "1.2.0",
    "testswarm": "1.1.0"
  },
  "scripts": {
    "test": "grunt",
    "prepublish": "grunt build"
  },
  "main": "qunit/qunit.js",
  "readme": "[![Build Status](http://jenkins.jquery.com/job/QUnit/badge/icon)](http://jenkins.jquery.com/job/QUnit/)\n\n# [QUnit](http://qunitjs.com) - A JavaScript Unit Testing Framework.\n\nQUnit is a powerful, easy-to-use, JavaScript unit testing framework. It's used by the jQuery\nproject to test its code and plugins but is capable of testing any generic\nJavaScript code (and even capable of testing JavaScript code on the server-side).\n\nQUnit is especially useful for regression testing: Whenever a bug is reported,\nwrite a test that asserts the existence of that particular bug. Then fix it and\ncommit both. Every time you work on the code again, run the tests. If the bug\ncomes up again - a regression - you'll spot it immediately and know how to fix\nit, because you know what code you just changed.\n\nHaving good unit test coverage makes safe refactoring easy and cheap. You can\nrun the tests after each small refactoring step and always know what change\nbroke something.\n\nQUnit is similar to other unit testing frameworks like JUnit, but makes use of\nthe features JavaScript provides and helps with testing code in the browser, e.g.\nwith its stop/start facilities for testing asynchronous code.\n\nIf you are interested in helping developing QUnit, you are in the right place.\nFor related discussions, visit the\n[QUnit and Testing forum](http://forum.jquery.com/qunit-and-testing).\n\n## Development\n\nTo submit patches, fork the repository, create a branch for the change. Then implement\nthe change, run `grunt` to lint and test it, then commit, push and create a pull request.\n\nInclude some background for the change in the commit message and `Fixes #nnn`, referring\nto the issue number you're addressing.\n\nTo run `grunt`, you need `node` and `npm`, then `npm install grunt -g`. That gives you a global\ngrunt binary. For additional grunt tasks, also run `npm install`.\n\n## Releases\n\nUse [jquery-release](https://github.com/jquery/jquery-release). The following aren't yet handled there:\n\nInstall [git-extras](https://github.com/visionmedia/git-extras) and run `git changelog` to update History.md. Clean up the changelog, removing merge commits or whitespace cleanups. Commit this before using the release script.\n\nThen run the script.\n\nUpdate web sites, replacing previous versions with new ones:\n\n* jquery/jquery-wp-content themes/jquery/footer-qunit.php\n* jquery/qunitjs.com pages/index.html\n\nFinally announce on Twitter @qunitjs\n\n\tReleased @VERSION: https://github.com/jquery/qunit/tree/@VERSION\n\tChangelog: https://github.com/jquery/qunit/blob/@VERSION/History.md",
  "readmeFilename": "README.md",
  "_id": "qunitjs@1.14.0",
  "_from": "qunitjs@"
}