test-runner
neil
test-runner | neil | |
---|---|---|
3 | 10 | |
276 | 350 | |
1.1% | 2.0% | |
0.0 | 7.3 | |
2 months ago | 5 days ago | |
Clojure | Clojure | |
Eclipse Public License 2.0 | MIT License |
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
neil
-
Adding Dependencies on Clojure Project the Node Way: A Small Intro to neil CLI
So neil has a bunch of other features like project scaffolding, building, testing, adding license, etc. I really recommend you take a deep look at the repository and learn all the automatized possibilities that neil adds to your project.
-
Leaving Clojure - Feedback for those that care
Check out neil. It makes creating new deps.edn-based projects easy. It also has commands to add deps incrementally to your deps.edn with neil dep add and helps you tag new releases with neil version. You can run it in a REPL if you want, but as you can see below, it runs pretty fast in the shell. $ brew install babashka/brew/neil $ time neil new scratch play Creating project from org.corfield.new/scratch in play neil new scratch play 0.09s user 0.06s system 54% cpu 0.280 total
-
Clojure is a product design tool
Full-featured test runner: https://github.com/lambdaisland/kaocha
If you install neil (https://github.com/babashka/neil), you can do `neil add test` which will automatically set up cognitect-labs/test-runner in your project. Then you can run tests with `neil test` (just an alias, you don't have to use it).
> I used Kit to bootstrap this project and the way it set up tests doesn't even work, but this was what most people recommended to me for starting a Clojure project
I don't really like the approach that Kit takes and prefer something more opinionated like Biff. I'd love to hear your feedback if you do end up trying out Biff.
-
I'm a masochist who want to compile a uberjar without Leiningen
For some common tasks, neil is also an option.
- Clojure Community State
-
Logging in Clojure: jar tidiness
Let's setup a basic project that includes a logger. I think the nicest way to get a new project up is with one of the tools that Borkdude has created, called neil. If you have this installed, just run the following in an empty directory:
-
Clojure needs a Rails, but not for the reason you think
When I see legit anger and frustration in these comments, I also think about the newcomers who might be turned off by the funky syntax just to generate a template. That said, my solution to this wasn't to add another complaint to the thread, but to add the neil new command to solve this problem for tools.deps going forward.
-
Anyone using the Kit framework?
There is also neil which offers some features to make working with deps.edn a little easier.
What are some alternatives?
kaocha - Full featured next gen Clojure test runner
inf-clojure - Basic interaction with a Clojure subprocess
rlwrap - A readline wrapper
deps-new - Create new projects for the Clojure CLI / deps.edn
pomegranate - A sane Clojure API for Maven Artifact Resolver + dynamic runtime modification of the classpath
tools.logging - Clojure logging API
timbre - Pure Clojure/Script logging library
ez-database - Handle all things database in one place
rain - 🌧️ A Clojure/Script library for fast and flexible web apps.
jibbit - Dockerless Clojure Image builds using deps.edn
clj-new - Generate new projects based on clj, Boot, or Leiningen Templates!
bbin - Install any Babashka script or project with one command