Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replace the JS test runner #367

Merged
merged 3 commits into from
Oct 21, 2024
Merged

Replace the JS test runner #367

merged 3 commits into from
Oct 21, 2024

Conversation

stof
Copy link
Contributor

@stof stof commented Aug 8, 2024

Instead of the outdated setup using the unmaintained phantomjs, this now uses @web/test-runner and runs tests in an actual browser.

I also updated QUnit to its latest version instead of the totally outdated version used before.
To run tests locally, I kept the index.html that supports standalone run of QUnit, even though npm test -- --manual is also possible thanks to the manual mode of @web/test-runner

stof added 2 commits August 8, 2024 17:27
This uses npm to install the testsuite dependencies instead of vendoring
them in the project to make the setup easier to maintain.
This also removes the file loading the ES5-shim as all maintained
browsers support ES5 natively anyway.
PhantomJS is not maintained anymore and the setup was broken. The new
setup uses `@web/test-runner` to run the QUnit tests in an actual
browser.
@stof
Copy link
Contributor Author

stof commented Oct 17, 2024

@monteiro could you merge this PR replacing the CI setup for JS files, to unlock other PRs like #360 please ?

@monteiro monteiro merged commit 4907baf into willdurand:master Oct 21, 2024
8 checks passed
@monteiro
Copy link
Collaborator

Thanks @stof

@stof stof deleted the js_test_runner branch October 21, 2024 09:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants