Skip to content

Define testing strategy #433

@plafer

Description

@plafer

We need to define a testing strategy that will identify what needs to be tested along with how to test it. For example, some questions to answer include

  • Currently MockContext doesn't do proper proofs. Should it? This would involve modifying the store to be a Merkle tree.
  • We want to make sure that we are compatible with gaia. However, integration tests of that sort are very slow, so we probably don't want to run them on every PR. Perhaps before every release is sufficient?
  • What will we be testing with basecoin-rs, that won't be covered with the MockContext-based tests?

Perhaps the outcome of this issue is an ADR which answers all these questions.

Metadata

Metadata

Assignees

Labels

O: exploratoryObjective: aims to investigate new ideasO: testingObjective: aims to improve testing coverage

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions