Arquillian Blog

Since we wrote this post we didn't laze around. Check our latest announcement.

The Arquillian team is proud to announce the 0.0.8 release of the Smart Testing component!

Test method selection

In all previous versions of the Smart Testing tool, by using the selecting mode, it was possible to select the whole test classes only.

In this release, we have introduced a possibility of selecting on the test method level. This new feature can be applied with two strategies: failed and categorized.
In case of the failed strategy – if you have a class with 10 test methods and only one of them fails, then in the next build Smart Testing selects and executes only the one test method that failed instead of running the whole test class. This should minimize the test suite execution and make the feedback loop much faster.
In case of the categorized strategy, it means that Smart Testing now resolves the annotations specified on the test methods and is able to select only test methods that belong to required categories.
By default, it is enabled for both strategies, but you can disable it either in the configuration file or using system properties -Dsmart.testing.failed.methods=false or -Dsmart.testing.categorized.methods=false respectively.

Test method selection can be used only with the selecting mode.

What’s next

In the next release, we are going to provide you a support for excluding categories in the categorized strategy. Stay tuned!

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 details

Component	Smart Testing
Version	0.0.8 view tag
Release date	2018-02-13
Released by	Matous Jobanek
Compiled against	Arquillian Spacelift – 1.0.2 ShrinkWrap Resolver – 3.1.2

Published artifacts org.arquillian.smart.testing

• org.arquillian.smart.testing » core jar javadoc pom
• org.arquillian.smart.testing » api jar javadoc pom
• org.arquillian.smart.testing » surefire-provider jar javadoc pom
• org.arquillian.smart.testing » junit-test-result-parser jar javadoc pom
• org.arquillian.smart.testing » strategy-affected jar javadoc pom
• org.arquillian.smart.testing » strategy-changed jar javadoc pom
• org.arquillian.smart.testing » strategy-failed jar javadoc pom
• org.arquillian.smart.testing » strategy-categorized jar javadoc pom
• org.arquillian.smart.testing » maven-lifecycle-extension jar javadoc pom
• org.arquillian.smart.testing » git-rules jar javadoc pom
• org.arquillian.smart.testing » smart-testing-test-bed jar javadoc pom
• org.arquillian.smart.testing » known-surefire-providers jar javadoc pom

Release notes and resolved issues 7

Component: Core

• #314 Test method selection make sense only when selecting mode is used
• #299 Investigate the possibility of using the tool on test method level basis

Component: Selection

• #306 Failed - support execution of the specific test methods that failed
• #305 Support selection of test methods
• #304 Categorized - support categorization for test methods

Component: Test Bed

• #294 Change test-bed core to use latest Embedded Maven features
• #293 Occasional IllegalStateException when running test-bed functional tests

Thanks to the following list of contributors: Matous Jobanek, Dipak Pawar