Skip to content

Testing #236

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
1 task done
DanielVoogsgerd opened this issue Mar 19, 2025 · 0 comments
Open
1 task done

Testing #236

DanielVoogsgerd opened this issue Mar 19, 2025 · 0 comments
Labels
C-Maintenance Category: Maintenance E-Medium Effort: Medium P-High Priority: High

Comments

@DanielVoogsgerd
Copy link
Collaborator

DanielVoogsgerd commented Mar 19, 2025

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:

@Lut99 What do you think?

@DanielVoogsgerd DanielVoogsgerd added C-Maintenance Category: Maintenance E-Medium Effort: Medium P-High Priority: High labels Mar 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-Maintenance Category: Maintenance E-Medium Effort: Medium P-High Priority: High
Projects
None yet
Development

No branches or pull requests

1 participant