discourse/test
Robin Ward 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
..
javascripts/integration/components REFACTOR: Replace global find with queryAll 2020-10-29 14:45:51 -04:00
run-qunit.js FIX: QUnit tests could time out based on load order (#12342) 2021-03-10 13:32:20 -05:00
smoke_test.js Revert "Reland "DEV: Add checks that assets do not modify cookies to smoke-test.js" (#9774)" (#9783) 2020-05-14 12:04:09 -07:00