Jumi test runner for all JVM languages
Jumi is a test runner for all programming languages on the JVM. It will natively support running tests in parallel, class loader caching, test order priorization and other measures to run tests faster. It covers the full stack for running tests (the responsibilities which used to be spread over build tools, IDEs and test runners) in order to overcome limitations of previously existing tools, specifically JUnit’s test runner, to better support all testing frameworks on the JVM.
Jumi is not only open source, but also open development. The process of how Jumi is developed is being screencasted at http://www.orfjackal.net/lets-code The long-term roadmap is in ROADMAP.txt and the short-term task list is in TODO.txt.
- Mailing list: https://groups.google.com/d/forum/jumi-test-runner
- Downloads: fi.jumi in Maven Central (Release Notes)
- Issue tracker: https://github.com/luontola/jumi/issues
- Source code:
- License: Apache License 2.0
- Developer: Esko Luontola (@orfjackal)
All the following features have been implemented and more are on the way.
Runs Tests in Parallel - Faster feedback by distributing the load over all your CPU cores. A testing framework that runs on Jumi can easily run even each test method in its own thread.
Accurate Test Output - When a test prints something to System.out/err, Jumi will show the output exactly inside that test in the results (unlike JUnit and many IDEs). Also when multiple tests are run in parallel, the output from each of them is isolated from each other.
Backward Compatible with JUnit - Runs your existing JUnit tests and also tests for the numerous other testing frameworks that support the JUnit test runner.
Expressive Execution Model - Supports better all testing frameworks. Unlike with JUnit, with Jumi it’s not necessary for a testing framework to know what tests exist before it executes the tests. Also tests may consist of multiple steps (“nested tests”), instead of just a flat JUnit-like organization.
Continue to the documentation to find out how to run your tests on Jumi.
Faster JUnit Tests with Jumi Test Runner and Class Loader Caching (2013-02-12)
Benchmarks of Jumi’s performance, especially after some optimizations have been implemented.
Announcing the First Release of the Jumi Test Runner for the JVM (2012-09-19)
Motivation and benefits of the Jumi test runner, and how testing framework, build tool and IDE developers can get started on implementing Jumi support.
What’s compatible with Jumi?
Jumi has just recently been released and it’s missing some important features, but it’s already at a stage where early adopters can start using it and testing framework developers can implement support for it. Here is a list of frameworks and tools that already have Jumi support:
- JUnit and any testing frameworks that run on JUnit, through Jumi’s JUnit backward compatibility (parallelism is limited to test class level)
- sbt build tool, through the sbt-jumi plugin
- Specsy, a testing framework for Scala, Groovy, Java and easily any other JVM-based language
Reliability - A test runner is the most important tool of a software developer, second only to a compiler. Thus it should have zero bugs. In the unlikely case that you find a bug from Jumi, you will be richly rewarded.
Speed - When tests are run after each change to a line of code, many times per minute, speed matters. Jumi will take any measures necessary (which don’t compromise reliability) to give faster feedback.
Usability - Oftentimes, high usability in the user interface affects also design decisions at the system’s lowest implementation levels. By covering the whole stack of running tests, from UI to class loading, Jumi will be able to maximize its usability.
Compatibility - Jumi attempts to become the next de facto test runner on the JVM. Thus it needs to integrate well with all tools and testing frameworks. We take backward compatibility seriously and will run any consumer contract tests from framework and tool developers. Any incompatible changes will be done carefully over a transition period.
Simplicity - The system should be as simple as possible, but no simpler. Adding new features should be done with great criticism and unnecessary features should be removed. To achieve high reliability, simplicity in implementation is critical.