IntersectMBO / IntersectMBO/ouroboros-consensus
Use more than one TxIn on LedgerDB.StateMachine tests
Open
better-tests
good first issue
UTxO-HD
- Dominant language
- Haskell
- Stars
- 67
- Forks
- 43
- Avg merge
- 5d 13h
- Merged PRs (30d)
- 43
Description
https://github.com/IntersectMBO/ouroboros-consensus/pull/1267#discussion_r1831565096
We should be able to augment the tables with more than one value. This shouldn't really affect the LedgerDB statemachine tested functionality, and it should be fairly easy to add.
Contributor guide
Research direction
Start with the linked pull-request discussion and locate the LedgerDB.StateMachine tests that currently use one TxIn or one table value. Update the test data to include more than one TxIn, then run the relevant state-machine test suite and confirm the tested functionality remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- blockchain, testing
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100