Opened on 01/24/2017 at 04:32:01 PM
Closed on 02/24/2017 at 10:58:03 AM
Last modified on 05/04/2017 at 01:48:58 PM
#4838 closed change (fixed)
Use nodeunit framework for integration tests running in browser
| Reported by: | trev | Assignee: | trev |
|---|---|---|---|
| Priority: | P4 | Milestone: | |
| Module: | Core | Keywords: | |
| Cc: | fhd | Blocked By: | |
| Blocking: | Platform: | Unknown / Cross platform | |
| Ready: | yes | Confidential: | no |
| Tester: | Unknown | Verified working: | no |
| Review URL(s): | |||
Description (last modified by fhd)
Background
#4726 introduced integration tests running in a headless browser via PhantomJS. These tests are currently using the QUnit framework however with a number of implications:
- The boilerplate is significantly different from our other code.
- An HTML file is required for each tests where a JS file should be enough.
- The output format is very different and less informative than for the other tests.
What to change
Use PhantomJS directly in order to run our tests with the nodeunit framework (using the browser distribution we have in the nodeunit module already).
Attachments (0)
Change History (4)
Note: See
TracTickets for help on using
tickets.
A commit referencing this issue has landed:
Issue 4838 - Use nodeunit framework for integration tests running in browser