Since we wrote this post we didn't laze around. Check our latest announcement.
The Arquillian team is proud to announce the 0.0.5 release of the Smart Testing component!
Highlights of this release
In this release we ship several API improvements making integration with 3rd party tools much easier.
Smart Testing API
The Smart Testing tool consists of three parts:
- Maven extension
- Surefire provider integration
Both the Surefire provider integration and the Maven extension are implemented only for the usage in Maven builds. They take care of the integration and invoke Smart Testing API provided by Core.
The Core contains the main logic that is responsible for selecting/ordering and applying corresponding strategies. This logic is exposed by Smart Testing API. If you want to use the logic in your environment or as an integration with some third-party library, you need to have the dependency of Smart Testing Core on your classpath:
plus all dependencies of strategies you want to use for the prioritization:
Having these dependencies specified, you can start using the API. The starting point is
SmartTesting class that provides you a fluent API:
.with(className -> isTest(className), configuration)
The first method
with takes as the first parameter a function that says which class is a test and which not. The second parameter is a configuration that should be used. The configuration file can be loaded using:
The second method
in sets path to the project where the tests will be executed in.
Last method is either
applyOnNames. It invokes the prioritization process and returns a prioritized set of
TestSelection classes. This class contains class name and list of strategies that are applied to it. If you want to get only the names or classes then use the method
With it, you should be able to use the Smart Testing logic in your test suites without being limited to the Maven builds.
We continue improving the tool so watch out for more!
What is Smart Testing?
Smart Testing is a tool that speeds up the test running phase by reordering test execution plan to increase a probability of fail-fast execution and thus give you faster feedback about your project’s health.
Release notes and resolved issues
- Component: Core
Thanks to the following list of contributors:
Matous Jobanek, Bartosz Majsak