Arquillian Blog

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

The Arquillian team is proud to announce the 2.4.3 release of the Arquillian Drone Extension component!

What is Arquillian?

Arquillian is open source software that empowers you to test JVM-based applications more effectively. Created to defend the software galaxy from bugs, Arquillian brings your test to the runtime so you can focus on testing your application's behavior rather than managing the runtime. Using Arquillian, you can develop a comprehensive suite of tests from the convenience of your IDE and run them in any IDE, build tool or continuous integration environment.

Release details

Component	Arquillian Drone Extension
Version	2.4.3 view tag
Release date	2017-11-03
Released by	Matous Jobanek
Compiled against	Arquillian Core – 1.1.13.Final Arquillian Spacelift – 1.0.2 Selenium – 3.7.0

Published artifacts org.jboss.arquillian.extension

• org.jboss.arquillian.extension » arquillian-drone-bom pom
• org.jboss.arquillian.extension » arquillian-drone-webdriver-depchain pom
• org.jboss.arquillian.extension » arquillian-drone-api jar javadoc pom
• org.jboss.arquillian.extension » arquillian-drone-spi jar javadoc pom
• org.jboss.arquillian.extension » arquillian-drone-configuration jar javadoc pom
• org.jboss.arquillian.extension » arquillian-drone-impl jar javadoc pom
• org.jboss.arquillian.extension » arquillian-drone-webdriver jar javadoc pom
• org.jboss.arquillian.extension » arquillian-drone-saucelabs-extension jar javadoc pom
• org.jboss.arquillian.extension » arquillian-drone-browserstack-extension jar javadoc pom
• org.jboss.arquillian.extension » arquillian-drone-appium-extension jar javadoc pom

Release notes and resolved issues 1

Component Upgrade

• ARQ-2147 - Upgrade to Selenium 3.7.0

Thanks to the following list of contributors: Matous Jobanek

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

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

Highlights of this release

After one month of hard work we bring you the third release of Smart Testing tool!
Apart from several small improvements, component upgrades, and bug fixes, this release contains one killer feature and one convenient feature that will make your life easier.

Configuration file

In previous releases, there was only one way of configuring the tool – through system properties. As we started introducing more options, we quickly realized that this is definitely not the most pleasant way of setting up the tool. From now on you can also use YAML configuration file.
The name of the file should be either smart-testing.yml or smart-testing.yaml and should be located in the root of the directory the build is executed from. Here’s an example:

strategies: new, changed, affected
mode: ordering
applyTo: surefire
debug: true
report:
    enable: true
scm:
    range:
      head: HEAD
      tail: HEAD~2

We are keeping the names as it is done for the system properties, just without the prefix smart.testing. This means that when you want to activate a set of strategies on a command line, then you should use the system property smart.testing.strategies. As you can see in the example, in the configuration file it is just strategies. Analogically for other parameters.

The system properties are not going away. When both system properties and the configuration file are used, the values defined by system properties have the precedence. This can be helpful when your Smart Testing setup is shared in your scm but you want to have special settings for different stages of CI pipeline.

Autocorrection of mistyped strategy names

It might happen that you misspell a strategy when executing the build. For example:

$ mvn clean verify -Dsmart.testing=new,change,afected

It can take you a second or two to notice why this will lead to a failing build with some hints in the error message. To save time (and headaches) you can activate the autocorrection feature by setting smart.testing.autocorrect=true on a command line or just autocorrect: true in the config file. If it is set, the mistyped name is automatically corrected and the affected strategy is used. In this case afected should be affected.

What’s next

We are working hard on the next release which will bring JUnit 5 support, a possibility of configuring custom strategies and many more cool features! 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.3 view tag
Release date	2017-10-23
Released by	Matous Jobanek
Compiled against	Arquillian Spacelift – 1.0.2 ShrinkWrap Resolver – 3.0.0-beta-2

Published artifacts org.arquillian.smart.testing

• org.arquillian.smart.testing » core 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 » 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

Release notes and resolved issues 16

Component: Core

• #231 Strategies should use Configuration provided by SmartTesting API
• #228 ChangeResolver and ChangeStorage should use correct project directory path
• #201 The Surefire logger instance should be retieved using reflection
• #133 Align ST Logger also with Maven logging format
• #113 Introduce YAML configuration file

Component: Maven

• #230 Use LocalStorage api to write modified pom.xml
• #219 Should delete target directory completely for mvn clean if configuration file has debug true enabled
• #218 NoSuchMethodError `ProviderParameters.getConsoleLogger()` with surefire 2.20.1
• #217 Smart Testing should run with project which has SCM setup, but doesn't have single commit
• #196 The installation script should check if there is a pom.xml
• #175 Shaded extension doesn't work with older versions of Maven
• #173 Enable autocorrect for mistyped strategy
• #144 Should produce reports when debug mode enabled

Component: Test Bed

• #226 SmartTestingSoftAssertions is not working as per expectation
• #140 Introduce custom assertj assertions

Component: Selection

• #96 Ordering mode not practical now

Thanks to the following list of contributors: Matous Jobanek, Dipak Pawar, Hemani, Bartosz Majsak, Alex Soto

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

The Arquillian team is proud to announce the 1.9.1 release of the Arquillian Cube Extension component!

What is Arquillian Cube Extension?

With Arquillian Cube you can control the lifecycle of Docker images as part of the test lifecyle, either automatically or manually. This gives you the chance to scale up from a integration/functional test level all the way up to the system test level.

Release details

Component	Arquillian Cube Extension
Version	1.9.1 view tag
Release date	2017-10-11
Released by	Alien Ike
Compiled against	Arquillian Core – 1.1.13.Final Arquillian Spacelift – 1.0.1 ShrinkWrap – 1.2.6 ShrinkWrap Resolver – 3.0.0-alpha-4

Published artifacts org.arquillian.cube

• org.arquillian.cube » arquillian-cube-api jar javadoc pom
• org.arquillian.cube » arquillian-cube-spi jar javadoc pom
• org.arquillian.cube » arquillian-cube-core jar javadoc pom
• org.arquillian.cube » arquillian-cube-containerless jar javadoc pom
• org.arquillian.cube » assertj-docker-java jar javadoc pom
• org.arquillian.cube » arquillian-cube-docker jar javadoc pom
• org.arquillian.cube » arquillian-cube-docker-drone jar javadoc pom
• org.arquillian.cube » arquillian-cube-docker-reporter jar javadoc pom
• org.arquillian.cube » arquillian-cube-docker-restassured jar javadoc pom
• org.arquillian.cube » arquillian-cube-docker-junit-rule jar javadoc pom
• org.arquillian.cube » arquillian-cube-openshift jar javadoc pom
• org.arquillian.cube » arquillian-cube-kubernetes-fabric8 jar javadoc pom
• org.arquillian.cube » arquillian-cube-kubernetes jar javadoc pom
• org.arquillian.cube » arquillian-cube-kubernetes-reporter jar javadoc pom
• org.arquillian.cube » arquillian-cube-requirement jar javadoc pom
• org.arquillian.cube » arquillian-cube-bom pom

Release notes and resolved issues 3

Other

• #816 properties in arquillian.xml take precedence over system properties
• #815 Make tests work on Openshift and Kubernetes without changes
• #804 Cube Drone with recordingMode NONE throws java.lang.IllegalArgumentException

Thanks to the following list of contributors: Jonh Wendell, Arquillian, Nicola Ferraro, Ladislav Thon

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

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

Highlights of this release

After a week since our very first release we have a brand new one! This time with several improvements and bug fixes, namely:

• simplified installation process
• hinting available strategies when misspelled in the configuration
• ability to narrow search for affected tests
• improved documentation

Simplified getting started

Even though installation process is very simple, we are huge fans of automation. So we created one liner which will take care of adding Smart Testing to your project.

Simply execute following snippet and you are ready to go.

$ curl -sSL https://git.io/v5jy6 | bash

Hinting available strategies

It might happen that you misspell a strategy when executing the build. For example:

$ mvn clean verify -Dsmart.testing=new,change,afected

This will lead to a failing build, but instead of leaving you with not just an exception thrown at your face and documentation to dig into, we are now hinting to matching strategies. With 0.0.2 you will see instead:

Unable to find strategy [afected]. Did you mean [affected]?
Unable to find strategy [change]. Did you mean [changed]?

Affected tests

Affected is one of the strategies in Smart Testing which let you find tests related to business code you have just changed. By default we transitively look up all related tests, but this can lead to a lot of tests being prioritized. Especially if you have deep hierarchies in your project.

To find only immediate related tests we have introduced a configuration option smart.testing.affected.transitivity which you can set to false.

Asciidoctor Extensions

We’ve created two Asciidoctor extensions to make documentation more resilient to changes and also to simplify the copy-paste process from documentation to your terminal.

First extension allows you to reference constants in the documentation from source code. For example to get the value represented by SMART_TESTING_MODE constant, add const macro in your document:

const:core/src/main/java/org/arquillian/smart/testing/Configuration.java[name="SMART_TESTING_MODE"]

Second extension brings copy-to-clipboard button in the rendered docs. To add it, simply use copyToClipboard macro:

[[singleTest]]
`mvn test -Dtest=SampleTest`  copyToClipboard:singleTest[]

What’s next

We are working hard on the next release which will bring simplified configuration and many more cool features! 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.2 view tag
Release date	2017-09-26
Released by	Bartosz Majsak
Compiled against	Arquillian Spacelift – 1.0.2 ShrinkWrap Resolver – 3.0.0-alpha-4

Published artifacts org.arquillian.smart.testing

• org.arquillian.smart.testing » core 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 » 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

Release notes and resolved issues 21

Component: Test Bed

• #193 Checkout all branches when importing a repository
• #191 Ignore .git suffix in the git-server

Component: Core

• #192 Not so helpful exceptions thrown when invalid commits are specified
• #185 Full support for OSX in install.sh
• #184 Basic support for OSX in install.sh
• #158 There is not need to have report name/directory customizable
• #157 There should be one logic/api that takes care of all files to be stored during/after test execution
• #146 Improve quick start experience (installation script)

Component: Maven

• #179 Some tests are not executable from the IDE
• #170 Suggest closest matching strategy when mispelled
• #168 .smart-testing folder is not removed if JVM is stopped
• #167 NPE is thrown is strategy is mispelled
• #166 Running affected strategy on assertj executes almost all test cases
• #165 Affected strategy analyze .class files when target dir not ignored

Component: Documentation

• #177 Add section about how to use it in Jenkins
• #163 Simplify documentation generation process
• #154 Update documentation with copy to clipboard extension
• #151 Create an Asciidoctor extension that adds a copy to clipboard button
• #149 Update documentation to use const extension
• #147 We should version documentation

Component: Selection

• #160 Should not fail If committed changes has deleted file

Thanks to the following list of contributors: Bartosz Majsak, Alex Soto, Matous Jobanek, Dipak Pawar

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

The Arquillian team is proud to announce the 1.9.0 release of the Arquillian Cube Extension component!

New version of Arquillian Cube 1.9.0 has been released with new features and bug fixes.

What’s new

Add support for network aliases

Add support for network aliases in docker compose format docker-compose aliases.

Disable OpenShift ImageStream detection by default

New flag has been added to enable/disable the detection of OpenShift Image Streams. These files must be located at target directory and their names should end with -is.yml.

By default this detection is disabled hence these files are not processed. If you want to enable you need to set OpenShift configuration parameter enableImageStreamDetection to true.

You can read more about this parameter at Arquillian Cube documentation

Many thanks to Georg Wolf, Jens and Ladislav Thon for their help.

What is Arquillian Cube Extension?

With Arquillian Cube you can control the lifecycle of Docker images as part of the test lifecyle, either automatically or manually. This gives you the chance to scale up from a integration/functional test level all the way up to the system test level.

Release details

Component	Arquillian Cube Extension
Version	1.9.0 view tag
Release date	2017-09-19
Released by	Alien Ike
Compiled against	Arquillian Core – 1.1.13.Final Arquillian Spacelift – 1.0.1 ShrinkWrap – 1.2.6 ShrinkWrap Resolver – 3.0.0-alpha-4

Published artifacts org.arquillian.cube

• org.arquillian.cube » arquillian-cube-api jar javadoc pom
• org.arquillian.cube » arquillian-cube-spi jar javadoc pom
• org.arquillian.cube » arquillian-cube-core jar javadoc pom
• org.arquillian.cube » arquillian-cube-containerless jar javadoc pom
• org.arquillian.cube » assertj-docker-java jar javadoc pom
• org.arquillian.cube » arquillian-cube-docker jar javadoc pom
• org.arquillian.cube » arquillian-cube-docker-drone jar javadoc pom
• org.arquillian.cube » arquillian-cube-docker-reporter jar javadoc pom
• org.arquillian.cube » arquillian-cube-docker-restassured jar javadoc pom
• org.arquillian.cube » arquillian-cube-docker-junit-rule jar javadoc pom
• org.arquillian.cube » arquillian-cube-openshift jar javadoc pom
• org.arquillian.cube » arquillian-cube-kubernetes-fabric8 jar javadoc pom
• org.arquillian.cube » arquillian-cube-kubernetes jar javadoc pom
• org.arquillian.cube » arquillian-cube-kubernetes-reporter jar javadoc pom
• org.arquillian.cube » arquillian-cube-requirement jar javadoc pom
• org.arquillian.cube » arquillian-cube-bom pom

Release notes and resolved issues 8

Bug

• #802 @RouteURL injection doesn't work when routerHost isn't configured.
• #795 Add a new property to disable detection of image stream files
• #789 NPE when getting default admin port
• #743 Arquillian Cube OpenShift namespace.use.existing + env.init.enabled=true fails to create test resources

Other

• #800 Can't set alwaysPull when using Compose format

Enhancement

• #797 Bump kubernetes client to 2.6.X
• #793 Add support for network aliases
• #791 Support for parallel tests with Cube Drone extension

Thanks to the following list of contributors: Ladislav Thon, Georg Wolf, Alex Soto, Filippe, Jonh Wendell, Arquillian, Jens, Ioannis Canellos, Bartosz Majsak