test-runner
clj-new
test-runner | clj-new | |
---|---|---|
3 | 5 | |
276 | 486 | |
1.1% | - | |
0.0 | 4.4 | |
2 months ago | about 2 months ago | |
Clojure | Clojure | |
Eclipse Public License 2.0 | Eclipse Public License 1.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
test-runner
-
Clojure is a product design tool
> I had to Grok Integrant again because I wouldn't understand my project otherwise.
You can use plain functions and `reduce` for system composition if you want. Take a look at how Biff does it: https://biffweb.com/p/thinking-about-system-composition/
DI should be used sparingly for the top-level, stateful pieces of your system. If you can't understand your program without it, is this a problem with Clojure itself or the design of the program?
> And when it comes to best practices around unit testing, it's another one of those things where no one in the community seems to be sharing much about it.
The `clojure.test` API has stayed the same for the last decade and that's what you'll see in most projects. Is the concern about how to run tests? Both of the following libraries work well:
Minimal test runner: https://github.com/cognitect-labs/test-runner
-
Build and run Clojure projects. CLI, tools.deps and deps.edn guide
:aliases {:test {:extra-paths ["test"] :extra-deps {io.github.cognitect-labs/test-runner {:git/url "https://github.com/cognitect-labs/test-runner.git" :git/sha "8c3f22363d63715de4087b038d79ae0de36a3263"}} :main-opts ["-m" "cognitect.test-runner"] :exec-fn cognitect.test-runner.api/test}}
-
How can I test my clojure code without re-jacking in every time?
Cognitect's test-runner is probably the most commonly used approach with deps.edn and the CLI: https://github.com/cognitect-labs/test-runner
clj-new
-
Build and run Clojure projects. CLI, tools.deps and deps.edn guide
clj-new library allows you to generate new projects from templates. In contrast to the previous example, this time you suggested adding a new alias globally in ~/.clojure/deps.edn:
-
Creating and publishing Clojure libraries
These steps aren't unique for the test-lib and you'll need to repeat them again when creating another libraries. Fortunately, there is a project called clj-new that will save you from doing similar work again and again.
-
Clojure Command Line Application Tutorial - On the Code Again
My new favourite thing is clj-new. Quoth the readme:
-
Building A Fast Command Line App With Clojure
I use Sean Corfield's clj-new project to initialize new Clojure projects. Install it for your environment according the instructions in his README, then run clj -X:new :template app :name kiramclean/test-cli to generate a new Clojure project (but replace kiramclean/test-cli with /).
-
Learning Clojure Part 1: Preparing local setup
FYI, https://github.com/seancorfield/clj-new
What are some alternatives?
kaocha - Full featured next gen Clojure test runner
babashka-tools - A collection of Babashka tools
rlwrap - A readline wrapper
graalvm-clojure - This project contains a set of "hello world" projects to verify which Clojure libraries do actually compile and produce native images under GraalVM.
pomegranate - A sane Clojure API for Maven Artifact Resolver + dynamic runtime modification of the classpath
timbre - Pure Clojure/Script logging library
rain - 🌧️ A Clojure/Script library for fast and flexible web apps.
clojure-test-lib
imba - 🐤 The friendly full-stack language
deps-deploy - deploy your stuff