cowprotocol / cowprotocol/dune-sync
Setup Mock Orderbook DBs for unit testing
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
In #3, we introduce some tests that are actually "integration tests", however, if we want to unit test this without relying on external sources, we should prepare two DBs (barn and orderbook) -- both populated with necessary seed data.
This will be similar to what we have done here:
https://github.com/cowprotocol/solver-rewards/tree/main/tests/db
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the tests introduced in issue #3 and compare the referenced tests/db setup in solver-rewards. Define the barn and orderbook databases with the necessary seed data so the tests can run without external sources, then verify the relevant unit tests use those local databases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- databases, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100