June 2013 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-127) Verify TestNG Parallel test exeuction

by Michal Vanco (JIRA)

[ https://issues.jboss.org/browse/ARQ-127?page=com.atlassian.jira.plugin.sy... ] Michal Vanco commented on ARQ-127: ---------------------------------- Hi, can you provide some update on this? It would be a big good-to-have for my usage of arquillian-testng-standalone + graphene2. Right now I'm getting this error: {noformat} java.lang.IllegalStateException: No TestRunnerAdaptor found, @BeforeSuite has not been called at org.jboss.arquillian.testng.Arquillian.verifyTestRunnerAdaptorHasBeenSet(Arquillian.java:246) at org.jboss.arquillian.testng.Arquillian.arquillianBeforeClass(Arquillian.java:101) 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:601) at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:564) at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:213) at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:138) at org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:175) at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:107) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:722) ... {noformat} > Verify TestNG Parallel test exeuction > ------------------------------------- > > Key: ARQ-127 > URL: https://issues.jboss.org/browse/ARQ-127 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Performance, Test Harness Integration > Reporter: Aslak Knutsen > Assignee: Ståle Pedersen > Priority: Critical > Fix For: 2.0.0.Beta1 > > > Verify that Arquillian behaves correctly when ran in TestNG Parallel modes. -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1389) Create an extension that allows users to specify CDI context active for a test.

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-1389?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak edited comment on ARQ-1389 at 6/5/13 4:14 AM: ------------------------------------------------------------- There is something already in place, but more focused on CDI/JSF world - https://community.jboss.org/thread/200461 was (Author: bmajsak): There is something already in place, but more focused on CDI/JSF integration - https://community.jboss.org/thread/200461 > Create an extension that allows users to specify CDI context active for a test. > ------------------------------------------------------------------------------- > > Key: ARQ-1389 > URL: https://issues.jboss.org/browse/ARQ-1389 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: John Ament > > I've seen the need for this to pop up in several places - at work, in SO questions, in email threads, and I think it would be ideal to handle as a new Arquillian Extension. Right now, Arquillian is dependent on the app server to manage context and typically the context activated is whatever the app server finds as appropriate. This works OK for servlet based containers since a RequestScope will be active, but for local, embedded (non servlet) or even JMX protocol based containers this doesn't work. > Ideally, a developer would be able to annotate a test method: > @ActiveContext(ValidScope.class) > Where ValidScope.class is a CDI scope (RequestScoped, SessionScoped.. etc) that can be activated. The extension would then activate this scope for the duration of the test, allowing injection of appropriately scoped objects to be injected correctly. > Perhaps this annotation can also be class level, applying to everything in that class. -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1389) Create an extension that allows users to specify CDI context active for a test.

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-1389?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak commented on ARQ-1389: ------------------------------------- There is something already in place, but more focused on CDI/JSF integration - https://community.jboss.org/thread/200461 > Create an extension that allows users to specify CDI context active for a test. > ------------------------------------------------------------------------------- > > Key: ARQ-1389 > URL: https://issues.jboss.org/browse/ARQ-1389 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: John Ament > > I've seen the need for this to pop up in several places - at work, in SO questions, in email threads, and I think it would be ideal to handle as a new Arquillian Extension. Right now, Arquillian is dependent on the app server to manage context and typically the context activated is whatever the app server finds as appropriate. This works OK for servlet based containers since a RequestScope will be active, but for local, embedded (non servlet) or even JMX protocol based containers this doesn't work. > Ideally, a developer would be able to annotate a test method: > @ActiveContext(ValidScope.class) > Where ValidScope.class is a CDI scope (RequestScoped, SessionScoped.. etc) that can be activated. The extension would then activate this scope for the duration of the test, allowing injection of appropriately scoped objects to be injected correctly. > Perhaps this annotation can also be class level, applying to everything in that class. -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-381) Annotation to add transactional boundaries around a test

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-381?page=com.atlassian.jira.plugin.sy... ] Bartosz Majsak commented on ARQ-381: ------------------------------------ I think this can be closed, as we have transaction-extension in place which fulfills this requirement. > Annotation to add transactional boundaries around a test > -------------------------------------------------------- > > Key: ARQ-381 > URL: https://issues.jboss.org/browse/ARQ-381 > Project: Arquillian > Issue Type: Feature Request > Reporter: David Allen > Assignee: David Allen > Priority: Minor > > Add a new annotation for test methods to indicate that the test framework should start a transaction before running @Before methods and the test itself, and to either commit or rollback the transaction after test completes and all @After methods. -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-897) ArchiveDeploymentExporter should export both archive and testable archive (if applicable)

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-897?page=com.atlassian.jira.plugin.sy... ] Bartosz Majsak reassigned ARQ-897: ---------------------------------- Assignee: Bartosz Majsak > ArchiveDeploymentExporter should export both archive and testable archive (if applicable) > ----------------------------------------------------------------------------------------- > > Key: ARQ-897 > URL: https://issues.jboss.org/browse/ARQ-897 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.0.0.Final > Reporter: Dan Allen > Assignee: Bartosz Majsak > Priority: Minor > Labels: starter > > The ArchiveDeploymentExporter should export both the archive and the testable archive (in the case they differ) for testable deployments. This enhancement simply makes it easier on the developer to > a) see the progression of the archive > b) see the contents of the original archive easier > Related source: > https://github.com/arquillian/arquillian-core/blob/master/container/impl-... -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1237) Warp: use PortProber to determine free ports for proxy

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-1237?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak reassigned ARQ-1237: ----------------------------------- Assignee: Bartosz Majsak > Warp: use PortProber to determine free ports for proxy > ------------------------------------------------------ > > Key: ARQ-1237 > URL: https://issues.jboss.org/browse/ARQ-1237 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha2 > Reporter: Lukáš Fryč > Assignee: Bartosz Majsak > Priority: Minor > Fix For: warp_1.0.0.Beta1 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Selenium 2 uses {{PortProber}} to check free ports to run Selenium Server on. > We can leverage that component too for Warp proxy and avoid conflicting ports. -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1143) Provide support for Groovy 2.0

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1143?page=com.atlassian.jira.plugin.s... ] Karel Piwko updated ARQ-1143: ----------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-testrunner-spock/pull/7 Now, which Groovy 2.1.4 it works fine. I've updated Spock to 0.7 as well. > Provide support for Groovy 2.0 > ------------------------------ > > Key: ARQ-1143 > URL: https://issues.jboss.org/browse/ARQ-1143 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Spock TestRunner > Affects Versions: spock_1.0.0.Alpha2 > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Fix For: spock_1.0.0.next > > > This might require changing dependency structure, hence Spock has two different versions as well. -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1384) Arquiliian Persistence TomEE support

by Tamás Kimmel (JIRA)

[ https://issues.jboss.org/browse/ARQ-1384?page=com.atlassian.jira.plugin.s... ] Tamás Kimmel updated ARQ-1384: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-extension-persistence/pull/33 > Arquiliian Persistence TomEE support > ------------------------------------ > > Key: ARQ-1384 > URL: https://issues.jboss.org/browse/ARQ-1384 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha6 > Reporter: Tamás Kimmel > Assignee: Bartosz Majsak > > It would be nice to have a TomEE test profile. > I've created one. > Running test on the modul i got 1 fail, and 2 errors. All others are green. > And (hopefully) i did not broke other profiles. > Please take a look at it. > https://github.com/kumm/arquillian-extension-persistence/commits/tomee -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1071) NullPointerException when timeout is set in @Test when using JUnit

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1071?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen closed ARQ-1071. ------------------------------ > NullPointerException when timeout is set in @Test when using JUnit > ------------------------------------------------------------------ > > Key: ARQ-1071 > URL: https://issues.jboss.org/browse/ARQ-1071 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.0.0.Final, 1.0.1.Final > Reporter: Rick-Rainer Ludwig > Fix For: 1.0.4.Final > > > When defining a timeout in @Test of JUnit Arquillian throws a NullPointerException: > {code} > java.lang.NullPointerException > at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263) > at org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOfTimeout.java:62) > {code} > The code to reproduce this: > {code} > import org.jboss.arquillian.junit.Arquillian; > import org.junit.Test; > import org.junit.runner.RunWith; > @RunWith(Arquillian.class) > public class TestTimeout { > @Test(timeout = 3000) > public void test() throws Exception { > Thread.sleep(1000); > } > } > {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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1287) arquillian-testng-standalone does not declare dependency on core impl in compile scope.

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1287?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen closed ARQ-1287. ------------------------------ > arquillian-testng-standalone does not declare dependency on core impl in compile scope. > --------------------------------------------------------------------------------------- > > Key: ARQ-1287 > URL: https://issues.jboss.org/browse/ARQ-1287 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Aliaksei Lahachou > Fix For: 1.0.4.Final > > > Unlike {{arquillian-junit-standalone}}, {{arquillian-testng-standalone}} does not declare dependency on core implementation ({{arquillian-core-impl-base}}, etc.) in compile scope. This leads to the problem, because user has to guess and specify dependencies these dependencies manually. -- 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

11 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues June 2013