Difference between revisions of "Using Qunit for testing JS"
From Dreamwidth Notes
Foxfirefey (Talk | contribs) (updated links to git) |
|||
| Line 2: | Line 2: | ||
For automated testing of back-end components, see [[Dev Testing]]. | For automated testing of back-end components, see [[Dev Testing]]. | ||
| − | |||
| − | |||
{{MoreInfo}} | {{MoreInfo}} | ||
[[Category: Development]] | [[Category: Development]] | ||
[[Category: Testing]] | [[Category: Testing]] | ||
Latest revision as of 10:10, 4 August 2014
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. There's some additional Dreamwidth-specific glue in DW::Controller::Dev.
For automated testing of back-end components, see Dev Testing.
This article could really use expansion. If you have information to add, please edit this page!
