Skip to content

Write tests for checking that all contracts have code > 0 #9

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.

Sign up for GitHub

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

Jump to bottom
Open
PaulRBerg opened this issue Apr 27, 2025 · 0 comments
Open

Write tests for checking that all contracts have code > 0 #9

PaulRBerg opened this issue Apr 27, 2025 · 0 comments
Assignees
@PaulRBerg
Labels
effort: low Easy or tiny task that takes less than a day. priority: 3 Nice-to-have. Willing to ship without this. type: test Adding, updating, or removing tests. work: clear Sense-categorize-respond. The relationship between cause and effect is clear.

Comments

@PaulRBerg
Copy link
Member

It's a resource-heavy test so it should be only run in CI once per week
@PaulRBerg PaulRBerg added effort: low Easy or tiny task that takes less than a day. priority: 3 Nice-to-have. Willing to ship without this. type: test Adding, updating, or removing tests. work: clear Sense-categorize-respond. The relationship between cause and effect is clear. labels Apr 27, 2025
@PaulRBerg PaulRBerg self-assigned this Apr 27, 2025
@PaulRBerg PaulRBerg transferred this issue from sablier-labs/deployments Jun 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@PaulRBerg PaulRBerg

Labels
effort: low Easy or tiny task that takes less than a day. priority: 3 Nice-to-have. Willing to ship without this. type: test Adding, updating, or removing tests. work: clear Sense-categorize-respond. The relationship between cause and effect is clear.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@PaulRBerg