Skip to content

Decide a test structure #80

Open
@ggonzalez94

Description

@ggonzalez94

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    type: testWork related to testing

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions