Difference between revisions of "Using Qunit for testing JS"
From Dreamwidth Notes
(Add links, categories, plea for more.) |
(Mention sinon, or else!) |
||
| Line 1: | Line 1: | ||
| − | You can use [http://docs.jquery.com/Qunit Qunit] for automated testing of your JS front-end code using jQuery and jQuery UI (the JS libraries we use for new UI development). There are some sample tests in [http://hg.dwscoalition.org/dw-free/file/tip/views/dev/tests/ the views/dev/test/ directory]. | + | You can use [http://docs.jquery.com/Qunit Qunit] and [http://sinonjs.org/qunit/ Sinon] for automated testing of your JS front-end code using jQuery and jQuery UI (the JS libraries we use for new UI development). There are some sample tests in [http://hg.dwscoalition.org/dw-free/file/tip/views/dev/tests/ the views/dev/test/ directory]. The Qunit and Sinon code itself lives in [http://hg.dwscoalition.org/dw-free/file/tip/htdocs/js/tests/ the htdocs/js/tests/ directory]. |
For automated testing of back-end components, see [[Dev Testing]]. | For automated testing of back-end components, see [[Dev Testing]]. | ||
Revision as of 14:16, 26 February 2011
You can use Qunit and Sinon for automated testing of your JS front-end code using jQuery and jQuery UI (the JS libraries we use for new UI development). There are some sample tests in the views/dev/test/ directory. The Qunit and Sinon code itself lives in the htdocs/js/tests/ directory.
For automated testing of back-end components, see Dev Testing.
This page needs to be updated with whatever happens as a result of bug 3525.
This article could really use expansion. If you have information to add, please edit this page!
