forked from onnovalkering/brane
-
Notifications
You must be signed in to change notification settings - Fork 10
Closed
Labels
C-MaintenanceCategory: MaintenanceCategory: MaintenanceE-MediumEffort: MediumEffort: MediumP-HighPriority: HighPriority: High
Description
Currently, Brane has painfully low test coverage. This introduces quite a bit of risk when working on establish parts of Brane.
We should really find some sort of testing strategy for Brane so that we can be confident that the alterations we are making are correct.
As a stopgap measure, I suggest we start implementing Cargo insta in some crates so that we at least know when stuff changes
Testing parts that interface with the machine would require some nasty mocking right now so that is not even the focus in my opinion, but for crates like brane-dsl there is no reason not to test I think
To Do:
- Implement snapshot regression testing Snapshot regression testing #245
@Lut99 What do you think?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
C-MaintenanceCategory: MaintenanceCategory: MaintenanceE-MediumEffort: MediumEffort: MediumP-HighPriority: HighPriority: High