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

Spike: Implement CometMock prototype in Go #917

Closed
Tracked by #2406
p-offtermatt opened this issue May 5, 2023 · 1 comment · Fixed by informalsystems/CometMock#1
Closed
Tracked by #2406

Spike: Implement CometMock prototype in Go #917

p-offtermatt opened this issue May 5, 2023 · 1 comment · Fixed by informalsystems/CometMock#1
Assignees
Labels
scope: testing Code review, testing, making sure the code is following the specification.

Comments

@p-offtermatt
Copy link
Contributor

Problem

A decision was made to use Tendermock for our e2e tests, but to reimplement it in Go.
I propose to also change the name to CometMock, to make sure there are no concerns regarding the Tendermint brand.
For this issue, a very small prototype implementation is planned to allow better splitting the work on doing the
full reimplementation.

The goal is to allow a simple stress test: connecting to N validators and processing M token transfers.
This will let us know if the implementation in Go still has performance bottlenecks.

Desired features thus are:

  • Connect to multiple applications via ABCI
  • Provide minimal RPC hooks to allow broadcasting token transfers

Closing criteria

The desired features have been implemented in a prototype implementation in Go.

@p-offtermatt p-offtermatt added the scope: testing Code review, testing, making sure the code is following the specification. label May 5, 2023
@p-offtermatt p-offtermatt self-assigned this May 5, 2023
@p-offtermatt
Copy link
Contributor Author

CometMock implementation, for now, lives in its own repo with a PR for the content of this issue informalsystems/CometMock#1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scope: testing Code review, testing, making sure the code is following the specification.
Projects
Status: ✅ Done
Development

Successfully merging a pull request may close this issue.

1 participant