[jboss-as7-dev] Testsuite changes
Ondřej Žižka
ozizka at redhat.com
Fri Nov 25 16:08:42 EST 2011
Kabir Khan píše v Pá 25. 11. 2011 v 18:29 +0000:
> I have some work in progress in my branch at: https://github.com/kabir/jboss-as/commits/rework-testsuite
>
> I have pushed all the testsuite/integration classes into sub modules, and renamed group-smoke -> smoke etc.
That's basically what I planned as a next step after merging.
> There are still a few scripts and xslt hanging around in the testsuite/integration aggregator. I have not investigated their usage.
Ant scripts and XSLT serve to copy AS around and to change
configuration. Can be shared by multiple sub-modules, so I'd recommend
keeping it in integration/ .
> From what I can see the pom2.xml files are not being used, so I've made no attempt to update those.
Yes, that's something to remove, I had it there to compare old & new
harness - regressions and sets of tests run.
> There are some TODOs in the pom's where I am not sure about stuff. I
I'll do / clean up the TODOs next week.
> did not change the pom2.xml files, I'm not sure they are being used?
Nope.
>
> Broken stuff:
> It is impossible to run a single test from Eclipse, the arquillian.xml file is not found in Eclipse. Probably because this from testsuite/pom.xml does not get added to Eclipse's classpath:
> <additionalClasspathElements combine.children="append">
> <additionalClasspathElement>${basedir}/src/test/config/arq</additionalClasspathElement>
> </additionalClasspathElements>
I'll check that.
> so I think we should move these back to the resources directory.
> Thomas does not like -DallTests running benchmark and stress, what would a good system property name be to enable running those?
> We need to reenable the -DskipTests=true we had before
> Rather than using xslt to modify the port offsets, we should change the socket bindings to use port-offset="${jboss.port.offset:0}" so that we can just pass a system property.
>
> I won't be around much this weekend, so there is minimum chance of me crashing with you if any of you decide to do anything. However, please make your changes public somewhere so I can pick them up if I feel the urge.
>
>
> On 25 Nov 2011, at 13:56, Kabir Khan wrote:
>
> > I have pushed Ondrej's work, and here is how to run it for developers (summarized from another mail from a few days ago):
> >>
> >> mvn clean install
> >> -> runs smoke tests as expected
> >> --
> >>
> >> mvn clean install -DallTests
> >> -> runs all tests as expected
> >> --
> >>
> >> mvn clean install -DallTests=true
> >> -> runs all tests as expected
> >> --
> >>
> >> mvn install -pl testsuite/integration/group-smoke/ -Dtest=org.jboss.as.test.smoke.embedded.demos.client.jms.JmsClientTestCase
> >> -> runs the one test as expected
> >> (I did -pl testsute/integration/group-smoke on the assumption that we will be moving to modules)
> >> --
> >>
> >> cd testsuite/integration/group-basic
> >> mvn install -Dtest=org.jboss.as.test.integration.deployment.classloading.ear.EarClassPath2TestCase
> >> -> runs the one test as expected
> >> --
> >>
> >> cd testsuite/integration/group-basic
> >> mvn install
> >> -> Runs those tests as expected
> >> --
> >
> > There will be some slight changes coming up, such as moving the test classes into individual modules. They currently all live in testsuite/integration/ and are compiled by the individual sub-modules.
> > _______________________________________________
> > jboss-as7-dev mailing list
> > jboss-as7-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-as7-dev/attachments/20111125/68216069/attachment.html
More information about the jboss-as7-dev
mailing list