[ https://issues.jboss.org/browse/ARQ-561?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen commented on ARQ-561: ----------------------------------- Meaning you want to it execute the @Test multiple times if you @Inject a List as a MethodArgument ? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ARQ-561?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen commented on ARQ-561: ----------------------------------- Karel, is this in any form useful as a workaround for now? https://gist.github.com/1358803 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ARQ-561?page=com.atlassian.jira.plugin.sy... ] Bartosz Majsak commented on ARQ-561: ------------------------------------ There is also another nice project for JUnit which mimics TestNG parametrization approach - http://code.google.com/p/junitparams/ Maybe this one is worth to try out as an alternative? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ARQ-561?page=com.atlassian.jira.plugin.sy... ] Karel Piwko commented on ARQ-561: --------------------------------- My opinion is that we should leverage Theories from JUnit experimental if possible, because it is much easier to read them, hovewer they still have problems 1/ and 2/ as described above. {code} @RunWith(ArquillianTheories.class) // this is a POC - Arquillian.class content which extends Theories instead of BlockJUnit4ClassRunner public class CDITest { @Inject HelloService service; @DataPoints // this must be static public static String[] services() { return new String[] { "service1", "service2" }; } @Deployment public static WebArchive createDeployment() { return ShrinkWrap.createFromZipFile(WebArchive.class, new File("../package-cdi-war/target/test.war")); } @Theory public void cdiTest(String name) { Assert.assertNotNull("Name not null, " + name, name); // this is not injected Assert.assertNotNull("Service not null", service); // this will fail Assert.assertEquals("Hello World!", service.createHelloMessage("World")); } } {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ARQ-561?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen edited comment on ARQ-561 at 1/24/12 8:58 AM: ------------------------------------------------------------ It would be executed both incontainer and on the client side if not one of them were skipped. We could have enhanced that with support for e.g. @RunAsClient. If we had executed the Client side multiple times for a Remote call, the Remote side would be invoked multiple times as well was (Author: aslak): It would be executed both incontainer and on the client side if not one of them were skipped. We could have enhanced that with support for e.g. @RunAsClient -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira