funboy
Hi,
I built a small utility tool mainly for running test partitions, generating coverage reports, and rerunning failed tests across all partitions.
I managed to speed up test suite from 20min down to 6min 
Why a binary instead of a Mix task?
When you run a Mix task, you often have to wait for the whole project to compile first, especially in large projects. Sometimes you’re waiting longer for compilation than for the task itself.
check avoids that completely. It’s an escript binary that directly runs the commands it needs.
The main feature is test partitioning.
Instead of running all tests one after another, check splits them into multiple partitions and runs them in parallel.
check # runs tests in 3 partitions by default
check --partitions 6 # use more partitions on bigger machines
Coverage is merged automatically after all partitions finish.
You can also run only tests affected by your changes:
check --only modified_tests
This is quite granular. If you change a single test, only that test is run. If you change a describe setup, only tests in that block are run.
You can find a guide on how to set up your project to run tests using partitions here 
Maybe some of you will find it useful too 
Where Next?
Trending in Dev Env & Tools
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Master modern tools, write cleaner code, and tackle real-world challenges with Manning books, videos, and courses. Start building today.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #ai
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Bringing learning, work and compliance together since 1987.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 4- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
funboy
Hi,
I’ve enhanced the check tool with dense coverage.
Problem:
Coverage output is too noisy. On large projects, it prints percentages for thousands of modules, even if I only changed a handful of files. The information I care about gets lost in the noise.
Solution:
al_check now diffs against the base branch and reports coverage only for new and modified files, grouped by change type with per-group average coverage.
Try it
more details → Coverage you’ll actually read
funboy
btw, is anyone here using the
checktool?kevinschweikert
I am using GitHub - karolsluszniak/ex_check: One task to efficiently run all code analysis & testing tools in an Elixir project. Born out of 💜 to Elixir and pragmatism. · GitHub currently
funboy
Yep,
ex_checkis great! I was just missing a few features, like running tests in partitions and using a prebuilt binary to avoid compiling the project before the first check starts. That’s why I ended up building my own tool