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.4 release of the Smart Testing component!

Highlights of this release

In this release we shipped two key new features – support for JUnit 5 and declarative way of defining relations between tests and business code. And bunch of fixes.

Annotations for affected tests

Starting from this release you are able to use declarative way of defining relationship between test and business code. By default affected strategy uses imports declared in the tests to build the graph of collaborators. This approach is fine for unit tests (white box tests) but might not work for higher level tests (black box test).

Using annotation like below you can define classes or packages which particular test covers.

@ComponentUnderTest(packages = "org.acme.main.superbiz.*")
public class AcmeServiceRestTest { ... }

Check our detailed documentation on how to use it.

What’s next

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 details

Component	Smart Testing
Version	0.0.4 view tag
Release date	2017-11-14
Released by	Bartosz Majsak
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 » 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 » 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 13

Component: Test Bed

• #259 Test is failing if running from IntelliJ

Component: Maven

• #253 Plugin selection using `ApplyTo` property not working
• #245 JUnit5 and JUnit4 cannot be mixed
• #235 Look for configuration file recursively in the parent directories.
• #216 Should not register ST extension if user is trying to run it with project which doesn't have scm repository setup
• #142 Should not register extension if skipTests is configured in pom.xml
• #92 Configurable list of strategies
• #15 Supporting JUnit 5

Other

• #252 Plugin selection using `ApplyTo` property not working
• #248 Getting NPE if providing empty smart-testing.yml

Component: Core

• #242 Introduce parameter for pointing to a custom configuration file
• #207 Add support for configuring strategies separately

Component: Selection

• #199 Smart Testing annotations for Affected

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

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

The Arquillian team is proud to announce the 3.0.0 release of the ShrinkWrap Resolver component!

In the final release of ShrinkWrap Resolver 3.0.0, we are introducing you one new feature into the EmbeddedMaven logic.

Maven build invocation command & Logging

In the previous releases, there was no easy way to get the DEBUG log from the Maven Invoker tool, including the command that is used for Maven build invocation.
In this release, we are introducing a method setDebugLoggerLevel() that sets the threshold of the InvokerLogger to DEBUG level. An example of the usage is:

EmbeddedMaven.forProject("path/to/pom.xml").setDebugLoggerLevel()

When it is set, then in the very beginning of the debug log, there is also contained the command that is used for the Maven build invocation. That will help you with debugging your potential problematic Maven builds.

Apart from this feature, you can find also several improvements, component upgrades and a lot of bug fixes there. For more information, check the release notes and resolved issues listed at the end of this announcement.

What is ShrinkWrap Resolver?

The ShrinkWrap Resolvers project provides a Java API to obtain artifacts from a repository system. This is handy to include third party libraries available in any Maven repository in your test archive. ShrinkWrap Resolvers additionally allow you to reuse all the configuration you've already specified in the Maven build file, making packaging of an application archive much easier job.

Release details

Component	ShrinkWrap Resolver
Version	3.0.0 view tag
Release date	2017-11-09
Released by	Matous Jobanek
Compiled against	Arquillian Spacelift – 1.0.2 JUnit – 4.12

Published artifacts org.jboss.shrinkwrap.resolver

• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-bom pom
• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-api jar javadoc pom
• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-spi jar javadoc pom
• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-depchain pom
• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-api-maven jar javadoc pom
• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-impl-maven jar javadoc pom
• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-api-maven-archive jar javadoc pom
• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-spi-maven jar javadoc pom
• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-spi-maven-archive jar javadoc pom
• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-impl-maven-archive jar javadoc pom
• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-api-maven-embedded jar javadoc pom
• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-impl-maven-embedded jar javadoc pom
• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-impl-gradle jar javadoc pom
• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-api-gradle-embedded-archive jar javadoc pom
• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-gradle-depchain pom
• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-impl-gradle-embedded-archive jar javadoc pom

Release notes and resolved issues 6

Component Upgrade

• SHRINKRES-277 - Upgrade to maven-invoker 3.0.0
• SHRINKRES-278 - Update Spacelift to 1.0.2 & AssertJ to 3.8.0
• SHRINKRES-280 - Update Gradle Tooling API to 4.0.1

Enhancement

• SHRINKRES-279 - There is no easy way to get command that will be used for Maven build invocation

Feature Request

• SHRINKRES-281 - Provide FormatProcessor for java.nio.file.Path

Bug

• SHRINKRES-275 - Dowloading/extracting of Maven binaries is not tread-safe

Thanks to the following list of contributors: Matous Jobanek, Hemani, Gunnar Morling

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

The Arquillian team is proud to announce the 2.4.5 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.5 view tag
Release date	2017-11-13
Released by	Matous Jobanek
Compiled against	Arquillian Core – 1.1.13.Final Arquillian Spacelift – 1.0.2 Selenium – 3.7.1

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

Bug

• ARQ-2151 - Cannot set useAutomationExtension option for chrome

Thanks to the following list of contributors: Matous Jobanek, Peter Kullmann

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

The Arquillian team is proud to announce the 2.4.4 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.4 view tag
Release date	2017-11-09
Released by	Matous Jobanek
Compiled against	Arquillian Core – 1.1.13.Final Arquillian Spacelift – 1.0.2 Selenium – 3.7.1

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 3

Component Upgrade

• ARQ-2149 - Upgrade to Selenium 3.7.1
• ARQ-2150 - Update HtmlUnit driver to 2.27

Bug

• ARQ-2151 - Cannot set useAutomationExtension option for chrome

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 1.9.2 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.2 view tag
Release date	2017-11-09
Released by	Bartosz Majsak
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 7

Other

• #843 Ability to refer to route names using system properties
• #842 Await for availability of injected @RouteURL
• #839 @RouteURL shouldn't add a port number when it's the default for the protocol
• #838 @RouteURL should have a parameter to customize the path portion of the URL
• #837 the @AwaitRoute mechanism probably doesn't deal nicely with self-signed HTTPS certs
• #827 add @AwaitRoute

Bug

• #829 DockerClientException: Could not build image: null when building from dockerfile

Thanks to the following list of contributors: Ladislav Thon, Bartosz Majsak, Arquillian, Ales Justin, Alex Soto