practicalli / practicalli/clojure
clojure.test
Open
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 117
- Forks
- 36
- PR merge metrics
- No merged PRs in 30d
Description
- development tests vs api namespace tests
- using deftest- to isolate development tests (testing those functions that are low level algoritym testing functions and will become private functions, i.e. defn- functions
See WeFarm interview code for an example
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.
Research direction
Review the distinction between development tests and API namespace tests described in the issue, then inspect the referenced WeFarm interview code for the proposed deftest- pattern. Determine which existing tests and private-function cases are in scope; done should establish a clear, consistent separation and verify the affected test suite.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100