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

Puppeteer E2E test: Auto-download browser #25380

Merged
merged 5 commits into from
Jan 31, 2023

Conversation

LeviPesin
Copy link
Contributor

Related issue: #24109

Description

Make Puppeteer auto-download latest Chromium browser and merge test/package.json with the core package.json (they were splitted because puppeteer package is very large -- now puppeteer-core package is used and the browser is downloaded by the script).

@epreston
Copy link
Contributor

Unrelated question: where do I set the global timeout on the e2e tests ?

@LeviPesin
Copy link
Contributor Author

What is the "global timeout"? You should either increase idleTime variable (for how long there should be no network connections) or parseTime variable (for how long to parse data after loading).

@marcofugaro
Copy link
Contributor

marcofugaro commented Jan 30, 2023

It takes only around 10 seconds to download chrome on github actions, not bad!

image

@mrdoob mrdoob added this to the r150 milestone Jan 31, 2023
@mrdoob
Copy link
Owner

mrdoob commented Jan 31, 2023

Ops... Some conflicts to resolve...

@LeviPesin
Copy link
Contributor Author

It's conflicting with #25384, I think...

@mrdoob
Copy link
Owner

mrdoob commented Jan 31, 2023

I deleted test/package-lock.json. Now there are only conflicts in pupeteer.js.

@LeviPesin
Copy link
Contributor Author

LeviPesin commented Jan 31, 2023

@mrdoob I think I resolved the conflicts.

@mrdoob mrdoob merged commit 73b3f24 into mrdoob:dev Jan 31, 2023
@LeviPesin LeviPesin deleted the puppeteer-autodownload-browser branch January 31, 2023 05:57
@epreston epreston mentioned this pull request Feb 2, 2023
mrdoob pushed a commit that referenced this pull request Feb 2, 2023
Qunit node module now found in base since PR #25380
mrdoob pushed a commit that referenced this pull request Feb 7, 2023
* 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.
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.

4 participants