Skip to content

Commit bc47a68

Browse files
committed
docs: add note about data validation in the testing library
1 parent a95116c commit bc47a68

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

docs/testing-guide/concepts.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -58,3 +58,8 @@ As explained in the [introduction](index.md), `algorand-python-testing` _injects
5858
3. **Mockable**: Not implemented, but can be mocked or patched. For example, `algopy.abi_call` can be mocked to return specific values or behaviours; otherwise, it raises a `NotImplementedError`. This category covers cases where native or emulated implementation in a unit test context is impractical or overly complex.
5959

6060
For a full list of all public `algopy` types and their corresponding implementation category, refer to the [Coverage](../coverage.md) section.
61+
62+
## Data Validation
63+
64+
Algorand Python and the puya compiler have functionality to perform validation of transaction inputs via the `--validate-abi-args`, `--validate-abi-return` CLI arguments, `arc4.abimethod(validate_encoding=...)` decorator and `.validate()` methods.
65+
The Algorand Python Testing library does *NOT* implement this validation behaviour, as you should test invalid inputs using an integrated test against a real Algorand network.

0 commit comments

Comments
 (0)