e429af8220
FIX: QUnit tests could time out based on load order ( #12342 )
...
By default our QUnit test runner starts automatically. This is normally
fine but for our `run-qunit.js` script we add a bunch of QUnit events
using `eval` and sometimes those events were added after the tests
already started/finished resulting in a hang.
This adds a new parameter that will cause QUnit not to run
automatically, which the runner uses, then triggers a `start()` when it
knows it's ready.
2021-03-10 13:32:20 -05:00
c6a1042950
DEV: prettier 2.2.1 ( #11862 )
2021-01-27 12:39:20 +01:00
ac5c457d9e
DEV: Move the failures list to the end of output ( #11082 )
...
No more scrolling up each time the tests fail.
(Alternatively, we could just not show the slowest tests list when there are any failures 🤷♂️ )
2020-10-30 17:29:45 +01:00
f2a6791ce2
DEV: linting of run-qunit.js ( #10728 )
2020-09-23 12:52:11 +02:00
78d443ad40
DEV: Add linebreaks around qunit "Tests timed out" message
2020-08-07 09:32:57 -04:00
09254410ea
FIX: Only raise proper `"error"` messages
...
Also support "1" for `QUNIT_FAIL_FAST` to make it consistent with other
arguments.
2020-08-05 16:27:06 -04:00
0c8365a1a2
Improve output for QUnit tests in CI:
...
* Uses fewer lines of output
* Always outputs error at the end even if timeout
* Support for QUNIT_FAIL_FAST ENV var to quit at first failure
2020-08-05 13:43:14 -04:00
18e3339580
Quit tests early, output seed to easily reproduce failure
2020-08-05 12:21:16 -04:00
8a50ab45aa
DEV: use REPORT_REQUESTS=1 to find all requests
...
We can use this to profile our pretender and ensure nothing is superfluous
and nothing is missing
2020-04-02 16:01:49 +11:00
8dcda65837
DEV: Correct error message check in run-qunit
...
Followup to 43ca1bb132
2019-12-12 14:06:06 +00:00
43ca1bb132
DEV: Handle occasional 'No inspectable targets' error in run-qunit
...
This is to work around https://github.com/GoogleChrome/chrome-launcher/issues/145
2019-12-12 13:24:58 +00:00
584021ca38
DEV: Correct error handling in run-qunit
...
runAllTests is an async function, so the try/catch block does not help. The function always returns a promise, so we need to use `.catch` to handle errors. Previously, raised errors were ignored, and the process continued running until it timed out.
2019-12-11 16:50:31 +00:00
b4d42d1151
DEV: removes memory profiling from qunit tests ( #8120 )
...
Most of the work on it has been done and it's un-necessary work for now.
2019-10-01 22:17:53 +02:00
4aefe589de
DEV: rake qunit:test was crashing on macOS due to a flag ( #8119 )
...
flag: --disable-software-rasterizer
2019-10-01 20:40:48 +02:00
460d431621
DEV: uses ember-cli recommended chrome flags ( #7939 )
2019-07-25 11:38:05 +02:00
cb08d3cc26
DEV: adds module debugging to js tests ( #7751 )
2019-06-11 23:14:42 +02:00
43a46df075
Revert "DEV: no-sandbox flag is deprecated ( #7660 )"
...
This reverts commit d4d42bc61c
2019-06-03 23:03:30 +02:00
d4d42bc61c
DEV: no-sandbox flag is deprecated ( #7660 )
2019-05-31 13:22:03 +02:00
3e4e3fc7d7
DEV: adds memory/event listeners reporting ( #7575 )
2019-05-20 16:35:23 +02:00
f41aa5cb98
EXPERIMENTAL: attempts to gather info if chrome runner crashed ( #7562 )
2019-05-16 18:00:57 +02:00
ea214b2b0c
DEV: logs tests exception when running qunit on headless chrome ( #7553 )
2019-05-16 08:48:08 +02:00
5b36fadec9
DEV: correct qunit runner for autospec
...
Was no longer working on latest nodes, unlink expects a callback
Also cleans up eslint warnings.
2019-03-20 16:44:00 +11:00
404acef6e3
DEV: Move `run-qunit.js` out of the vendor directory
2018-12-03 16:16:37 +00:00
Robin Ward
Joffrey JAFFEUX
Jarek Radosz
Penar Musaraj
Sam Saffron
David Taylor