feat: wrappers test cases removed from toolchain#1476
Merged
dOrgJelli merged 39 commits intoorigin-devfrom Feb 18, 2023
Merged
Conversation
1dc48cb to
92b7979
Compare
92b7979 to
c325aa1
Compare
ff28a7a to
5b008af
Compare
krisbitney
suggested changes
Feb 3, 2023
Contributor
krisbitney
left a comment
There was a problem hiding this comment.
This is really awesome. It's going to be a massive boost to testing speed and dev productivity!
Contributor
|
@cbrzn added a fix here: polywrap/wrap-test-harness#39 |
dOrgJelli
approved these changes
Feb 18, 2023
This file contains hidden or 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
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.
closes #1203
depends on: #1482 (& not required: #1480)
this pr has removed the
packages/test-cases/cases/wrappersfolder, and the tests have been migrated to the wasm test harness repository.client tests have also been updated with a new structure to differentiate between different client features (open to any feedback)
development guidelines have also been updated. would appreciate strong feedback there to make sure that the development flow is clear enough when it comes to updating test cases