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

Allow integration tests to run against built code #4546

Closed
lobsterkatie opened this issue Feb 11, 2022 · 0 comments · Fixed by #4551
Closed

Allow integration tests to run against built code #4546

lobsterkatie opened this issue Feb 11, 2022 · 0 comments · Fixed by #4551
Assignees

Comments

@lobsterkatie
Copy link
Member

As part of our work on v7, we're revamping our bundling process, both to standardize it and speed it up, and to allow us to create more variations of out our packages (with and without debug statements, ES5 and ES6, cjs and esm, bundled and via npm, minified, etc).

As a way to verify that all of our various builds work correctly (and as a way to identify errors which might not show up in all variations), we want to adapt our integration tests to run against built files as well as source files. (Right now, our TS source is compiled on the fly each time we run tests.)

To be more specific, the goal is to have a core set of integration tests, runnable in two frameworks: one which uses a pre-built bundle, which can be passed in, and one which builds with webpack or rollup, using different flavors of our npm package.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants