-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
feat(tests): Run Playwright tests using bundles. #4551
Conversation
size-limit report
|
I think this is fine, as we want playwright to be where we focus on from now on. |
Found double-importing issue when testing bundles. Will update in a bit. |
Could not avoid updating 30 templates after all. :/ |
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.
This is a great start, thank you!
I left a few comments below, but I think the biggest thing right now is to address the ES6/tracing bundle question. See #4551 (comment).
packages/integration-tests/suites/public-api/addBreadcrumb/template.hbs
Outdated
Show resolved
Hide resolved
Co-authored-by: Katie Byers <lobsterkatie@gmail.com>
5602c3d
to
627de51
Compare
4e10222
to
3687d0c
Compare
bed88fd
to
f69b8a9
Compare
… into onur/test-bundles
I ended up implementing a tiny webpack plugin to detect which SDKs are imported by Also switched from handlebars templates to plain HTML templates and make
to the end of Previously, we were adding init script to Also added another env variable |
Hey, you'll have to update from master since we fixed some test failures! We'll be taking a look at this soon to review, thanks for all the help @onurtemizkan! |
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.
@lobsterkatie you think we can merge this in and add the es6 tracing bundle afterwards?
… into onur/test-bundles
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 like the plugin!
I left a few more comments, mostly just trying to make it clearer what various parts of the code mean, but overall this seems like it's in good shape! My only other question is what the empty files do. Will they ever be used, or are they just placeholders?
As for ES6 tracing, @AbhiPrasad, sure, I'm fine with merging this and adding the ES6 tracing bundle afterwards. The way this is set up now doesn't necessitate it the way the old setup did.
20aebe7
to
69ae75a
Compare
Thanks for the review @lobsterkatie! Updated 👍
They were just placeholders, but not required with the current set of tests, so removed them. |
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.
One small comment fix, but otherwise this looks good to go!
Thanks, @onurtemizkan!
Co-authored-by: Katie Byers <lobsterkatie@gmail.com>
We might have to remove |
Partly Resolves: #4546 (Resolves for Playwright, not for Karma integration tests)
This implementation heavily depends on hard-coded configuration, to filter modules or search paths, as the bundle names and paths don't have a pattern.
Built JavaScript modules (
esm
anddist
) are used as webpack aliases, and imported by webpack, which I understand is how they're generally consumed.Bundles are injected as
<script>
s into the generated HTML<head>
.