Testing Plans

[Andrew Eberbach <ae...@us.ibm.com>]

Hi,

As per the call today, I'd like to get the ball rolling with testing. 
Here's a link to the original email I sent a while back in response to 
Nathan's email about testing. 

http://marc.theaimsgroup.com/?l=muse-dev&m=115143926500357&w=2

Steve: thoughts?

I'd like to get a different harness set up for doing runtime testing. This 
would involve having a set-up and tear-down in a JUnit test suite that 
would do the necessary deployment to tomcat (or whatever) and then let 
developers easily write tests against an EPR. The benefit of this is that 
I can then run the whole test suite in two nested "for each" loops:

foreach jvm in jvms-we-support {
      foreach container in containers-we-support {
        jvm\java.exe runSuite container;
      }
}

If this is possible with maven, then we can do that. I just thought it'd 
be easiest with plain old ant.

The other piece I want integrated is code coverage. There's a tool called 
EMMA (http://emma.sourceforge.net/) which will do the nice thing of 
annotating binary class files with code coverage hooks so that we can 
modify the classes and then just run all of the tests. After that the tool 
will generate pretty reports telling us about how much (or how little) 
code coverage we have. Again, I've already tried this with ant and it 
works, I'd like to have have this run after the build but before the 
automated test suite kicks off.

Thanks,
Andrew

Andrew Eberbach
Autonomic Computing
(919) 254-2645
T/L: 444-2645
aeberbac@us.ibm.com