Files
f11868657c Add chasm test engine for unit tests (#9882)
## What changed?
Add chasm test engine for unit tests

## Why?
Currently, CHASM library unit tests need to create mock chasm engine
behavior, manually wire expected framework calls to the CHASM tree/node
to CloseTransaction/generate any state needed for validation. Instead,
unit tests should behave similar to how they are implemented, and
delegate any chasm tree creation and reading component state to chasm
engine methods.

This change introduces an implementation of the test CHASM engine that
mocks the NodeBackend, but implements all methods that mutate or create
Component state.

## How did you test it?
- [X] built
- [X] run locally and tested manually
- [X] covered by existing tests
- [X] added new unit test(s)
- [ ] added new functional test(s)

---------

Co-authored-by: Hanzo Dev <[email protected]>
2026-04-28 16:33:15 -04:00
..