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.

Sign up for GitHub

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

getLedgerEntries: Outline building and parsing all sorts of LedgerKeys #1060

Open
wants to merge 8 commits into
base: main
Choose a base branch
from
Open

getLedgerEntries: Outline building and parsing all sorts of LedgerKeys #1060

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
dd00d77
Outline building and parsing all sorts of LedgerKeys/EntryDatas
Shaptic Oct 25, 2024
0fcc954
Fixup all links
Shaptic Oct 25, 2024
969a4ec
More formatting
Shaptic Oct 25, 2024
5c962e4
Run formatter, add links
Shaptic Oct 25, 2024
001206c
Add CLI usage, cleanup
Shaptic Oct 28, 2024
68a7275
Fix lack of closing tag oops
Shaptic Oct 29, 2024
b66d855
Merge branch 'main' into getLedgerEntries-guide
Shaptic Nov 30, 2024
702461e
Fixup sloppy merge
Shaptic Nov 30, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/build/guides/testing/unit-tests.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,6 +25,7 @@ fn test() {
assert_eq!(client.increment(), 3);
}
```

Ref: https://github.com/stellar/soroban-examples/blob/main/increment/src/test.rs

:::tip
Expand All @@ -42,6 +43,7 @@ The Env created at the beginning of the test is not a simulation of the Soroban
It's a simple test, but it's a complete test. There's a full environment setup, used, and torn down in the test, and it happens fast. The Rust test harness runs all the tests for a contract in parallel and each will have its own isolated contract environment.

Most tests, even integration tests and fuzz tests, will look very similar to this unit test. They'll do four things:

1. Create an environment, the `Env`.
2. Register the contract(s) to be tested.
3. Invoke functions using a client.
Expand Down
Loading