docs: how to run unit vs integration tests#37
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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
1 participant
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.
Adds a Running tests section to the README. Documents the distinction that wasn't written down:
deno task test:unit— deterministic, no network/stack.deno task test:integration/deno task test(CI) — deploy + transact on public Stellar testnet (NetworkConfig.TestNet(), no local-stack override). Needs network + Friendbot; the submit step can transiently fail withSTX_002on public-testnet congestion → re-run.Also notes that
test/contracts/*.wasmare the integration artifacts and must be refreshed from the matching soroban-core release. All verified against the actual test config.