Our artifacts (test behaviour trees) only exist in json serialized format
Expected Behavior
We should add a little script to regenerate these, if our dataclass schema ever changes. It may also be worthwhile adding in-python-memory fixtures for these behaviour trees, in the interest of not going through serialization/deserialization each time.
Context / environment
Discussion from today's BEAM tagup
Steps to Reproduce (for bugs)
N/A
Suggested Solution
Fixtures in conftest.
possibly a make artifacts routine
Current Behavior
Our artifacts (test behaviour trees) only exist in json serialized format
Expected Behavior
We should add a little script to regenerate these, if our dataclass schema ever changes. It may also be worthwhile adding in-python-memory fixtures for these behaviour trees, in the interest of not going through serialization/deserialization each time.
Context / environment
Discussion from today's BEAM tagup
Steps to Reproduce (for bugs)
N/A
Suggested Solution
Fixtures in conftest. possibly a
make artifacts
routine