substreams-testing

Substreams unit tests validate parsing and balance updates by applying reusable test design templates with synthetic fixtures. You build a Rust test scaffold, construct mock data covering edge cases, and execute assertions against module outputs to verify parsing reliability.

Substreams reorg handling is tested through integration tests with real or synthetic fixtures simulating chain reorganizations. You orchestrate mock block data covering reorg scenarios, then validate modules correctly process block reversions and update outputs without corruption or data loss.

Substreams performance benchmarks apply load testing and parallel execution validation with realistic blocks. You use performance testing patterns to measure module throughput under load, identifying bottlenecks in parsing, data transformation, and output generation across pipeline stages.

Yes, Substreams integration testing supports real and synthetic fixtures for mock data orchestration. You build test data covering edge cases, enabling reliable verification of module interactions, balance updates, and parsing accuracy without requiring live blockchain data access.

Substreams test failures in balance updates typically arise from inadequate fixture coverage for edge cases. You need test data orchestration with synthetic mocks replicating real-world scenarios, ensuring modules handle zero-value transfers, dust amounts, and concurrent updates reliably.

Yes, Substreams test scaffolds require Rust because modules are written in Rust and compiled to WebAssembly. You build unit and integration tests within the Rust ecosystem, using test builders and fixtures to validate parsing, balance updates, and reorg handling workflows.