launchpad development|
Size: 1264
Comment:
|
← Revision 17 as of 2011-12-21 20:34:00 ⇥
Size: 2511
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| ## page was renamed from TestingJavaScript | |
| Line 3: | Line 4: |
| = Testing JavaScript = | = YUIXHR Integration Testing in JavaScript = |
| Line 5: | Line 6: |
| Launchpad's JavaScript testing consists of unit tests built with [[http://developer.yahoo.com/yui/3/|YUI 3's]] [[http://developer.yahoo.com/yui/3/yuitest/|yuitest]] library, and automated acceptance testing using the Windmill framework. We use the GradedBrowserSupport chart to determine which browsers code should be regularly tested in. | Launchpad's JavaScript testing is built arount [[http://developer.yahoo.com/yui/3/|YUI 3's]] [[http://developer.yahoo.com/yui/3/yuitest/|yuitest]] library. We use the GradedBrowserSupport chart to determine which browsers code should be regularly tested in. |
| Line 7: | Line 10: |
| == Testing the lazr-js Widget Library == === Unit testing === |
Every JavaScript component should be tested first and foremost using [[JavascriptUnitTesting|unit testing]]. |
| Line 10: | Line 12: |
| The unit tests can be run stand-alone from the [[https://edge.launchpad.net/lazr-js|lazr-js]] project. | We have infrastructure to write tests centered on the integration between the JavaScript component and the app server (regular API or view/++model++ page api.) |
| Line 12: | Line 15: |
| To run the lazr-js test suite: | These are still written using the `yuitest` library, but they are loaded and can access a "real" appserver (the one started by the AppServerLayer). |
| Line 14: | Line 18: |
| 1. Grab a copy of the lazr-js trunk: {{{ bzr get lp:lazr-js }}} 1. Change to the `tests/` directory of the component you want to test. For example, `$ cd src/inlineeditor/tests/`. 1. Load any HTML files you find into your browser. The test suite will run automatically. |
The testing framwork also allows testing integration of the component on the page itself (answering the question: Is it hooked up properly?) through loading a page through an iframe for inspection. XXX: Give more information on how to do this. |
| Line 18: | Line 22: |
| ''This process is really onerous - maybe the YUI 2 Test``Manager offers a better way to handle this. -- [[LaunchpadHome:mars]] <<DateTime(2009-02-26T15:43:40Z)>>'' | == Creating the tests == |
| Line 20: | Line 24: |
| === Acceptance testing === | * Use `standard_yuixhr_test_template.js` `standard_yuixhr_test_template.py` in the root of the Launchpad tree as templates. Copy and rename both files to the same directory. (You can put them in the usual `javascript/tests` subdirectory.) * The `.js` file contains the tests using the standard `yuitest` library. * The `.py` file contains fixtures that will operate within the app server. They should create content (through the standard LaunchpadObjectFactory) that will be accessed by the test (through. The database is automatically reset after every test. |
| Line 22: | Line 32: |
| You can try out stand-alone versions of the lazr-js widgets using the `examples/` pages. E.g.: | == Running the tests == |
| Line 24: | Line 34: |
| {{{ $ firefox examples/inlineedit/index.html }}} |
* We have tests discoverer that will make these tests run automatically as part of the test suite. * To run manually, start the test-appserver using: {{{ make run-testapp }}} * Visit in your browser `https://launchpad.dev:8085/+yuitest/`''path-to-test-basename-from-root''. So for example, if you copied the templates to `lib/lp/bugs/javascript/tests/test_some_xhr.js`, you can run the tests by accessing `https://launchapd.dev:8085/+yuitest/lib/lp/bugs/javascript/tests/test_some_xhr`. |
| Line 28: | Line 43: |
| == Gotchas == * When loading `https://launchpad.dev:8085/+yuitest` if you see "cannot import Python fixture file" it may be due to not having {{{__init__.py}}} files in the directory and parent directories where you've put your new `.py` test fixture. |
YUIXHR Integration Testing in JavaScript
Launchpad's JavaScript testing is built arount YUI 3's yuitest library. We use the GradedBrowserSupport chart to determine which browsers code should be regularly tested in.
Every JavaScript component should be tested first and foremost using unit testing.
We have infrastructure to write tests centered on the integration between the JavaScript component and the app server (regular API or view/++model++ page api.)
These are still written using the yuitest library, but they are loaded and can access a "real" appserver (the one started by the AppServerLayer).
The testing framwork also allows testing integration of the component on the page itself (answering the question: Is it hooked up properly?) through loading a page through an iframe for inspection. XXX: Give more information on how to do this.
Creating the tests
Use standard_yuixhr_test_template.js standard_yuixhr_test_template.py in the root of the Launchpad tree as templates. Copy and rename both files to the same directory. (You can put them in the usual javascript/tests subdirectory.)
The .js file contains the tests using the standard yuitest library.
The .py file contains fixtures that will operate within the app server. They should create content (through the standard LaunchpadObjectFactory) that will be accessed by the test (through. The database is automatically reset after every test.
Running the tests
- We have tests discoverer that will make these tests run automatically as part of the test suite.
- To run manually, start the test-appserver using:
make run-testapp
Visit in your browser https://launchpad.dev:8085/+yuitest/path-to-test-basename-from-root. So for example, if you copied the templates to lib/lp/bugs/javascript/tests/test_some_xhr.js, you can run the tests by accessing https://launchapd.dev:8085/+yuitest/lib/lp/bugs/javascript/tests/test_some_xhr.
Gotchas
When loading https://launchpad.dev:8085/+yuitest if you see "cannot import Python fixture file" it may be due to not having __init__.py files in the directory and parent directories where you've put your new .py test fixture.
