February 2010 - arquillian-issues

[JBoss JIRA] Created: (ARQ-66) provide a mechanism for adding library JARs (test dependencies) to the deployment

by Dan Allen (JIRA)

provide a mechanism for adding library JARs (test dependencies) to the deployment --------------------------------------------------------------------------------- Key: ARQ-66 URL: https://jira.jboss.org/jira/browse/ARQ-66 Project: Arquillian Issue Type: Feature Request Components: Core Reporter: Dan Allen Assignee: Pete Muir Fix For: 1.0.0-alpha-1 The requirement to add extra JARs into the deployment is going to surface fairly early on in the adoption of Arquillian. In our examples, we are sticking to APIs in Java EE, but most projects have third-party JARs on which the application depends. Common examples are a logging framework, Apache Commons libraries, Google Collections, Hibernate Search...anything not available in the container. We might need to update the @Deployment signature to support: @Deployment static Set<Archive<?>> x(); Or maybe a seperate @DeploymentDependencies (this could be defined in e.g. a super class) @DeploymentDependencies static Set<Archive<?>> x() We are also going to need to consider providing APIs for resolving Maven dependencies (groupId, artifactId, version) or resolving test dependencies from the Maven pom. We need to be flexible. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

3
10
0 / 0

[JBoss JIRA] Created: (ARQ-68) Ability to apply configuration changes to the container

by Pete Muir (JIRA)

Ability to apply configuration changes to the container ------------------------------------------------------- Key: ARQ-68 URL: https://jira.jboss.org/jira/browse/ARQ-68 Project: Arquillian Issue Type: Feature Request Reporter: Pete Muir For example, we might want to adjust something in conf/* in JBoss AS or perhaps add an installed library to the server. Whilst this might not be advisable testing practice, it is sometimes necessary! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
6
0 / 0

[JBoss JIRA] Created: (ARQ-30) @Deployment should have some intelligent defaults

by Aslak (JIRA)

@Deployment should have some intelligent defaults ------------------------------------------------- Key: ARQ-30 URL: https://jira.jboss.org/jira/browse/ARQ-30 Project: Arquillian Issue Type: Task Reporter: Aslak The API @Deployment should have some smart auto packaging options to help package the test - Add The TestCase itself - Add the TestCase package recursively - Add Resources in TestCase package ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

3
11
0 / 0

[JBoss JIRA] Created: (ARQ-55) TestNG @Test(dependsOnMethods="") does not work when running inside the container

by Aslak Knutsen (JIRA)

TestNG @Test(dependsOnMethods="") does not work when running inside the container --------------------------------------------------------------------------------- Key: ARQ-55 URL: https://jira.jboss.org/jira/browse/ARQ-55 Project: Arquillian Issue Type: Bug Components: TestNG Reporter: Aslak Knutsen "methodX is not allowed to depend on methodY" The way Arquillian invokes the remote container it creates a new 'suite' pr TestCase pr test method. Since only one test method is invoked pr suite, TestNGs dependsOnMethods fail. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (ARQ-67) Need to be able to deploy resources to the container alongside the primary deployment

by Pete Muir (JIRA)

Need to be able to deploy resources to the container alongside the primary deployment ------------------------------------------------------------------------------------- Key: ARQ-67 URL: https://jira.jboss.org/jira/browse/ARQ-67 Project: Arquillian Issue Type: Feature Request Reporter: Pete Muir Assignee: Pete Muir For examples, tests will need to be able to deploy -ds.xml, JMS configuration files etc. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

5
19
0 / 0

[JBoss JIRA] Created: (ARQ-37) Support JUnit @Test(expected = Exception.class)

by Aslak (JIRA)

Support JUnit @Test(expected = Exception.class) ----------------------------------------------- Key: ARQ-37 URL: https://jira.jboss.org/jira/browse/ARQ-37 Project: Arquillian Issue Type: Task Reporter: Aslak When doing remote calls, we should translate the Exceptions between the client/server so we can support Junit expected -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
6
0 / 0

[JBoss JIRA] Created: (ARQ-73) OSGi test container

by Pete Muir (JIRA)

OSGi test container ------------------- Key: ARQ-73 URL: https://jira.jboss.org/jira/browse/ARQ-73 Project: Arquillian Issue Type: Feature Request Reporter: Pete Muir Testing OSGi bundles is hard, because you need to generate the osgi bundle header from the classes in the test case. As we have control of the classpath through shrinkwrap, generating the header should be straightforward, as should setting up the container. Could offer Equinox, Felix or both. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (ARQ-70) Support Method argument injection

by Aslak Knutsen (JIRA)

Support Method argument injection --------------------------------- Key: ARQ-70 URL: https://jira.jboss.org/jira/browse/ARQ-70 Project: Arquillian Issue Type: Feature Request Reporter: Aslak Knutsen Assignee: Aslak Knutsen TestEnrichers should be extended to support method argument injection. {code} @Test public void shouldBeAbleToInjectArguments(@Resource, @EJB, MyCDIBean) throws Exception { } {code} e.g: {code} public interface TestEnricher { /** * Extension point to add features to the test method arguments. * * IE. Argument injection * * @param method * @return Object[] that match the Field[] indexes. Return null at a specific index value if it can't be handeled. */ Object[] resolve(Method method); } {code} -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (ARQ-71) Should be able to run the test case locally

by Aslak Knutsen (JIRA)

Should be able to run the test case locally ------------------------------------------- Key: ARQ-71 URL: https://jira.jboss.org/jira/browse/ARQ-71 Project: Arquillian Issue Type: Feature Request Reporter: Aslak Knutsen It should be possible to just use Arquillian for packaging/deployment for a test case without actually running the test case inside the container. Needed to ie support testing of Servlets, or EJB Remoting -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
5
0 / 0

[JBoss JIRA] Created: (ARQ-69) Redesign the test framework adaptor

by Aslak Knutsen (JIRA)

Redesign the test framework adaptor ----------------------------------- Key: ARQ-69 URL: https://jira.jboss.org/jira/browse/ARQ-69 Project: Arquillian Issue Type: Task Components: Core, Documentation, JUnit, TestNG Reporter: Aslak Knutsen Assignee: Aslak Knutsen Too much of the Arquillian core responsibility is handed out to the Test Framework integration code. Redesign to a more event/lifecycle based integration. The DeployableTestBuilder should return a appropriate impl depending on in container or not. {code} public interface DeployableTestRunner { public void beforeSuite() throws LifecycleException public void afterSuite() throws LifecycleException public void beforeClass(Class<?> testClass) throws DeploymentException public void afterClasss(Class<?> testClass) throws DeploymentException public void before(Class<?> testClass, Method testMethod) public void after(Class<?> testClass, Method testMethod) public TestResult test(TestMethodExecutor testMethodExecutor) } {code} -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues February 2010