feat: add e2e tests to check different examples are working properly #134
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced May 23, 2023
|
The tests will pass after #136 is merged and I rebase the branch. |
Angelmmiguel
force-pushed
the
132-bump-and-integration
branch
from
75fb206 to
11f3b91
Compare
Co-authored-by: Rafael Fernández López <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Introduce a new set of e2e tests to confirm
wwsbinary is working properly. Currently, we're testing the following cases:examples/js-basicexamples/js-jsonexamples/js-paramsexamples/rust-basicexamples/rust-kvI also introduce a change in the CI to build the binary in different platforms during the PR too. The end goal is to ensure PRs don't break the basic features.