Add status monitor comprehensive tests
Open
monitor
tests
- Dominant language
- Rust
- Stars
- 104
- Forks
- 138
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 56
Description
Multiple times already we've upgraded protocol versions and later found that the monitor codebase had not been fully adapted to the newest revisions (especially around the transaction flows and MASM code, see [example](https://github.com/0xMiden/node/pull/1826)). It would be great to add some end-to-end monitor tests that run at least against a mocked node, in a way that we can tell if something is wrong before manually running or deploying it. More generally this will also help catch protocol bugs before the client does through its integration tests, because it contains some code that runs basic transactions.
Contributor guide
Assessment
This issue has not been assessed yet.