-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
tests: add devtools e2e test runner #14110
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i'm not sure why you're using contentshell, but the e2e tests just use chromium in both local devtools dev and the devtools CI bots. doing that should allow us to delete some stuff :)
d5bf0df
to
00202f1
Compare
Took awhile to wrangle CI stuff, making sure to only build DT the once. The trick was to zip the entire CDT directory in the shared build artifacts cache. |
Co-authored-by: Adam Raine <6752989+adamraine@users.noreply.github.com>
Pretty much the same structure as the webtests, but simpler. Re-uses some scripts from the webtests folder. Can re-org whenever we actually delete webtests.
Waiting on this to land: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/3682120