Difference between revisions of "Using Qunit for testing JS"
From Dreamwidth Notes
(Fix typo, add link to related open ticket) |
(Add links, categories, plea for more.) |
||
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] 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]. | ||
− | + | For automated testing of back-end components, see [[Dev Testing]]. | |
− | + | This page needs to be updated with whatever happens as a result of [http://bugs.dwscoalition.org/show_bug.cgi?id=3525 bug 3525]. | |
+ | |||
+ | {{MoreInfo}} | ||
+ | [[Category: Development]] | ||
+ | [[Category: Testing]] |
Revision as of 20:10, 24 February 2011
You can use 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 the views/dev/test/ 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!