April 2011 - arquillian-issues - Jboss List Archives

[JBoss JIRA] Created: (ARQ-232) Redesign Servlet protocol to be more human friendly

by Aslak Knutsen (JIRA)

Redesign Servlet protocol to be more human friendly --------------------------------------------------- Key: ARQ-232 URL: https://jira.jboss.org/browse/ARQ-232 Project: Arquillian Issue Type: Feature Request Components: Test Protocol SPIs and Implementation Reporter: Aslak Knutsen Priority: Minor We should redesign the Servlet communication protocol to be more Rest api like. This will make it easier for humans to execute tests outside of the Arquillian Client and opens for other clients to communicate with the test. http://arquillian.pastebin.com/XHsfaycJ Add support for html output -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (ARQ-141) Add option to export the generated Archive to inspect the final deployment

by Aslak Knutsen (JIRA)

Add option to export the generated Archive to inspect the final deployment -------------------------------------------------------------------------- Key: ARQ-141 URL: https://jira.jboss.org/browse/ARQ-141 Project: Arquillian Issue Type: Task Components: Configuration, Documentation Reporter: Aslak Knutsen It is useful for debugging to have Arquillian export the Archive it is about to deploy, specially in IN_CONTAINER mode. Create a ArchiveExporter EventHandler on class level and make the export folder configurable. If option is not set: don't export -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

4
10
0 / 0

[JBoss JIRA] Created: (ARQ-350) Map client events 1 to 1 with container events

by Aslak Knutsen (JIRA)

Map client events 1 to 1 with container events ---------------------------------------------- Key: ARQ-350 URL: https://issues.jboss.org/browse/ARQ-350 Project: Arquillian Issue Type: Feature Request Components: Base Implementation, Test Protocol SPIs and Implementation Reporter: Aslak Knutsen We should redo how the test execution lifecycles happen. In the current impl the flow is: Client(BeforSuite, BeforeClass, Before) -> Container(BeforSuite, BeforeClass, Before, Test, After, AfterClass, AfterSuite) -> Client(After, AfterClass, AfterSuite) We should map these 1 to 1 with the incontainer execution and keep the test instance alive between the calls. Client(BeforeClass) -> Container(BeforeClass) Client(Before) -> Container(Before) .. This way the execution is closer to how it normally would be, and extensions can interact with the Container/Environment or Client in the appropriate lifecycles more naturally. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (ARQ-271) TestEnricher should be called in @BeforeClass as well

by Thomas Diesler (JIRA)

TestEnricher should be called in @BeforeClass as well ----------------------------------------------------- Key: ARQ-271 URL: https://jira.jboss.org/browse/ARQ-271 Project: Arquillian Issue Type: Feature Request Reporter: Thomas Diesler The TestEnricher API could be extended such that static fields can be initialized. @Inject public static BundleContext context; @BeforeClass public static void beforeClass() { System.out.println("BeforeClass: " + context); } There would be two calls to TestEnricher. #1 After test class load, but before a call to @BeforeClass. #2 After instantiation of the test class, but before a call to @Before (#2 is the current behaviour) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

4
10
0 / 0

[JBoss JIRA] Created: (ARQ-417) Support maven deployments

by Adrian Cole (JIRA)

Support maven deployments ------------------------- Key: ARQ-417 URL: https://issues.jboss.org/browse/ARQ-417 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Configuration Reporter: Adrian Cole Microdeployments via ShrinkWrap are a nimble deployment mechanism that allows developers to test bytecode skipping the build. Another usecase is to have ARQ in a CI loop, testing artifacts post-deploy. For this sort of scenario, it would be useful to reuse test cases from the microdeployments, but have them leveraged against code pulled from maven artifacts published in a prior step. For example, we could have an @Maven annotation which could define the coordinates of an ear file, and place that on a test scenario that performs the war, ejb, cdi, etc tests of from the dependent modules. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

4
8
0 / 0

[JBoss JIRA] Created: (ARQ-250) Add Mobicents Sip Servlets container

by jean deruelle (JIRA)

Add Mobicents Sip Servlets container ------------------------------------ Key: ARQ-250 URL: https://jira.jboss.org/browse/ARQ-250 Project: Arquillian Issue Type: Feature Request Reporter: jean deruelle Priority: Optional Fix For: 1.0.0.Alpha4 Need to add a Mobicents container based on the currently existing Tomcat container so that the Mobicents Sip Servlets testsuite can move to arquillian. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
7
0 / 0

[JBoss JIRA] Created: (ARQ-322) Implement a GlassFish 3 managed container

by Dan Allen (JIRA)

Implement a GlassFish 3 managed container ----------------------------------------- Key: ARQ-322 URL: https://jira.jboss.org/browse/ARQ-322 Project: Arquillian Issue Type: Feature Request Components: GlassFish Containers Affects Versions: 1.0.0.Alpha4 Reporter: Dan Allen Priority: Minor To round out the GlassFish support, we need a managed container (see the JBoss AS managed container). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
30
0 / 0

[JBoss JIRA] Created: (ARQ-184) NPE in o.j.aop.Dispatcher.invoke:117 - ARQ Alpha2 + remote-50 + as-client 5.0.1

by Ondrej Žižka (JIRA)

NPE in o.j.aop.Dispatcher.invoke:117 - ARQ Alpha2 + remote-50 + as-client 5.0.1 ------------------------------------------------------------------------------- Key: ARQ-184 URL: https://jira.jboss.org/browse/ARQ-184 Project: Arquillian Issue Type: Bug Environment: ARQ Alpha2 + remote-50 + as-client 5.0.1 + EAP 5.0.1 Reporter: Ondrej Žižka STR: 1) Download the project attached, 2) Run EAP 5.0.1 default, but I think the request doesn't even get sent. 3) mvn clean install (profile is self-enabled), 4) You'll get a NPE: org.jboss.arquillian.impl.event.FiredEventException: org.jboss.arquillian.spi.LifecycleException: Could not connect to container at org.jboss.arquillian.impl.event.MapEventManager.fire(MapEventManager.java:68) at org.jboss.arquillian.impl.context.AbstractEventContext.fire(AbstractEventContext.java:115) at org.jboss.arquillian.impl.EventTestRunnerAdaptor.beforeSuite(EventTestRunnerAdaptor.java:62) at org.jboss.arquillian.junit.Arquillian.<init>(Arquillian.java:71) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:31) at org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:24) at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:57) at org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:29) at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:57) at org.junit.internal.requests.ClassRequest.getRunner(ClassRequest.java:24) at org.apache.maven.surefire.junit4.JUnit4TestSet.<init>(JUnit4TestSet.java:45) at org.apache.maven.surefire.junit4.JUnit4DirectoryTestSuite.createTestSet(JUnit4DirectoryTestSuite.java:56) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.locateTestSets(AbstractDirectoryTestSuite.java:96) at org.apache.maven.surefire.Surefire.createSuiteFromDefinition(Surefire.java:209) at org.apache.maven.surefire.Surefire.run(Surefire.java:156) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009) Caused by: org.jboss.arquillian.spi.LifecycleException: Could not connect to container at org.jboss.arquillian.jbossas.remote50.JBossASRemoteContainer.start(JBossASRemoteContainer.java:89) at org.jboss.arquillian.impl.handler.ContainerStarter.callback(ContainerStarter.java:52) at org.jboss.arquillian.impl.handler.ContainerStarter.callback(ContainerStarter.java:41) at org.jboss.arquillian.impl.event.MapEventManager.fire(MapEventManager.java:63) ... 24 more Caused by: java.lang.NullPointerException at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:117) at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.invoke(AbstractDeployHandler.java:210) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:897) at org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:768) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:721) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:548) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:234) at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:206) at org.jboss.remoting.Client.invoke(Client.java:1708) at org.jboss.remoting.Client.invoke(Client.java:612) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at AOPProxy$1.loadProfile(AOPProxy$1.java) at org.jboss.arquillian.jbossas.remote50.JBossASRemoteContainer.initDeploymentManager(JBossASRemoteContainer.java:222) at org.jboss.arquillian.jbossas.remote50.JBossASRemoteContainer.start(JBossASRemoteContainer.java:85) at org.jboss.arquillian.impl.handler.ContainerStarter.callback(ContainerStarter.java:52) at org.jboss.arquillian.impl.handler.ContainerStarter.callback(ContainerStarter.java:41) at org.jboss.arquillian.impl.event.MapEventManager.fire(MapEventManager.java:63) at org.jboss.arquillian.impl.context.AbstractEventContext.fire(AbstractEventContext.java:115) at org.jboss.arquillian.impl.EventTestRunnerAdaptor.beforeSuite(EventTestRunnerAdaptor.java:62) at org.jboss.arquillian.junit.Arquillian.<init>(Arquillian.java:71) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:31) at org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:24) at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:57) at org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:29) at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:57) at org.junit.internal.requests.ClassRequest.getRunner(ClassRequest.java:24) at org.apache.maven.surefire.junit4.JUnit4TestSet.<init>(JUnit4TestSet.java:45) at org.apache.maven.surefire.junit4.JUnit4DirectoryTestSuite.createTestSet(JUnit4DirectoryTestSuite.java:56) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.locateTestSets(AbstractDirectoryTestSuite.java:96) at org.apache.maven.surefire.Surefire.createSuiteFromDefinition(Surefire.java:209) at org.apache.maven.surefire.Surefire.run(Surefire.java:156) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:72) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at AOPProxy$1.loadProfile(AOPProxy$1.java) at org.jboss.arquillian.jbossas.remote50.JBossASRemoteContainer.initDeploymentManager(JBossASRemoteContainer.java:222) at org.jboss.arquillian.jbossas.remote50.JBossASRemoteContainer.start(JBossASRemoteContainer.java:85) ... 27 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

6
12
0 / 0

[JBoss JIRA] Created: (ARQ-131) Include utility base class to simplify JPA testing

by Paul Bakker (JIRA)

Include utility base class to simplify JPA testing -------------------------------------------------- Key: ARQ-131 URL: https://jira.jboss.org/jira/browse/ARQ-131 Project: Arquillian Issue Type: Feature Request Components: Test Harness Integration Reporter: Paul Bakker Priority: Minor Two things are often needed when testing JPA code: -1 Counting rows in a table -2 Rolling back the transaction after each test (to speed up test execution, while potentially dangerous) To simplify testing it would be good to have a set of base classes that implement this common functionality. Test class can extend a base class when this kind of functionality is required. The Spring framework has excellent support for this and can be used for inspiration: http://static.springsource.org/spring/docs/3.0.x/spring-framework-referen... I included some example code that I wrote myself to get a feel how difficult it would be to implement. The code uses an embedded container using the EJB 3.1 API, but should off course integrate with Arquillian. By default each testcase runs in a transaction (using the usertransaction) and is rolled back at the end of the test, unless the testcase is annotated @TransactionAttribute(TransactionAttributeType.NOT_SUPPORTED). The rollback behavior can be changed with the custom @RollbackAfterTest anotation. I would be happy to help implementing this feature. -- 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

12 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (ARQ-413) Investigate possibility of reusing RHQ plugins to implement managed containers.

by Ondrej Zizka (JIRA)

Investigate possibility of reusing RHQ plugins to implement managed containers. ------------------------------------------------------------------------------- Key: ARQ-413 URL: https://issues.jboss.org/browse/ARQ-413 Project: Arquillian Issue Type: Task Security Level: Public (Everyone can see) Reporter: Ondrej Zizka Assignee: Ondrej Zizka (01:23:17) OndejZizka: aslak: One more thing, do you know RHQ project? (01:23:25) aslak: OndejZizka, yea? (01:23:50) OndejZizka: Well then you probably know that it has plugins for many containers (01:24:06) OndejZizka: So I thought, this could be re-used to make managed contaiers (01:24:26) aslak: hmm.. possible (01:24:27) OndejZizka: Basically, they have all it needs - starting, stopping, deploy/undeploy, config (01:24:34) OndejZizka: + some extras where possible (01:25:01) aslak: OndejZizka, got a url for source? (01:25:05) OndejZizka: Sure, sec (01:25:08) aslak: container source (01:25:21) OndejZizka: aslak: http://git.fedorahosted.org/git/?p=rhq/rhq.git; (01:26:00) OndejZizka: aslak: The source is vast. Not easy to locate concrete functionality, but plugins are separated as modules (01:37:52) jshaughn: ozizka-here: The CLI speaks only to the server (01:38:12) jshaughn: The only thing that comes close perhaps to what you're asking is the standalone plugin container jsanda_afk jshaughn (01:38:30) ozizka-here: jshaughn: Sounds promising, continue pls :) (01:38:36) jshaughn: this is a tool that is typically used to help rapid devleopment of plugins (01:39:14) jshaughn: it allows a plugin to basically run and gives a command line interface for executing its implementd factes (01:39:24) jshaughn: sorry, "facets" (01:39:42) jshaughn: I actually have not used it but let me see if I can track down a link (01:40:17) jshaughn: Heiko (pilhuhn) is the implementor and resident expert. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues April 2011