Clojure Unit Testing
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- clojure
- Domain
- documentation, testing-qa
Research direction
Review the existing unit-testing content and the linked matcher-combinators and CIDER Tour resources first. Define the advanced features and tools to cover, including comparing data structures, then update the relevant documentation and verify that the new examples and guidance are complete.
Written by the indexing model from the issue text.
Description
Extend existing unit testing content with more advanced features and tools.
Comparing data structures
https://github.com/nubank/matcher-combinators
Resources to review
- Dominant language
- Makefile
- Stars
- 117
- Forks
- 36
- PR merge metrics
- No merged PRs in 30d
Contributor guide
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.
More from practicalli/clojure
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
practicalli/clojure#381 ·
-
Clojure on windows Open
Difficulty 1/5 Under an hour Newbie friendliness 75/100
practicalli/clojure#298 ·
-
video
practicalli/clojure#478 · 1 assignee ·
-
practicalli/clojure#477 · 1 assignee ·
-
practicalli/clojure#476 · 1 assignee ·
All issues in practicalli/clojure
Similar issues
-
sync-en
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
agilepathway/label-checker#640 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
BasedHardware/omi#15662 · 1 comment ·
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100