marigold-dev / marigold-dev/deku
Generative testing for `consensus.ml`
Nobody has claimed this yet.
- Dominant language
- OCaml
- Stars
- 82
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
Currently we have a handful of tests for `consensus.ml` that run through common scenarios. Since we have no proof of correctness of our consensus protocol, this is not ideal. There are many parts of the consensus state space these tests do not touch, but generative testing could make us much more confident. Currently all work related to this is held on branch [automated-consensus](https://github.com/marigold-dev/deku/tree/automated-consensus)
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 by reading consensus.ml and reviewing the existing tests for common scenarios. Then inspect the automated-consensus branch, where related work is held, to understand the proposed generative testing approach. Done means consensus behavior is exercised across substantially more of the state space through generative tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ocaml
- Domain
- distributed-systems, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100