Skip to main content
Smart contracts need both unit and integration tests:
  1. Unit tests exercise methods individually. They are written in Rust alongside the contract and run locally.
  2. Integration tests deploy the compiled contract to a local Sandbox or testnet and exercise it through transactions.
Use unit tests for contract logic and state changes. Use integration tests for behavior that depends on the runtime, including cross-contract calls, gas, attached deposits, and multiple accounts. We recommend using both types of tests and testing on testnet before deploying a contract to mainnet.
Unit tests allow you to test the contract methods individually. They are suitable to check the storage is updated correctly, and that methods return their expected values. They are written in Rust alongside the contract’s code and execute locally. To run the unit tests, simply navigate to the contract’s folder and run cargo test:
cargo test runs both unit and integration tests present in the project.

​
Snippet I: Testing a Counter

The tests in the Counter Example rely on basic functions to check that the increment, decrement, and reset methods work properly.

​
Snippet II: Modifying the Context

While doing unit testing you can modify the Environment variables through the VMContextBuilder. This will enable you to, for example, simulate calls from different users, with specific attached deposit and GAS. Here we present a snippet on how we test the donate method from our Donation Example by manipulating the predecessor and attached_deposit.

​
⚠️ Limitations

Unit tests are useful to check for code integrity, and detect basic errors on isolated methods. However, since unit tests do not run on a blockchain, there are many things which they cannot detect. Unit tests are not suitable for: For all these cases it is necessary to complement unit tests with integration tests.