diff options
author | Michał Gołębiowski-Owczarek <m.goleb@gmail.com> | 2023-01-23 23:49:44 +0100 |
---|---|---|
committer | GitHub <noreply@github.com> | 2023-01-23 23:49:44 +0100 |
commit | b02a257f98688aa890e06a85672cd1a54c3ffa3a (patch) | |
tree | 0c5496cb1e61a964e35c73aa5696d0cc245e4f5f /src/ajax/script.js | |
parent | ce90a48450ba40586a6567235abb8fd2df84da97 (diff) | |
download | jquery-b02a257f98688aa890e06a85672cd1a54c3ffa3a.tar.gz jquery-b02a257f98688aa890e06a85672cd1a54c3ffa3a.zip |
Build: Run GitHub Action browser tests on Playwright WebKit
So far, we've been running browser tests on GitHub Actions in Chrome
and Firefox. Regular Safari is not available in GitHub Actions but
Playwright WebKit comes close to a dev version of Safari.
With this change, our GitHub CI & local test runs will invoke tests on
all actively developed browser engines on all PRs.
Also, our GitHub Actions browser tests are now running on Node.js 18.
Detection of the Playwright WebKit browser in support unit tests is done
by checking if the `test_browser` query parameter is set to `"Playwright"`;
this is a `karma-webkit-launcher` feature. Detecting that browser via
user agent as we normally do is hard as the UA on Linux is very similar
to a real Safari one but it actually uses a newer version of the engine.
In addition, we now allow to pass custom browsers when one needs it;
e.g., to run the tests in all three engines on Linux/macOS, run:
```
grunt && BROWSERS=ChromeHeadless,FirefoxHeadless,WebkitHeadless grunt karma:main
```
Closes gh-5190
Diffstat (limited to 'src/ajax/script.js')
0 files changed, 0 insertions, 0 deletions