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

[Q3 TechDebt] Introduce table-driven unit tests for the major usecase components with mocks #275

Open
p0mvn opened this issue Jun 1, 2024 — with Linear · 0 comments
Assignees

Comments

Copy link
Member

p0mvn commented Jun 1, 2024

Currently, we struggle to test edge cases for many higher-level components due to our test suite setup.

The test suite is constructed from mainnet state. As a result, it primarily validates basic happy path invariants. Due to us frequently updating mainnet state and it changing over time, we cannot make detailed assertions as to avoid flakiness.

For testing the edge cases, we should instead mock out the lower-level components and create detailed table-drive unit tests.

Major components to mock out and test:

  • Router usecase
  • Tokens usecase
  • Pools usecase

Note that this is a large effort that is to be converted into a bigger project with sub-tasks once scop is defined

@p0mvn p0mvn self-assigned this Jun 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant