July 2012 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-779) Seam2 Extension does not build on build server

by Aslak Knutsen (JIRA)

Aslak Knutsen created ARQ-779: --------------------------------- Summary: Seam2 Extension does not build on build server Key: ARQ-779 URL: https://issues.jboss.org/browse/ARQ-779 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Seam2 Affects Versions: seam2_1.0.0.Alpha2 Reporter: Aslak Knutsen Assignee: Bartosz Majsak Fix For: seam2_1.0.0.next https://arquillian.ci.cloudbees.com/job/Arquillian-Extension-Seam2/org.jb... The build server use a special settings.xml that is not picked up when using Resolver by default. Since Seam2 is not in Maven Central the jboss.org nexus repos can not be found when resolving. A build-server profile should be setup that can pass a settings.xml from commandline to the surefire process. Same with the maven.repo.local, see tomcat containers for example: https://github.com/arquillian/arquillian-container-tomcat/blob/master/pom... -- 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

11 years, 11 months

2
1
0 / 0

[JBoss JIRA] (ARQ-871) Consider calling Lifecycle.endCall after each test method

by Marek Schmidt (JIRA)

Marek Schmidt created ARQ-871: --------------------------------- Summary: Consider calling Lifecycle.endCall after each test method Key: ARQ-871 URL: https://issues.jboss.org/browse/ARQ-871 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Seam2 Affects Versions: seam2_1.0.0.Alpha2 Reporter: Marek Schmidt Assignee: Bartosz Majsak It would probably make sense to call Lifecycle.endCall after each test method, so we'd get fresh contexts. -- 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

11 years, 11 months

2
2
0 / 0

[JBoss JIRA] (ARQ-1012) org.junit.Assume API not working

by Karsten Ohme (JIRA)

Karsten Ohme created ARQ-1012: --------------------------------- Summary: org.junit.Assume API not working Key: ARQ-1012 URL: https://issues.jboss.org/browse/ARQ-1012 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Integration Test Suite Affects Versions: 1.0.0.Final Environment: Windows 7, Java 1.7 Reporter: Karsten Ohme Hi, my test classes are annotated with @RunWith(Arquillian.class) I try to use the newer JUnit org.junit.Assume API. The problem ist, that the outcome of the test seems to be ignored, e.g. org.junit.Assume.assertNonNull does not fail and throws an exception. -- 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

11 years, 11 months

2
2
0 / 0

[JBoss JIRA] (ARQ-620) arquillian-core-impl-base needs a non-optional dependency on jboss-logmanager

by Geoffrey De Smet (Created) (JIRA)

arquillian-core-impl-base needs a non-optional dependency on jboss-logmanager ----------------------------------------------------------------------------- Key: ARQ-620 URL: https://issues.jboss.org/browse/ARQ-620 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Geoffrey De Smet Priority: Optional Otherwise LoadableExtensionLoader fails with a ClassNotFoundException if you're deploying to jetty 6 for example (which doesn't have jboss-logging in it's classpath by default): {code} Could not load Logmanager "org.jboss.logmanager.LogManager" java.lang.ClassNotFoundException: org.jboss.logmanager.LogManager at java.net.URLClassLoader$1.run(URLClassLoader.java:202) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) at java.lang.ClassLoader.loadClass(ClassLoader.java:247) at java.util.logging.LogManager$1.run(LogManager.java:166) at java.security.AccessController.doPrivileged(Native Method) at java.util.logging.LogManager.<clinit>(LogManager.java:156) at java.util.logging.Logger.getLogger(Logger.java:287) at org.jboss.arquillian.core.impl.loadable.LoadableExtensionLoader.<clinit>(LoadableExtensionLoader.java:45) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:247) at org.jboss.arquillian.test.spi.SecurityActions.loadClass(SecurityActions.java:64) at org.jboss.arquillian.test.spi.TestRunnerAdaptorBuilder.build(TestRunnerAdaptorBuilder.java:49) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:72) at org.junit.runner.JUnitCore.run(JUnitCore.java:157) at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:71) at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:199) at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:62) 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 com.intellij.rt.execution.application.AppMain.main(AppMain.java:120) {code} -- 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

11 years, 11 months

2
3
0 / 0

[JBoss JIRA] (ARQ-639) Add ability to postpone initialization of non-managed deployments annotated @Deployment(managed=false)

by Dominik Pospisil (Created) (JIRA)

Add ability to postpone initialization of non-managed deployments annotated @Deployment(managed=false) ------------------------------------------------------------------------------------------------------ Key: ARQ-639 URL: https://issues.jboss.org/browse/ARQ-639 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 1.0.0.CR5 Reporter: Dominik Pospisil Currently deployments annotated using @Deployment(managed=false) are initialized prior to test case execution (EventTestRunnerAdaptor.beforeClass:80). Some test scenarios require that the initialization of the deployment is postponed until the actual deployment is performed using Deployer.deploy() call. It would be nice if the @Deploymnent(managed=false) method is called during Deployer.deploy() call by default or if there is an option to specify when the initialization should be performed. This way the content of the deployment may be constructed / updated during test case runtime using information which may not be available before test execution. -- 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

11 years, 11 months

6
6
0 / 0

[JBoss JIRA] (ARQ-726) Arq doc: Missing note about -Darquillian.xml=some-file-or-classpath-resource.xml

by Ondrej Zizka (JIRA)

Ondrej Zizka created ARQ-726: -------------------------------- Summary: Arq doc: Missing note about -Darquillian.xml=some-file-or-classpath-resource.xml Key: ARQ-726 URL: https://issues.jboss.org/browse/ARQ-726 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 1.0.0.CR5 Reporter: Ondrej Zizka Assignee: Aslak Knutsen Priority: Minor http://docs.jboss.org/arquillian/reference/latest/en-US/html_single/ 4.4. Container configuration Missing these information: * the -Darquillian.xml=... sys prop * that it can be a path on classpath or filesystem * which of the above takes precedence -- 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

11 years, 11 months

2
2
0 / 0

[JBoss JIRA] (ARQ-862) manual containers not to be stopped in AfterClass

by Radoslav Husar (JIRA)

Radoslav Husar created ARQ-862: ---------------------------------- Summary: manual containers not to be stopped in AfterClass Key: ARQ-862 URL: https://issues.jboss.org/browse/ARQ-862 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 1.0.0.CR8 Reporter: Radoslav Husar Currently, all containers with manually managed life-cycle are shutdown after class. This makes all tests run very long. The solution is to leave the container lifecycle handling to the user which has to deal with non-deterministic order of the test class execution him/herself but ARQ should still do the work for stopping the still running containers in @AfterSuite. -- 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

11 years, 11 months

2
2
0 / 0

[JBoss JIRA] (ARQ-905) Provide SPI for filtering tests

by Dan Allen (JIRA)

Dan Allen created ARQ-905: ----------------------------- Summary: Provide SPI for filtering tests Key: ARQ-905 URL: https://issues.jboss.org/browse/ARQ-905 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Dan Allen Provide an SPI (or observer hook) for filtering the test classes. There are many reasons to filter which tests are run: * execution speed * available environment (e.g., based on target container, based on access to shared resource) * permitted exclusions (like in a TCK) * user story * deliverable * demo * security (whether running the test is allowed) * ... We can't think of all of them. That's why we should over an SPI to allow these possibilities to be explored. Currently, test filtering (or selection) is handled in a few different ways: * suite definition * groups * test plugin includes/excludes (e.g., Maven surefire) While these options can handle many of the cases, they are still very limiting, esp since they are static declarations. Imagine long lists of test classes or brow-wrinkling include/exclude logic. Let's give the developers the choice of how they want to implement filtering. We can then provide some nice options in the way of extensions. For instance, imagine a rule-based test filter extension. You can write rules in the Drools DSL to decide which tests to execute. This is very powerful for user story-based development and even contract deliverables. The filter should be able to inject various parts of the Arquillian runtime, including: * Current test class being processed * Active container class and configuration * Test archive The filter should be able to invoke an "ignore" or "skip" method to instruct Arquillian to skip running the test. -- 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

11 years, 11 months

2
4
0 / 0

[JBoss JIRA] (ARQ-906) Provide SPI for container configuration activation

by Dan Allen (JIRA)

Dan Allen created ARQ-906: ----------------------------- Summary: Provide SPI for container configuration activation Key: ARQ-906 URL: https://issues.jboss.org/browse/ARQ-906 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Dan Allen Activing container configuration right now is a real pain. It requires the user to manually correlate the choice of container adapter with the choice of container configuration. I propose that we offer an SPI for container configuration activation. We can then provide some nice options in the way of extensions for doing container selection. For example, an extension could match the qualifier name to the package name of the container implementation to decide which configuration to activate. It could read a mapping file that the user provides. Or it could use a remote registry. Anything is possible once this aspect of Arquillian is pluggable. And it will take the burden of selecting a container configuration off the developer. -- 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

11 years, 11 months

2
1
0 / 0

[JBoss JIRA] (ARQ-920) Support @Deployment on non-public member (method or field)

by Dan Allen (JIRA)

Dan Allen created ARQ-920: ----------------------------- Summary: Support @Deployment on non-public member (method or field) Key: ARQ-920 URL: https://issues.jboss.org/browse/ARQ-920 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Dan Allen Priority: Minor I don't see a reason why we are forcing the @Deployment member (method or field) to be public. It's common to have non-public injection points, so it's reasonable to assume we can honor non-public members for defining a @Deployment as well. -- 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

11 years, 11 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues July 2012