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

[Indexer] Create integration tests #60

Open
bitbeckers opened this issue May 22, 2024 · 4 comments · Fixed by #79 or #100
Open

[Indexer] Create integration tests #60

bitbeckers opened this issue May 22, 2024 · 4 comments · Fixed by #79 or #100

Comments

@bitbeckers
Copy link
Contributor

We handle a lot of state changes and utilize (semi) complex queries and SQL functions.

To validate our assumptions of the indexing, parsing, storing and availability of events emitted from EVM chains, we should set up integration tests that follow the following pattern:

  • Emit EVM event from the HypercertMinter contract (for example using Anvil)
  • Observe, proces and store event
  • Check DB state

Pay special attention to token transfers, burns, allow list claims.

@bitbeckers
Copy link
Contributor Author

Let's first solve #28, #29, #48, #49

@bitbeckers bitbeckers linked a pull request Jun 5, 2024 that will close this issue
3 tasks
@bitbeckers
Copy link
Contributor Author

Inital integration test created and added to CI stream in #79

@bitbeckers
Copy link
Contributor Author

WIP. Gradually adding integration tests but we need to have a clean, robust solution for resetting the database between tests. Currently the tests are unstable as they sometime manipulate rows from other test cases

@bitbeckers
Copy link
Contributor Author

Memory/timing issue with resetting of DB between test. Leaving out of CI for now but focussing on running tests locally to assert functionality

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