practicalli / practicalli/clojure
Clojure Spec Generative testing and Generators
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 117
- Forks
- 36
- PR merge metrics
- No merged PRs in 30d
Description
https://the-frey.github.io/2018/03/01/experimenting-with-spec-generators
https://gist.github.com/ghoseb/9f81ca592a56c23a4f7564e813d23ea5
https://archive.ochronus.com/generative-testing-in-clojure/
https://purelyfunctional.tv/issues/purelyfunctional-tv-newsletter-215-clojure-and-generative-testing/
https://clojure.github.io/test.generative/
https://conan.is/blogging/clojure-spec-tips.html
https://cognitect.com/blog/blog/2016/10/5/interactive-development-with-clojurespec
https://purelyfunctional.tv/mini-guide/clojure-spec-vs-schema/
https://blog.jeaye.com/2017/05/31/clojure-spec/
https://blog.taylorwood.io/2018/10/15/clojure-spec-faq.html
https://www.bradcypert.com/an-informal-guide-to-clojure-spec/
https://clojure.org/guides/spec#_using_sand_generators
https://insideclojure.org/2019/01/18/journal/
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
The issue contains links about Clojure Spec, generative testing, and generators but names no repository files, tests, or entry point. Review the linked material and the repository structure first, then clarify the intended documentation location, scope, and acceptance criteria before starting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- testing
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100