[jboss-dev-forums] [Design the new POJO MicroContainer] - Re: aop-mc-int tests with maven

kabir.khan@jboss.com do-not-reply at jboss.com
Mon Apr 23 15:36:53 EDT 2007


I'll try to dig out the old build-test.xml to add the tests, I'll let you know when I get stuck.

A few further questions:

I see we now have things like

  |       <plugin>
  |         <groupId>org.apache.maven.plugins</groupId>
  |         <artifactId>maven-surefire-plugin</artifactId>
  |         <executions>
  |           <execution>
  |             <id>weave</id>
  |             <phase>test</phase>
  |             <goals>
  |               <goal>test</goal>
  |             </goals>
  | ....
  |           <execution>
  |             <id>weave-secure</id>
  |             <phase>test</phase>
  |             <goals>
  |               <goal>test</goal>
  |             </goals>
  | ...
  | 

Is there a way to for example only run the weave-secure tests?

Some of the tests (those belonging to group 3) will be run 4 times, the others will be run twice. At the moment with the surefire plugin I assume that the last run will override the report for the previous run. With the old build they had a separate file generated for each security/weaving configuration, is that possible? 
For example for the org.jboss.test.microcontainer.test.LifecycleTestCase test, you would get something like:

  | TEST-org.jboss.test.microcontainer.test.LifecycleTestCase-weave.txt
  | TEST-org.jboss.test.microcontainer.test.LifecycleTestCase-weave.xml
  | TEST-org.jboss.test.microcontainer.test.LifecycleTestCase-weave-secure.txt
  | TEST-org.jboss.test.microcontainer.test.LifecycleTestCase-weave-secure.xml
  | TEST-org.jboss.test.microcontainer.test.LifecycleTestCase-no-weave.txt
  | TEST-org.jboss.test.microcontainer.test.LifecycleTestCase-no-weave.xml
  | TEST-org.jboss.test.microcontainer.test.LifecycleTestCase-no-weave-secure.txt
  | TEST-org.jboss.test.microcontainer.test.LifecycleTestCase-no-weave-secure.xml
  | 

The extension would also get passed into junit and get picked out by the org.jboss.ant.taskdefs.XMLJUnitMultipleResultFormatter and used as the title/identifier in the generated xml. An example of this can be found in the current aop cc runs
http://cruisecontrol.jboss.com/cc/artifacts/jboss-aop-testsuite/20070423105405/results/index.html,  and then if you click pretty much any package name you will see that the same test has been run under different configurations. Pretty useful if a test fails in some configurations and not others - like for example the tests in the org.jboss.test.aop.jdk15annotated package :-)

Also, with the old build it was possible to just run one single test for a certain weaving mode, e.g

  | $ ant one-test-no-weave -Dtest=org.jboss.test.microcontainer.test.LifecycleTestCase
  | 
  | Is that still doable somehow?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4039989#4039989

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4039989



More information about the jboss-dev-forums mailing list