Folks, the initial work on consolidating the arquillian test infrastructure (AS7-734 <https://issues.jboss.org/browse/AS7-734>) is done. What you see in pull request 49 <https://github.com/jbossas/jboss-as/pull/49> installs the latest arquillian 1.0.0.Beta2 release to use with all test suites. These are testsuite + smoke + spec + integration

On 06/09/2011 06:52 AM, Jaikiran Pai wrote: > Should the testsuite2 (and everything under it) be deleted now? Or will > it continue to stay - it has additionally "api" and "internals" modules. > Where should new tests go? I am also interested in this, I am just about to write a bunch of spec tests and would like to know where to place them. Incidentally after my latest rebase InteliJ now correctly identified testsuite/smoke as a valid Maven artefact and processes the source correctly, the other modules are not currently recognised so InteliJ does not handle the source correctly.

Should the testsuite2 (and everything under it) be deleted now?

On Thursday 09 June 2011 12:25 AM, Thomas Diesler wrote: > Folks, > > the initial work on consolidating the arquillian test infrastructure > (AS7-734<https://issues.jboss.org/browse/AS7-734>) is done. > > What you see in pull request 49 > <https://github.com/jbossas/jboss-as/pull/49> installs the latest > arquillian 1.0.0.Beta2 release to use with all test suites. These are > > testsuite > + smoke > + spec > + integration Should the testsuite2 (and everything under it) be deleted now? Or will it continue to stay - it has additionally "api" and "internals" modules. Where should new tests go? -Jaikiran _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

Done, pls pull https://github.com/jbossas/jboss-as/pull/51 On 06/10/2011 08:27 AM, Thomas Diesler wrote: > > Should the testsuite2 (and everything under it) be deleted now? > > yes, this should be deleted - I follow up > > On 06/09/2011 07:52 AM, Jaikiran Pai wrote: >> On Thursday 09 June 2011 12:25 AM, Thomas Diesler wrote: >>> Folks, >>> >>> the initial work on consolidating the arquillian test infrastructure >>> (AS7-734<https://issues.jboss.org/browse/AS7-734>) is done. >>> >>> What you see in pull request 49 >>> <https://github.com/jbossas/jboss-as/pull/49> installs the latest >>> arquillian 1.0.0.Beta2 release to use with all test suites. These are >>> >>> testsuite >>> + smoke >>> + spec >>> + integration >> Should the testsuite2 (and everything under it) be deleted now? Or will >> it continue to stay - it has additionally "api" and "internals" >> modules. >> Where should new tests go? >> >> -Jaikiran >> _______________________________________________ >> jboss-as7-dev mailing list >> jboss-as7-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

this would be a mistake, I thought I moved all the stuff - let me check - maybe there was an overlap On 06/10/2011 12:15 PM, Jaikiran Pai wrote: > Hi Thomas, > > I don't see that those tests have been moved to the new "testsuite" > location. We'll first have to move them to the new location and then > delete the testsuite2/ stuff. > > -Jaikiran > On Friday 10 June 2011 01:15 PM, Thomas Diesler wrote: >> Done, pls pull >> >> https://github.com/jbossas/jboss-as/pull/51 >> >> On 06/10/2011 08:27 AM, Thomas Diesler wrote: >>>> Should the testsuite2 (and everything under it) be deleted now? >>> yes, this should be deleted - I follow up >>> >>> On 06/09/2011 07:52 AM, Jaikiran Pai wrote: >>>> On Thursday 09 June 2011 12:25 AM, Thomas Diesler wrote: >>>>> Folks, >>>>> >>>>> the initial work on consolidating the arquillian test infrastructure >>>>> (AS7-734<https://issues.jboss.org/browse/AS7-734>) is done. >>>>> >>>>> What you see in pull request 49 >>>>> <https://github.com/jbossas/jboss-as/pull/49> installs the latest >>>>> arquillian 1.0.0.Beta2 release to use with all test suites. These are >>>>> >>>>> testsuite >>>>> + smoke >>>>> + spec >>>>> + integration >>>> Should the testsuite2 (and everything under it) be deleted now? Or >>>> will >>>> it continue to stay - it has additionally "api" and "internals" >>>> modules. >>>> Where should new tests go? >>>> >>>> -Jaikiran >>>> _______________________________________________ >>>> jboss-as7-dev mailing list >>>> jboss-as7-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

Folks, the initial work on consolidating the arquillian test infrastructure (AS7-734 <https://issues.jboss.org/browse/AS7-734>) is done. What you see in pull request 49 <https://github.com/jbossas/jboss-as/pull/49> installs the latest arquillian 1.0.0.Beta2 release to use with all test suites. These are testsuite + smoke + spec + integration The AS7 instance is started in managed mode (i.e. in a separate VM). There is no arquillian subsystem any more nor any test related jar artefacts in modules. Instead the arquillian endpoint is deployed before the first test. As a side effect of arq managed it is also possible to manually start up an AS7 instance and run the tests as usual. This is useful for in container debugging. The maven test goal works as expected. You can run individual tests with -Dtest=Foo For this iteration, the focus was on infrastructure not on individual test failures. All tests were ported to the new arquillian API. Tests that failed for obvious reasons were fixed the hard ones ignored. To see which tests were ignored run > git grep AS7-734 Attached is a snapshot of the ignored tests. I'll take care of the osgi ones. For the others I'd like to ask the respective authors to have a look. JSF testing is currently disabled completely because of its dependency on the arquillian servlet protocol. I'll follow up with the JSF folks so we can decide how to resurrect those. Overall writing integration tests should now be much easier. cheers -thomas - xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler JBoss OSGi Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

Yes, it should work. I haven't really looked at your pastebin, just saying that it's supposed to work. On 6/9/11 8:21 AM, Scott Marlow wrote: > Should "mvn clean install -DallTests" in as7/testsuite work? > > I'm getting http://pastebin.com/21RNcB9x > > > On 06/08/2011 02:55 PM, Thomas Diesler wrote: >> Folks, >> >> the initial work on consolidating the arquillian test infrastructure >> (AS7-734<https://issues.jboss.org/browse/AS7-734>) is done. >> >> What you see in pull request 49 >> <https://github.com/jbossas/jboss-as/pull/49> installs the latest >> arquillian 1.0.0.Beta2 release to use with all test suites. These are >> >> testsuite >> + smoke >> + spec >> + integration >> >> The AS7 instance is started in managed mode (i.e. in a separate VM). >> There is no arquillian subsystem any more nor any test related jar >> artefacts in modules. Instead the arquillian endpoint is deployed before >> the first test. As a side effect of arq managed it is also possible to >> manually start up an AS7 instance and run the tests as usual. This is >> useful for in container debugging. The maven test goal works as >> expected. You can run individual tests with -Dtest=Foo >> >> For this iteration, the focus was on infrastructure not on individual >> test failures. All tests were ported to the new arquillian API. Tests >> that failed for obvious reasons were fixed the hard ones ignored. >> >> To see which tests were ignored run >> >> > git grep AS7-734 >> >> Attached is a snapshot of the ignored tests. I'll take care of the osgi >> ones. For the others I'd like to ask the respective authors to have a look. >> >> JSF testing is currently disabled completely because of its dependency >> on the arquillian servlet protocol. I'll follow up with the JSF folks so >> we can decide how to resurrect those. >> >> Overall writing integration tests should now be much easier. >> >> cheers >> -thomas >> - >> >> xxxxxxxxxxxxxxxxxxxxxxxxxxxx >> Thomas Diesler >> JBoss OSGi Lead >> JBoss, a division of Red Hat >> xxxxxxxxxxxxxxxxxxxxxxxxxxxx >> >> >> >> >> _______________________________________________ >> jboss-as7-dev mailing list >> jboss-as7-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev > > _______________________________________________ > jboss-as7-dev mailing list > jboss-as7-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

If I build in as7/demos first, I get further but still get a lot of build errors. http://pastebin.com/rzUKUxZg On 06/09/2011 11:12 AM, Scott Marlow wrote: > I get: > > [ERROR] Failed to execute goal on project jboss-as-testsuite-smoke: > Could not resolve dependencies for project > org.jboss.as:jboss-as-testsuite-smoke:jar:7.0.0.Beta4-SNAPSHOT: The > following artifacts could not be resolved: > org.jboss.as:jboss-as-demos-legacy:jar:7.0.0.Beta4-SNAPSHOT, > org.jboss.as:jboss-as-demos-internals:jar:7.0.0.Beta4-SNAPSHOT: Failure > to find org.jboss.as:jboss-as-demos-legacy:jar:7.0.0.Beta4-SNAPSHOT in > https://repository.jboss.org/nexus/content/groups/public/ was cached in > the local repository, resolution will not be reattempted until the > update interval of jboss-public-repository-group has elapsed or updates > are forced -> [Help 1] > > > > On 06/09/2011 10:56 AM, Brian Stansberry wrote: >> Yes, it should work. >> >> I haven't really looked at your pastebin, just saying that it's supposed >> to work. >> >> On 6/9/11 8:21 AM, Scott Marlow wrote: >>> Should "mvn clean install -DallTests" in as7/testsuite work? >>> >>> I'm getting http://pastebin.com/21RNcB9x >>> >>> >>> On 06/08/2011 02:55 PM, Thomas Diesler wrote: >>>> Folks, >>>> >>>> the initial work on consolidating the arquillian test infrastructure >>>> (AS7-734<https://issues.jboss.org/browse/AS7-734>) is done. >>>> >>>> What you see in pull request 49 >>>> <https://github.com/jbossas/jboss-as/pull/49> installs the latest >>>> arquillian 1.0.0.Beta2 release to use with all test suites. These are >>>> >>>> testsuite >>>> + smoke >>>> + spec >>>> + integration >>>> >>>> The AS7 instance is started in managed mode (i.e. in a separate VM). >>>> There is no arquillian subsystem any more nor any test related jar >>>> artefacts in modules. Instead the arquillian endpoint is deployed before >>>> the first test. As a side effect of arq managed it is also possible to >>>> manually start up an AS7 instance and run the tests as usual. This is >>>> useful for in container debugging. The maven test goal works as >>>> expected. You can run individual tests with -Dtest=Foo >>>> >>>> For this iteration, the focus was on infrastructure not on individual >>>> test failures. All tests were ported to the new arquillian API. Tests >>>> that failed for obvious reasons were fixed the hard ones ignored. >>>> >>>> To see which tests were ignored run >>>> >>>> > git grep AS7-734 >>>> >>>> Attached is a snapshot of the ignored tests. I'll take care of the osgi >>>> ones. For the others I'd like to ask the respective authors to have a look. >>>> >>>> JSF testing is currently disabled completely because of its dependency >>>> on the arquillian servlet protocol. I'll follow up with the JSF folks so >>>> we can decide how to resurrect those. >>>> >>>> Overall writing integration tests should now be much easier. >>>> >>>> cheers >>>> -thomas >>>> - >>>> >>>> xxxxxxxxxxxxxxxxxxxxxxxxxxxx >>>> Thomas Diesler >>>> JBoss OSGi Lead >>>> JBoss, a division of Red Hat >>>> xxxxxxxxxxxxxxxxxxxxxxxxxxxx >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> jboss-as7-dev mailing list >>>> jboss-as7-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev >>> >>> _______________________________________________ >>> jboss-as7-dev mailing list >>> jboss-as7-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev >> >> > > _______________________________________________ > jboss-as7-dev mailing list > jboss-as7-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-as7-dev _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

Folks, the initial work on consolidating the arquillian test infrastructure (AS7-734 <https://issues.jboss.org/browse/AS7-734>) is done. What you see in pull request 49 <https://github.com/jbossas/jboss-as/pull/49> installs the latest arquillian 1.0.0.Beta2 release to use with all test suites. These are testsuite + smoke + spec + integration The AS7 instance is started in managed mode (i.e. in a separate VM). There is no arquillian subsystem any more nor any test related jar artefacts in modules. Instead the arquillian endpoint is deployed before the first test. As a side effect of arq managed it is also possible to manually start up an AS7 instance and run the tests as usual. This is useful for in container debugging. The maven test goal works as expected. You can run individual tests with -Dtest=Foo For this iteration, the focus was on infrastructure not on individual test failures. All tests were ported to the new arquillian API. Tests that failed for obvious reasons were fixed the hard ones ignored. To see which tests were ignored run > git grep AS7-734 Attached is a snapshot of the ignored tests. I'll take care of the osgi ones. For the others I'd like to ask the respective authors to have a look. JSF testing is currently disabled completely because of its dependency on the arquillian servlet protocol. I'll follow up with the JSF folks so we can decide how to resurrect those. Overall writing integration tests should now be much easier. cheers -thomas - xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler JBoss OSGi Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

I follow up on this On 06/10/2011 04:59 AM, Scott Marlow wrote: > I tried enabling one of the failing jpa tests > (testsuite/spec/src/test/java/org/jboss/as/test/spec/jpa/MultiplePuTestCase.java) > > and get this in server.log (http://pastie.org/2045779 for full details): > > " > > jboss.deployment.unit."MultiplePuTestCase.jar".INSTALL: Failed to > process phase INSTALL of deployment "MultiplePuTestCase.jar" > ... > Caused by: java.lang.RuntimeException: Error getting reflective > information for class class > org.jboss.as.test.spec.jpa.MultiplePuTestCase > ... > Caused by: java.lang.NoClassDefFoundError: > org/jboss/shrinkwrap/api/asset/Asset > ... > Caused by: java.lang.ClassNotFoundException: > org.jboss.shrinkwrap.api.asset.Asset from [Module > "deployment.MultiplePuTestCase.jar:main" from Service Module Loader] > " > > Does this likely mean an error in the test itself? Or elsewhere? > > > On 06/08/2011 02:55 PM, Thomas Diesler wrote: >> Folks, >> >> the initial work on consolidating the arquillian test infrastructure >> (AS7-734<https://issues.jboss.org/browse/AS7-734>) is done. >> >> What you see in pull request 49 >> <https://github.com/jbossas/jboss-as/pull/49> installs the latest >> arquillian 1.0.0.Beta2 release to use with all test suites. These are >> >> testsuite >> + smoke >> + spec >> + integration >> >> The AS7 instance is started in managed mode (i.e. in a separate VM). >> There is no arquillian subsystem any more nor any test related jar >> artefacts in modules. Instead the arquillian endpoint is deployed >> before >> the first test. As a side effect of arq managed it is also possible to >> manually start up an AS7 instance and run the tests as usual. This is >> useful for in container debugging. The maven test goal works as >> expected. You can run individual tests with -Dtest=Foo >> >> For this iteration, the focus was on infrastructure not on individual >> test failures. All tests were ported to the new arquillian API. Tests >> that failed for obvious reasons were fixed the hard ones ignored. >> >> To see which tests were ignored run >> >> > git grep AS7-734 >> >> Attached is a snapshot of the ignored tests. I'll take care of the osgi >> ones. For the others I'd like to ask the respective authors to have >> a look. >> >> JSF testing is currently disabled completely because of its dependency >> on the arquillian servlet protocol. I'll follow up with the JSF >> folks so >> we can decide how to resurrect those. >> >> Overall writing integration tests should now be much easier. >> >> cheers >> -thomas >> - >> >> xxxxxxxxxxxxxxxxxxxxxxxxxxxx >> Thomas Diesler >> JBoss OSGi Lead >> JBoss, a division of Red Hat >> xxxxxxxxxxxxxxxxxxxxxxxxxxxx >> >> >> >> >> _______________________________________________ >> jboss-as7-dev mailing list >> jboss-as7-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev > _______________________________________________ > jboss-as7-dev mailing list > jboss-as7-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-as7-dev