marigold-dev / marigold-dev/deku
test tezos integrations commit_state_hash
Open
Nobody has claimed this yet.
backlog
- Dominant language
- OCaml
- Stars
- 82
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
@callistonianembrace suggested at https://github.com/marigold-dev/sidechain/pull/100#discussion_r680436910 that we could run a tezos node in mockup mode for testing on the CI.
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 locating the integration tests for commit_state_hash and the repository's CI configuration, then determine how a Tezos node in mockup mode can be run there. Done means the integration test runs against that node in CI and covers commit_state_hash.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100