launchpad development|
Size: 2245
Comment:
|
Size: 2516
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 4: | Line 4: |
| = Integration Testing in JavaScript = | = YUIXHR Integration Testing in JavaScript = |
| Line 10: | Line 10: |
| Every JavaScript component should be tested first and foremost using [[JavaScriptUnitTest|unit testing]]. | Every JavaScript component should be tested first and foremost using [[JavascriptUnitTesting|unit testing]]. |
| Line 30: | Line 30: |
| be accessed by the test (through. The database is automatically reset after every tests. | be accessed by the test (through. The database is automatically reset after every test. |
| Line 32: | Line 32: |
| == Running the tests === | == Running the tests == |
| Line 43: | 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` file 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 file test fixture.
