EPIC: Implement and integrate CometMock #932
Labels
admin: epic
An EPIC -- meta issue used to track a body of work
S: Productivity
Productivity: Developer tooling, infrastructure improvements enabling future growth
scope: testing
Code review, testing, making sure the code is following the specification.
Problem
We would like to mock out CometBFT in our end-to-end tests, since we
want to test the underlying application, but we do not care about actually running
a replicated state machine resistant to byzantine faults - just running a state machine is enough for testing.
Mocking out the consensus layer means we can skip
waiting for the network communication in the potentially multiple rounds
needed for CometBFT to come to consensus.
Thus, this can make the existing tests which are running full nodes faster.
Looking further, it can also enable writing tests with new functionality,
as CometMock can mock arbitrary timestamps coming from Comet,
and we can finely control which validators sign and don't sign which blocks.
Closing criteria
CometMock has been implemented in a proper repository.
It is integrated in our CI pipeline(s) and covers all common usecases
in a way that is delightful to use.
Problem details
Task list
Must have
Nice to have
The text was updated successfully, but these errors were encountered: