Tests: Migrate test runner to jquery-test-runner #2325
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
I've moved all the code from
test/runner
into a package called jquery-test-runner. The changes to this repo are fairly simple. It uses the binary included in that package to run tests in browsers using selenium and browserstack.Some things to note:
jtr
(alias forjquery-test-runner
) binary includes several commands. The default command is for test runs (jtr
orjtr run
). jtr also includesjtr serve
, which has a-p
(--port
) option (rather than an env var). Seenpx jtr --help
for all commands and options.jquery-test-runner
.test/runner
folder, which means the recent changes to allow Edge runs in IE-mode have been kept,express
is not used for the test server, etc. jquery-migrate and jquery-ui will now be able to take advantage of those changes.jquery-test-runner
can take a YAML config file, with support for all of the same options as the command line. I considered JSON and JS, but I liked how terse the YAML was. See jtr-isolate.yml for an example, which is used to create a separate run for each module in BrowserStack runs while still sharing browser instances.Ref jquery/jquery#5604