[
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}
Make Arquillian compatible with JUnit Parametrized runner
---------------------------------------------------------
Key: ARQ-561
URL:
https://issues.jboss.org/browse/ARQ-561
Project: Arquillian
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Test Harness Integration
Reporter: Ondrej Skutka
Labels: arq_qe_blocker
Make Arquillian runner compatible with JUnit's Parametrized runner
(org.junit.runners.Parameterized).
--
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