Confirmed users
324
edits
AMO:Developers/JavaScriptTesting: Difference between revisions
Jump to navigation
Jump to search
AMO:Developers/JavaScriptTesting (view source)
Revision as of 18:58, 15 November 2010
, 15 November 2010no edit summary
mNo edit summary |
No edit summary |
||
| Line 28: | Line 28: | ||
*** [http://code.google.com/p/js-test-driver/wiki/QUnitAdapter Qunit for JsTestDriver] (Cannot do async testing) | *** [http://code.google.com/p/js-test-driver/wiki/QUnitAdapter Qunit for JsTestDriver] (Cannot do async testing) | ||
* Cons | * Cons | ||
** Might be tricky to get working for CI. | ** Might be tricky to get working for CI. We could load a single webpage in a web browser VM though and use builtin hooks to get test results | ||
** All user events need to be simulated by triggering the event or otherwise. | ** All user events need to be simulated by triggering the event or otherwise. | ||
** does not fit seamlessly into the current test suite (but maybe with NoseJS?) | ** does not fit seamlessly into the current test suite (but maybe with NoseJS?) | ||
==== [http://ianb.github.com/doctestjs/ doctest.js] ==== | |||
* Pros | |||
** Tests are in a more readable format | |||
** Doubles as documentation | |||
** some builtin utilities for async testing (like wait()) | |||
** runs in a browser, like production | |||
* Cons | |||
** Might be tricky to integrate into CI | |||
=== Mock Objects === | === Mock Objects === | ||