September 2011 - arquillian-issues

[JBoss JIRA] Created: (ARQ-611) If Drone extension is on classpath but not used, destroying drone instance will lead to failure

by Karel Piwko (JIRA)

If Drone extension is on classpath but not used, destroying drone instance will lead to failure ----------------------------------------------------------------------------------------------- Key: ARQ-611 URL: https://issues.jboss.org/browse/ARQ-611 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Drone Affects Versions: drone_1.0.0.CR2 Reporter: Karel Piwko Priority: Critical Fix For: drone_1.0.0.Final {code} java.lang.IllegalArgumentException: Drone context should have been instantiated at org.jboss.arquillian.drone.impl.Validate.notNull(Validate.java:42) at org.jboss.arquillian.drone.impl.DroneDestructor.destroyClassScopedDrone(DroneDestructor.java:74) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:68) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:54) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:134) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:114) at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.afterClass(EventTestRunnerAdaptor.java:87) at org.jboss.arquillian.junit.Arquillian$3$1.evaluate(Arquillian.java:180) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:290) at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:45) at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:175) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:123) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

3
4
0 / 0

[JBoss JIRA] Created: (ARQ-599) ApplicationArchiveInstrumenter should also also instrument classes inside JARs

by Marek Schmidt (JIRA)

ApplicationArchiveInstrumenter should also also instrument classes inside JARs ------------------------------------------------------------------------------ Key: ARQ-599 URL: https://issues.jboss.org/browse/ARQ-599 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Jacoco Affects Versions: jacoco_1.0.0.Alpha1 Reporter: Marek Schmidt Classes inside packaged .jars are not instrumented. ApplicationArchiveInstrumenter should also instrument classes inside archives. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

4
7
0 / 0

[JBoss JIRA] Created: (ARQ-336) Inject container references in the test to start/stop containers

by Jean Deruelle (JIRA)

Inject container references in the test to start/stop containers ---------------------------------------------------------------- Key: ARQ-336 URL: https://jira.jboss.org/browse/ARQ-336 Project: Arquillian Issue Type: Feature Request Components: Base Implementation Reporter: Jean Deruelle Useful to test HA configuration and failover. Start 3 instances of JBoss AS in cluster mode target one of them and be able to kill it and start new nodes on demand to test failover. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

12
35
0 / 0

[JBoss JIRA] Created: (ARQ-570) Minor docs typos

by Ondrej Zizka (JIRA)

Minor docs typos ---------------- Key: ARQ-570 URL: https://issues.jboss.org/browse/ARQ-570 Project: Arquillian Issue Type: Quality Risk Security Level: Public (Everyone can see) Components: Documentation Reporter: Ondrej Zizka Priority: Trivial {code} @Test // runs in container public void shouldBeAbleToRunOnClientSide() throws Exception { } {code} I thin that should be named `shouldBeAbleToRunOnContainerSide`. {code} @ArquillianResource(MyServlet.class) private URL baseServerURL; {code} I think that should be baseServletURL. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

4
3
0 / 0

[JBoss JIRA] Created: (ARQ-474) provide a mechanism to order the test runs

by Prabhat Jha (JIRA)

provide a mechanism to order the test runs ------------------------------------------ Key: ARQ-474 URL: https://issues.jboss.org/browse/ARQ-474 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Test Harness Integration Affects Versions: 1.0.0.Beta1 Reporter: Prabhat Jha Currently there exists annotation for deployment ordering but there does not exist a way to control the order in which one wants to run the test. TestNG does have ordering via depends method but JUnit does not. Usually, it's recommended to not have a dependency of test order but in case of clustering and data grid testing where you want to verify replication, it makes sense to have that. Please add a fix version which makes a sense based on the roadmap you have. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

8
14
0 / 0

[JBoss JIRA] Created: (ARQ-605) Arquillian TestNG base class breaks tests TestNG groups

by Tom Barlow (JIRA)

Arquillian TestNG base class breaks tests TestNG groups ------------------------------------------------------- Key: ARQ-605 URL: https://issues.jboss.org/browse/ARQ-605 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Integration Test Suite Affects Versions: 1.0.0.CR5 Reporter: Tom Barlow The 'alwaysRun' parameter on the Arquillian TestNG base class causes these methods to ALWAYS get run, even when Arquillian tests are excluded via their group. @BeforeSuite(alwaysRun = true) public void arquillianBeforeSuite() throws Exception This has a side effect of breaking maven profiles that use testng groups to select their tests. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

6
6
0 / 0

[JBoss JIRA] Created: (ARQ-382) Move Reference Guide to new Confluence jboss.org instance.

by Aslak Knutsen (JIRA)

Move Reference Guide to new Confluence jboss.org instance. ---------------------------------------------------------- Key: ARQ-382 URL: https://issues.jboss.org/browse/ARQ-382 Project: Arquillian Issue Type: Feature Request Components: Documentation Affects Versions: 1.0.0.Beta1 Reporter: Aslak Knutsen We should move the Reference Guide over to the new Confluence space for easy edit. We will probably lose some of the jira commit docs references, but so be it.. https://docs.jboss.org/author/display/ARQ/Home -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

3
5
0 / 0

[JBoss JIRA] Created: (ARQ-594) The reference guide at http://docs.jboss.org/arquillian/reference/latest/ should be removed

by Marek Schmidt (JIRA)

The reference guide at http://docs.jboss.org/arquillian/reference/latest/ should be removed ------------------------------------------------------------------------------------------- Key: ARQ-594 URL: https://issues.jboss.org/browse/ARQ-594 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 1.0.0.CR4 Reporter: Marek Schmidt The reference documentation at http://docs.jboss.org/arquillian/reference/latest/ is outdated and thus misleading, as users think it is the "latest". Until ARQ-382 is resolved, the docs should be removed or redirect to https://docs.jboss.org/author/display/ARQ/Home instead. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

3
2
0 / 0

[JBoss JIRA] Created: (ARQ-532) Add SPI for @ArquillianResource ResourceProvider

by Aslak Knutsen (JIRA)

Add SPI for @ArquillianResource ResourceProvider ------------------------------------------------ Key: ARQ-532 URL: https://issues.jboss.org/browse/ARQ-532 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Base Implementation Reporter: Aslak Knutsen Fix For: 1.1.0.Beta1 Currently the list of ResourceProvider's are hardcoded in ArquillianResourceTestEnricher, this should be extracted out as a Service. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

5
5
0 / 0

[JBoss JIRA] Created: (ARQ-49) Arquillian depends upon ShrinkWrap internals

by Andrew Lee Rubinger (JIRA)

Arquillian depends upon ShrinkWrap internals -------------------------------------------- Key: ARQ-49 URL: https://jira.jboss.org/jira/browse/ARQ-49 Project: Arquillian Issue Type: Task Reporter: Andrew Lee Rubinger Caught that a few Arquillian classes are directly depending upon ShrinkWrap internals, for which we cannot provide guarantee of consistency between releases. [alr@localhost trunk]$ egrep 'shrinkwrap.impl' -R . |grep .java ./demo/src/test/java/com/acme/cdi/InjectionTestCase.java:import org.jboss.shrinkwrap.impl.base.asset.ByteArrayAsset; ./demo/src/test/java/com/acme/cdi/.svn/text-base/InjectionTestCase.java.svn-base:import org.jboss.shrinkwrap.impl.base.asset.ByteArrayAsset; ./impl-base/src/main/java/org/jboss/arquillian/impl/ArquillianDeploymentAppender.java: Package.getPackage("org.jboss.shrinkwrap.impl.base"), ./impl-base/src/main/java/org/jboss/arquillian/impl/.svn/text-base/ArquillianDeploymentAppender.java.svn-base: Package.getPackage("org.jboss.shrinkwrap.impl.base"), ./junit/src/main/java/org/jboss/arquillian/junit/JUnitTestRunner.java:import org.jboss.shrinkwrap.impl.base.Validate; ./junit/src/main/java/org/jboss/arquillian/junit/.svn/text-base/JUnitTestRunner.java.svn-base:import org.jboss.shrinkwrap.impl.base.Validate; ./testng/src/main/java/org/jboss/arquillian/testng/TestNGTestRunner.java:import org.jboss.shrinkwrap.impl.base.Validate; ./testng/src/main/java/org/jboss/arquillian/testng/.svn/text-base/TestNGTestRunner.java.svn-base:import org.jboss.shrinkwrap.impl.base.Validate; ./demo-testng/src/test/java/com/acme/cdi/InjectionTestCase.java:import org.jboss.shrinkwrap.impl.base.asset.ByteArrayAsset; ./demo-testng/src/test/java/com/acme/cdi/.svn/text-base/InjectionTestCase.java.svn-base:import org.jboss.shrinkwrap.impl.base.asset.ByteArrayAsset; Likely we'll want to evaluate these dependencies and instead move to API-only (for compile time, runtime requiring ShrinkWrap impls in "test" scope). -- 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

6
10
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues September 2011