You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want to build a more robust test suite for the state override system on compare function such that in the future if upstream changes logic related to this we can make sure we catch any new bugs.
Currently we have 83% coverage of compare function using mostly unit test + a single end to end test, we should try to build more variations of the end-to-end test, also making sure we test both historical and current-state calls.
Build end-to-end tests for all override cases (try to hit all panics in compare function), and query reth state using historical and current-state rpc calls.
Tasks
###TODO
The text was updated successfully, but these errors were encountered:
Overview
We want to build a more robust test suite for the state override system on compare function such that in the future if upstream changes logic related to this we can make sure we catch any new bugs.
Currently we have 83% coverage of compare function using mostly unit test + a single end to end test, we should try to build more variations of the end-to-end test, also making sure we test both historical and current-state calls.
Links
Compare function:
telos-reth/crates/telos/rpc-engine-api/src/compare.rs
Line 113 in c1640ac
Current end to end test:
telos-reth/crates/telos/node/tests/state_bypass.rs
Line 89 in c1640ac
Acceptance Criteria
Build end-to-end tests for all override cases (try to hit all panics in compare function), and query reth state using historical and current-state rpc calls.
Tasks
###TODO
The text was updated successfully, but these errors were encountered: