OpenZeppelin / OpenZeppelin/compact-tools
Add unit tests for the simulator
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 5
- Avg merge
- 15h 28m
- Merged PRs (30d)
- 31
Description
Related:
Originally posted by @andrew-fleming in https://github.com/OpenZeppelin/compact-tools/pull/26#pullrequestreview-3536993401
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 simulator implementation and the repository's existing unit-test setup. Define the simulator behaviors that need coverage, add tests for them, and confirm the test suite passes; the issue does not identify specific files or expected cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100