July 2014 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-1815) Unable to locate Oracle Sequence filter

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-1815?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak updated ARQ-1815: -------------------------------- Summary: Unable to locate Oracle Sequence filter (was: Unable to locate Oracle Statement filter) > Unable to locate Oracle Sequence filter > --------------------------------------- > > Key: ARQ-1815 > URL: https://issues.jboss.org/browse/ARQ-1815 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha7 > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Priority: Blocker > Fix For: persistence_1.0.0.Alpha7 > > > When trying to define custom table filter using > {{<property name=“customTableFilter”>org.jboss.arquillian.persistence.dbunit.filter.OracleDatabaseSequenceFilterProvider</property>}} > It's resulting in > {{Unable to find sequence filter for org.jboss.arquillian.persistence.dbunit.filter.OracleDatabaseSequenceFilterProvider. Using default database sequence filter.}} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1815) Unable to locate Oracle Statement filter

by Bartosz Majsak (JIRA)

Bartosz Majsak created ARQ-1815: ----------------------------------- Summary: Unable to locate Oracle Statement filter Key: ARQ-1815 URL: https://issues.jboss.org/browse/ARQ-1815 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Persistence Affects Versions: persistence_1.0.0.Alpha7 Reporter: Bartosz Majsak Assignee: Bartosz Majsak Priority: Blocker Fix For: persistence_1.0.0.Alpha7 When trying to define custom table filter using {{<property name=“customTableFilter”>org.jboss.arquillian.persistence.dbunit.filter.OracleDatabaseSequenceFilterProvider</property>}} It's resulting in {{Unable to find sequence filter for org.jboss.arquillian.persistence.dbunit.filter.OracleDatabaseSequenceFilterProvider. Using default database sequence filter.}} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-197) Research support for @Deployment on multiple levels

by MINNA HU (JIRA)

[ https://issues.jboss.org/browse/ARQ-197?page=com.atlassian.jira.plugin.sy... ] MINNA HU commented on ARQ-197: ------------------------------ Hi [~kshantaraman], I am not the developer of arquillian-suite-extension, but I would like to answer your questions as I like this extension, and I'd like to promote it to more people, thank you~ Please see my comments inline. 1) Does each of my tests need to be in their own class? The extension does not affect the way of organizing your tests, for me, I have several test classes, and each test class contain several tests for each feature. 2) Does the Deployment class have to be separate? Yes, I created a separate class for deployments, and mark it as @ArquillianSuiteDeployment. 3) Does the plugin work Test Suites TESTNG tests? Yes, I am using TestNG tests. > Research support for @Deployment on multiple levels > --------------------------------------------------- > > Key: ARQ-197 > URL: https://issues.jboss.org/browse/ARQ-197 > Project: Arquillian > Issue Type: Feature Request > Components: Base Implementation > Reporter: Aslak Knutsen > Priority: Critical > Fix For: 2.0.0.CR1 > > > One deployment pr TestCase might not always be the ideal solution. Research how we can deploy multiple TestCases with one Deployment and test them all at once. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-197) Research support for @Deployment on multiple levels

by Karthik Shantaraman (JIRA)

[ https://issues.jboss.org/browse/ARQ-197?page=com.atlassian.jira.plugin.sy... ] Karthik Shantaraman edited comment on ARQ-197 at 7/8/14 1:46 PM: ----------------------------------------------------------------- Hi [~huangdihu], I have gone through that plugin and now am left with a couple of questions 1) Does each of my tests need to be in their own class? 2) Does the Deployment class have to be separate? 3) Does the plugin work Test Suites TESTNG tests? Thanks, Karthik was (Author: kshantaraman): Hi [~huangdihu]], I have gone through that plugin and now am left with a couple of questions 1) Does each of my tests need to be in their own class? 2) Does the Deployment class have to be separate? 3) Does the plugin work Test Suites TESTNG tests? Thanks, Karthik > Research support for @Deployment on multiple levels > --------------------------------------------------- > > Key: ARQ-197 > URL: https://issues.jboss.org/browse/ARQ-197 > Project: Arquillian > Issue Type: Feature Request > Components: Base Implementation > Reporter: Aslak Knutsen > Priority: Critical > Fix For: 2.0.0.CR1 > > > One deployment pr TestCase might not always be the ideal solution. Research how we can deploy multiple TestCases with one Deployment and test them all at once. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-197) Research support for @Deployment on multiple levels

by Karthik Shantaraman (JIRA)

[ https://issues.jboss.org/browse/ARQ-197?page=com.atlassian.jira.plugin.sy... ] Karthik Shantaraman commented on ARQ-197: ----------------------------------------- Hi [~huangdihu]], I have gone through that plugin and now am left with a couple of questions 1) Does each of my tests need to be in their own class? 2) Does the Deployment class have to be separate? 3) Does the plugin work Test Suites TESTNG tests? Thanks, Karthik > Research support for @Deployment on multiple levels > --------------------------------------------------- > > Key: ARQ-197 > URL: https://issues.jboss.org/browse/ARQ-197 > Project: Arquillian > Issue Type: Feature Request > Components: Base Implementation > Reporter: Aslak Knutsen > Priority: Critical > Fix For: 2.0.0.CR1 > > > One deployment pr TestCase might not always be the ideal solution. Research how we can deploy multiple TestCases with one Deployment and test them all at once. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-197) Research support for @Deployment on multiple levels

by MINNA HU (JIRA)

[ https://issues.jboss.org/browse/ARQ-197?page=com.atlassian.jira.plugin.sy... ] MINNA HU commented on ARQ-197: ------------------------------ [~kshantaraman]: try https://github.com/ingwarsw/arquillian-suite-extension, it works for me. Our full deployment will take 10 minutes to run, and we have 8 test classes right now, so at least arquillian-suite-extension saves us 7*10 minutes when it reuses the deployment for each test class. We will have more test classes in future, the improvement is dramatic. > Research support for @Deployment on multiple levels > --------------------------------------------------- > > Key: ARQ-197 > URL: https://issues.jboss.org/browse/ARQ-197 > Project: Arquillian > Issue Type: Feature Request > Components: Base Implementation > Reporter: Aslak Knutsen > Priority: Critical > Fix For: 2.0.0.CR1 > > > One deployment pr TestCase might not always be the ideal solution. Research how we can deploy multiple TestCases with one Deployment and test them all at once. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-567) Supporting Test Suites (@ArquillianSuite)

by Karthik Shantaraman (JIRA)

[ https://issues.jboss.org/browse/ARQ-567?page=com.atlassian.jira.plugin.sy... ] Karthik Shantaraman commented on ARQ-567: ----------------------------------------- Hi, Is there a way to run multiple tests with a single Deployment? > Supporting Test Suites (@ArquillianSuite) > ----------------------------------------- > > Key: ARQ-567 > URL: https://issues.jboss.org/browse/ARQ-567 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Mousavi Jahan Abadi S. M. > > Currently, it is supported that JUnit test cases being run by Arquillian. This feature request is request for supporting test suites too to be run by Arquillian too. Idea is like: > @RunWith(ArquillianSuite.class) > @Suite.SuiteClasses( { TestCase1.class, TestCase2.class, .... } ) > public class AllTests{ > @Deployment > public static JavaArchive createTestArchive(){ > return ShrinkWrap.create(JavaArchive.class,"test.jar"); > } > } > The advantages of above approach for users of Arquillian framework are: > - Test cases don't needed to be modified to have: "@RunWith(Arquillian.class)" annotation. In other words, test cases will be pure JUnit code, and no Arquillian code (results in less coding for end users). > - It is not necessary to include the static "@Deployment" methods in all test cases any more, and only Test Suite need to define the archieving/deployment related setting/definitions. > The advantage of above approach for framework itself is: > - From performance point-of-view, it becomes possible for Arquillian to deploy all test cases in the Test Suite into J2EE container in one action (one deploy/undeploy for one test suite, instead of mulitple deploy/undeploy for each test case). -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-197) Research support for @Deployment on multiple levels

by Karthik Shantaraman (JIRA)

[ https://issues.jboss.org/browse/ARQ-197?page=com.atlassian.jira.plugin.sy... ] Karthik Shantaraman commented on ARQ-197: ----------------------------------------- Hi, Is there a way to run multiple tests with a single Deployment? > Research support for @Deployment on multiple levels > --------------------------------------------------- > > Key: ARQ-197 > URL: https://issues.jboss.org/browse/ARQ-197 > Project: Arquillian > Issue Type: Feature Request > Components: Base Implementation > Reporter: Aslak Knutsen > Priority: Critical > Fix For: 2.0.0.CR1 > > > One deployment pr TestCase might not always be the ideal solution. Research how we can deploy multiple TestCases with one Deployment and test them all at once. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1814) TomcatManagedConfiguration validates catalinaBase too soon

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1814?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen updated ARQ-1814: ------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: tomcat_1.0.0.Final Resolution: Done pushed upstream; https://github.com/arquillian/arquillian-container-tomcat/commit/b44ff17a... > TomcatManagedConfiguration validates catalinaBase too soon > ---------------------------------------------------------- > > Key: ARQ-1814 > URL: https://issues.jboss.org/browse/ARQ-1814 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: tomcat_1.0.0.CR7 > Reporter: Brett Meyer > Fix For: tomcat_1.0.0.Final > > > CATALINA_BASE is only necessary if you're running multiple instances of Tomcat on a single host. If only one instance is running, CATALINA_BASE==CATALINA_HOME. > When catalinaBase is not set in arquillian.xml (tomcat 7 managed container), you get the following NPE. TomcatManagedContainer could probably assume CATALINA_BASE==CATALINA_HOME if CATALINA_BASE is not explicitly set. > {code} > org.jboss.arquillian.container.spi.client.container.LifecycleException: Could not start container > at org.jboss.arquillian.container.tomcat.managed_7.TomcatManagedContainer.start(TomcatManagedContainer.java:177) > at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:199) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156) > 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.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > 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.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) > 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.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:77) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:70) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forEachSuiteContainer(ContainerLifecycleController.java:221) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startSuiteContainers(ContainerLifecycleController.java:69) > 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.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > 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.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:86) > 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.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > 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.createSuiteContext(TestContextHandler.java:60) > 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.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeSuite(EventTestRunnerAdaptor.java:68) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:97) > at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:35) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:146) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:97) > 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.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103) > at com.sun.proxy.$Proxy0.invoke(Unknown Source) > at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:145) > at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:87) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69) > Caused by: java.lang.NullPointerException > at java.io.File.<init>(File.java:251) > at org.jboss.arquillian.container.tomcat.managed_7.TomcatManagedContainer.start(TomcatManagedContainer.java:105) > ... 67 more > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-600) Improve Tomcat codebase - Managed

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-600?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen updated ARQ-600: ------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done pushed upstream https://github.com/arquillian/arquillian-container-tomcat/commit/8a91b971... > Improve Tomcat codebase - Managed > --------------------------------- > > Key: ARQ-600 > URL: https://issues.jboss.org/browse/ARQ-600 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Reporter: Aslak Knutsen > Assignee: Stephen Coy > Fix For: tomcat_1.0.0.Final > > > After the Tomcat Container code clean up, tomcat-common, it seems all the Managed Tomcat containers are identical both in impl and configuration. > We can create a similar tomcat-common-managed that will have the common parts between the different versions. > {note} > If Tomcat Managed 5.5, 6 and 7 are identical, why do we have 3 versions? > {note} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues July 2014