Skip to content

Explain or improve how to test collections #20905

Open

Description

Multiple users complained that with the (partial) migration to collections in v0.50 (Hub, Injective), testing modules that use collections became harder.

The solution we provided was to create keeper wrappers and use that in the modules. That is acceptable for v0.50, as not all modules have migrated to collections. However, with v0.52 coming, the deleted API surface has increased significantly.
However, it appears that we ourselves didn't encounter the problem as we kept the API we needed directly in the modules (check bank API for instance vs staking).

We should possibly go through each module that migrated to collections and bring back so API for compatibility, or provide an example on how to write tests and use ourselves that method (otherwise it's unfair to break people but not ourselves).

cc @MSalopek

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    C:collectionsT: Dev UXUX for SDK developers (i.e. how to call our code)UX for SDK developers (i.e. how to call our code)T: TestsT:DocsChanges and features related to documentation.Changes and features related to documentation.

    Type

    No type

    Projects

    • Status

      📋 Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions