Jeff Williams 96f8875449 fix test breakage 7 vuotta sitten
..
fixtures 96f8875449 fix test breakage 7 vuotta sitten
lib 13f09f397c Clean up space-after-keywords lint violations 9 vuotta sitten
specs 2c6bcd4407 prevent crash when an anonymous class is passed as a parameter (#1416) 7 vuotta sitten
tutorials 7fd0f590ee don't crash on UTF-8 JSON files with a leading BOM (#1256, #1297) 7 vuotta sitten
README.md 621f012211 Remove Rhino support 9 vuotta sitten
async-callback.js e4236eaa42 remove most globals from jsdoc.js (#287) 12 vuotta sitten
jasmine-jsdoc.js 857a346f4b add `jasmine.replaceTagDictionary` and `jasmine.restoreTagDictionary` test helpers 7 vuotta sitten
reporter.js 41ccdf832e fix known issues on Node.js 0.11 (#555) 11 vuotta sitten
runner.js 0af05bea81 Add bluebird promises, make publish method work asynchronously if needed 10 vuotta sitten
spec-collection.js a097e2f299 get rid of jsdoc/util/runtime (#1383); delint 7 vuotta sitten

README.md

Testing JSDoc 3

Running Tests

Running tests is easy. Just change your working directory to the jsdoc folder and run the following command on Windows:

jsdoc -T

Or on OS X, Linux, and other POSIX-compliant platforms:

./jsdoc -T

Writing Tests

Adding tests is pretty easy, too. You can write tests for JSDoc itself (to make sure tags and the parser, etc. are working properly), tests for plugins, and/or tests for templates.

JSDoc 3 uses Jasmine (https://github.com/pivotal/jasmine) as its testing framework. Take a look at that project's wiki for documentation on writing tests in general.

Tests for JSDoc

Take a look at the files in the test directory for many examples of writing tests for JSDoc itself. The test\fixtures directory hold fixtures for use in the tests, and the test\specs directory holds the tests themselves.

Tests for plugins

Tests for plugins are found in the plugins\test directory. Plugins containing tests that were installed with the Jakefile install task will be run automatically.

Tests for templates

TODO