- Injection of Spring beans into test classes
- Configuration from both XML and Java-based config
- Injecting beans configured in web application (e.g. DispatcherServlet) for tests annotated with @SpringWebConfiguration
- Support for both Spring(@Autowired, @Qualifier, @Required) and JSR-330(@Inject, @Named) annotations
- Bean initialization support (@PostConstruct)
- Auto packaging the spring-context and spring-web artifacts.
- Spring 4+
The extension is splitted into couple modules. In order to enable the Spring IOC for the Arquillian Tests it is required to add the following dependency into the project POM.
<dependency>
<groupId>org.jboss.arquillian.extension</groupId>
<artifactId>arquillian-service-integration-spring-inject</artifactId>
<version>${arquillian.spring.version}</version>
<scope>test</scope>
</dependency>
Java config is also supported and it requires following dependency:
<dependency>
<groupId>org.jboss.arquillian.extension</groupId>
<artifactId>arquillian-service-integration-spring-javaconfig</artifactId>
<version>${arquillian.spring.version}</version>
<scope>test</scope>
</dependency>
Each Arquillian test which relies on Spring framework and requires dependency injection of configured beans has to be
annotated with one of the following:
@SpringConfiguration - for xml configuration, @SpringAnnotationConfiguration - for Java-based configuration
and @SpringWebConfiguration - for web applications.
The annotation will instruct the test enricher how to initialize the application context, the first two will cause that
for each test case new application context will be created. @SpringWebConfiguration is used for retrieving the context of
specific Spring FrameworkServlet (e.g. DispatcherServlet) or the root web application context in general.
Note: The annotations may not be mixed with each other, each test will use only one application context.
It's posible to modify the default behaviour of the extension and set the following settings through arquillian.xml.
- Name of custom context classes to be used instead of Spring's ClassPathXmlApplicationContext and AnnotationConfigApplicationContext.
Note: When using the extension with Maven the artifacts version is being read from POM file directly. Modifying the version in the arquillian.xml will have no effect. It's intention is to support other then Maven build systems.
Example:
<?xml version="1.0" encoding="UTF-8"?>
<arquillian xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://jboss.org/schema/arquillian"
xsi:schemaLocation="http://jboss.org/schema/arquillian http://jboss.org/schema/arquillian/arquillian_1_0.xsd">
<extension qualifier="spring">
<!-- The name of custom context class, optional, when not specified
then org.springframework.context.support.ClassPathXmlApplicationContext will be used -->
<property name="customContextClass">org.springframework.context.support.ClassPathXmlApplicationContext</property>
<!-- The name of custom context class, optional, when not specified then
org.springframework.context.annotation.AnnotationConfigApplicationContext -->
<property name="customAnnotationContextClass">org.springframework.context.annotation.AnnotationConfigApplicationContext</property>
</extension>
</arquillian>
The test which requires the dependencies to be injected through Spring should be annotated with @SpringConfiguration. The annotations provides the information where to look for the spring configuration
<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:context="http://www.springframework.org/schema/context"
xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-3.0.xsd http://www.springframework.org/schema/context http://www.springframework.org/schema/context/spring-context-3.1.xsd">
<context:component-scan base-package="org.jboss.arquillian.spring.testsuite.beans.repository.impl"/>
<context:component-scan base-package="org.jboss.arquillian.spring.testsuite.beans.service.impl"/>
</beans>Test example
@RunWith(Arquillian.class)
@SpringConfiguration({"applicationContext.xml"})
public class DefaultEmployeeRepositoryTestCase {
@Deployment
public static JavaArchive createTestArchive() {
return ShrinkWrap.create(JavaArchive.class, "spring-test.jar")
.addClasses(Employee.class,
EmployeeRepository.class, DefaultEmployeeRepository.class, NullEmployeeRepository.class)
.addAsResource("applicationContext.xml");
}
@Autowired
@Qualifier("defaultEmployeeRepository")
private EmployeeRepository employeeRepository;
@Test
public void testGetEmployees() throws Exception {
List<Employee> result = employeeRepository.getEmployees();
assertNotNull("Method returned null list as result.", result);
assertEquals("Two employees were expected.", 2, result.size());
}
}@Configuration
public class AppConfig {
@Bean
public EmployeeRepository defaultEmployeeRepository() {
return new DefaultEmployeeRepository();
}
@Bean
public EmployeeService defaultEmployeeService() {
return new DefaultEmployeeService();
}
}Test example
@RunWith(Arquillian.class)
@SpringAnnotationConfiguration(classes = {AppConfig.class})
public class AnnotatedConfigurationTestCase {
@Deployment
public static JavaArchive createTestArchive() {
return ShrinkWrap.create(JavaArchive.class, "spring-test.jar")
.addClasses(Employee.class,
EmployeeService.class, DefaultEmployeeService.class,
EmployeeRepository.class, DefaultEmployeeRepository.class, NullEmployeeRepository.class,
AppConfig.class);
}
@Autowired
private EmployeeService employeeService;
@Test
public void testGetEmployees() throws Exception {
List<Employee> result = employeeService.getEmployees();
assertNotNull("Method returned null list as result.", result);
assertEquals("Two employees were expected.", 2, result.size());
}
}The above examples allowed testing seperate classes injected through Spring without configuring entire web application, following example demonstrates how to test a simple MVC application instead.
Simple annotated controller
@Controller
public class EmployeeController {
@Autowired
private EmployeeService employeeService;
@RequestMapping("/Employees.htm")
public String getEmployees(Model model) {
model.addAttribute("employees", employeeService.getEmployees());
return "employeeList";
}
}Web.xml
<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd"
version="3.0">
<listener>
<listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>
</listener>
<servlet>
<servlet-name>employee</servlet-name>
<servlet-class>org.springframework.web.servlet.DispatcherServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>employee</servlet-name>
<url-pattern>*.htm</url-pattern>
</servlet-mapping>
</web-app>Note: The ContextLoaderListener is required here, mostly because each dispatcher servlet has it own application context that is inaccessible from outside. To overcome this limitation the extensions requires that the web application will create Root Web Application Context by defining ContextLoaderListener or ContextLoaderServlet in it's web.xml.
Configuration files
In this example the Spring context is configured through a xml file.
employee-servlet.xml
<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:context="http://www.springframework.org/schema/context"
xmlns:mvc="http://www.springframework.org/schema/mvc"
xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-3.0.xsd http://www.springframework.org/schema/context http://www.springframework.org/schema/context/spring-context-3.1.xsd http://www.springframework.org/schema/tool http://www.springframework.org/schema/tool/spring-tool-3.1.xsd http://www.springframework.org/schema/mvc http://www.springframework.org/schema/mvc/spring-mvc-3.1.xsd">
<context:component-scan base-package="org.jboss.arquillian.spring.testsuite.beans.repository.impl"/>
<context:component-scan base-package="org.jboss.arquillian.spring.testsuite.beans.service.impl"/>
<context:component-scan base-package="org.jboss.arquillian.spring.testsuite.beans.controller"/>
<mvc:annotation-driven />
<bean id="viewResolver"
class="org.springframework.web.servlet.view.UrlBasedViewResolver">
<property name="viewClass" value="org.springframework.web.servlet.view.JstlView"/>
<property name="prefix" value="/WEB-INF/jsp/"/>
<property name="suffix" value=".jsp"/>
</bean>
</beans>Test
It is possible to inject into the test fully configured Spring MVC controller and run on it simple tests in the container.
@RunWith(Arquillian.class)
@SpringWebConfiguration(servletName = "employee")
public class EmployeeControlerTestCase {
@Deployment
@OverProtocol("Servlet 3.0")
public static WebArchive createTestArchive() {
return ShrinkWrap.create(WebArchive.class, "spring-test.war")
.addClasses(Employee.class,
EmployeeService.class, DefaultEmployeeService.class,
EmployeeRepository.class, DefaultEmployeeRepository.class, NullEmployeeRepository.class,
EmployeeController.class)
.addAsLibraries(springDependencies())
.addAsLibraries(mockitoDependencies())
.addAsWebInfResource("mvc/web.xml", "web.xml")
.addAsWebInfResource("mvc/employee-servlet.xml", "employee-servlet.xml")
.addAsWebInfResource("mvc/applicationContext.xml", "applicationContext.xml");
}
/**
* The injected {@link EmployeeController}.
*/
@Autowired
private EmployeeController employeeController;
/**
* Tests {@link EmployeeController#getEmployees(org.springframework.ui.Model)} method.
*/
@Test
public void testGetEmployees() {
String result;
Model model;
ArgumentCaptor<List> argument;
assertNotNull("The controller hasn't been injected.", employeeController);
model = mock(Model.class);
argument = ArgumentCaptor.forClass(List.class);
result = employeeController.getEmployees(model);
verify(model).addAttribute(eq("employees"), argument.capture());
assertEquals("The controller returned invalid view name, 'employeeList' was expected.", "employeeList", result);
assertEquals("Two employees should be returned from model.", 2, argument.getValue().size());
}
}Again, the above configuration can be also done without any piece of XML (even without a web.xml descriptor). All thanks to WebApplicationInitializer which allows to set up the servlets programmatically.
Instead of defining web.xml it is possible to write a simple class:
public class EmployeeWebInitializer implements WebApplicationInitializer {
public void onStartup(ServletContext servletContext) throws ServletException {
// creates the web app context
AnnotationConfigWebApplicationContext webContext = new AnnotationConfigWebApplicationContext();
webContext.register(WebAppConfig.class);
// registers context load listener
servletContext.addListener(new ContextLoaderListener(new AnnotationConfigWebApplicationContext()));
// adds a dispatch servlet, the servlet will be configured from the created application context
ServletRegistration.Dynamic servletConfig = servletContext.addServlet("employee",
new DispatcherServlet(webContext));
servletConfig.setLoadOnStartup(1);
servletConfig.addMapping("*.htm");
}
}Only what is left to do is define a configuration for the Spring context.
@Configuration
@EnableWebMvc
@ComponentScan(basePackages = {
"org.jboss.arquillian.spring.testsuite.beans.repository.impl",
"org.jboss.arquillian.spring.testsuite.beans.service.impl",
"org.jboss.arquillian.spring.testsuite.beans.controller"})
public class WebAppConfig {
/**
* <p>Retrieves instance of {@link ViewResolver}.</p>
*
* @return instance of {@link ViewResolver}
*/
@Bean
public ViewResolver viewResolver() {
InternalResourceViewResolver resolver = new InternalResourceViewResolver();
resolver.setPrefix("/WEB-INF/views/");
resolver.setSuffix(".jsp");
return resolver;
}
}Test code
Now the test deployment doesn't require any kind of descriptors.
@RunWith(Arquillian.class)
@SpringWebConfiguration(servletName = "employee")
public class EmployeeControllerWebInitTestCase {
@Deployment
@OverProtocol("Servlet 3.0")
public static WebArchive createTestArchive() {
return ShrinkWrap.create(WebArchive.class, "spring-test.war")
.addClasses(Employee.class,
EmployeeService.class, DefaultEmployeeService.class,
EmployeeRepository.class, DefaultEmployeeRepository.class, NullEmployeeRepository.class,
EmployeeController.class, WebAppConfig.class, EmployeeWebInitializer.class)
.addAsLibraries(springDependencies())
.addAsLibraries(mockitoDependencies());
}
/**
* The injected {@link EmployeeController}.
*/
@Autowired
private EmployeeController employeeController;
/**
* Tests {@link EmployeeController#getEmployees(org.springframework.ui.Model)} method.
*/
@Test
public void testGetEmployees() {
String result;
Model model;
ArgumentCaptor<List> argument;
assertNotNull("The controller hasn't been injected.", employeeController);
model = mock(Model.class);
argument = ArgumentCaptor.forClass(List.class);
result = employeeController.getEmployees(model);
verify(model).addAttribute(eq("employees"), argument.capture());
assertEquals("The controller returned invalid view name, 'employeeList' was expected.", "employeeList", result);
assertEquals("Two employees should be returned from model.", 2, argument.getValue().size());
}
}For additional examples please take a look at the Showcase
mvn clean install
Available profiles (for running the integration tests in the container):
- jbossas-managed
- glassfish-embedded