-
-
Notifications
You must be signed in to change notification settings - Fork 35.5k
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
Puppeteer E2E test: Auto-download browser #25380
Conversation
Unrelated question: where do I set the global timeout on the e2e tests ? |
What is the "global timeout"? You should either increase |
Ops... Some conflicts to resolve... |
It's conflicting with #25384, I think... |
I deleted |
@mrdoob I think I resolved the conflicts. |
Qunit node module now found in base since PR #25380
* Update Unit Test Readme Update unit test readme to reflect changes since #25380 Avoid building the library and flagging the files as changed (tests run off source) Add notes to help people running unit tests. ColorManagement.enabled is false by default. Tune logging so only genuine test failure messages are displayed. * Update ColorManagement.tests.js Minimize the console messages captured.
Related issue: #24109
Description
Make Puppeteer auto-download latest Chromium browser and merge
test/package.json
with the corepackage.json
(they were splitted becausepuppeteer
package is very large -- nowpuppeteer-core
package is used and the browser is downloaded by the script).