-
Notifications
You must be signed in to change notification settings - Fork 5
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
Introduce a testing framework for Wasmer Pack #112
Conversation
ec7c9e1
to
583a6eb
Compare
⏱ Workflow Timer ⏱ Make sure you keep an eye on build times! One of this project's goals is to keep CI runs under 5 minutes so developers can maintain fast edit-compile-test cycles.
🤖 Beep. Boop. I'm a bot. If you find any issues, please report them to https://github.com/Michael-F-Bryan/workflow-timer. |
After talking with @dynamite-bud, we're thinking we might merge this PR as-is and follow up with PRs that implement JavaScript testing and refactor the workflow. |
Description
This PR introduces a
wasmer-pack-testing
crate that people can use when writing integration tests for bindings generated bywasmer-pack
. At the moment, support for Python is implemented, and we'll implement the JavaScript tests in a future PR.CC #87.
Context
At the moment, creating and running integration tests for Wasmer Pack is quite cumbersome because it relies on several external tools (
cargo wapm
,yarn
,python
,pip
, etc.).Wasmer Pack also has integration tests which run the real
wasmer/wasmer-pack
andwasmer/wabt
packages. This is great because we're testing real-world packages, but it's also unhelpful because those integration tests are testing real-world packages which don't necessarily include every little feature of WAI/Wasmer Pack that we'd like to test.Checklist