Content tagged with: integration testing
Arquillian is a open source platform sponsored by JBoss that simplifies the testing of Java middleware. It brings your test to the runtime, freeing you from the concern of managing the runtime from your test and letting you focused on writing your integration test logic. This blog post by Nikolas Frankel explains how to to test Java EE components on JBoss 5.1 EAP with Arquilian and TestNG. His conclusion is that Arquillian seems to be a nice in-container testing framework but seems to have to be polished around some corners. …
This blog post explains how to separate integration and unit tests with Maven, Sonar, Failsafe and JaCoCo. This is achieved by executing unit tests via Surefire and integration tests via Failsafe. Then you show as much information about them as possible in Sonar. The post provides detailed command lines and Maven configuration files to achieve this goal.
This presentation addresses the missing link in Enterprise Java development: simple, easy integration testing. You will learn how the simplified component model of Java EE can be applied to testable development.
Integration tests are performed after a successful execution of unit tests. Integration tests are, therefore, executed less frequently, because unit tests will naturally fail often. With this strict separation between unit tests and integration tests, we can save several minutes (sometimes, hours) with each turnaround. This article explains how integration testing can increase your productivity and ensure the deployability of your Java EE 6 application.
In this podcast Red Hat principal software engineer and open source evangelist Dan Allen explains how Arquillian eases integration testing. The mission of the Arquillian project is to provide a simple test harness that abstracts away all container lifecycle and deployment from the test logic so developers can easily produce a broad range of integration tests for their enterprise Java applications.
This blog post explains how to keep your unit and integration tests in separate packages when you perform a standard Maven build.