Skip to content
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

Decide a test structure #80

Open
ggonzalez94 opened this issue Mar 20, 2025 · 0 comments
Open

Decide a test structure #80

ggonzalez94 opened this issue Mar 20, 2025 · 0 comments
Labels
type: test Work related to testing

Comments

@ggonzalez94
Copy link
Collaborator

So far we've been fairly loose in how we organize tests, mostly putting them under a single file per contract. We should make a conscious decision that improves organization, but is not overkill(if in doubt we should always defer to the simplest structure).

Test organization

@LeoPatOZ suggested using this state driven approach. Foundry has also some guidance on how to best organize your tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: test Work related to testing
Projects
None yet
Development

No branches or pull requests

1 participant