[ https://issues.jboss.org/browse/ARQ-1303?page=com.atlassian.jira.plugin.s... ] Jakub Narloch commented on ARQ-1303: ------------------------------------ Ok, But in such case, how can I use that in my test? I would have to 'lookup' the bean that is being test each time from the application context. You won't be able to inject you configured beans into the the tests directly. I was thinking about different aproach. How about resigning from class level annotations in favor of 'factory method'. Something like: {code} public class TestCase { @SpringApplicationContext public static ApplicationContext createApplicationContext() { return ... // the application context could be created fully programticly } public void test() { } } {code} In such way we could just @Autowire the beans in to the test class afterwards. Also we would have access to the ApplicationContext by simply adding @Autowired ApplicationContext field. It would work out of the box (likely this feature has been added somewhere in Spring 2.5.x version). The other thing I was thinking was using the same convention as in Spring Test 3.1. You are able to define static inner class annotated with @Configuration and define your beans there. Something like: {code} @SpringAnnotationConfiguration public class TestCase { @Configuration static class ContextConfiguration { @Bean public SomeBean create() { } } public void test() { } } {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira