Just wanted to ask on the back of this whether any of you have got the
Maven Site Reporting working when you have some JUnit tests running in
the 'Integration-test' phase.
I posted this recently
OK, my thanks to Arnaud, Dave and Wendy!
I'm going to try it out over the next couple of days, I feel that I have a
good direction now. Thanks!
Kind regards
Kjetil Kjernsmo
--
Senior Knowledge Engineer
Direct: +47 6783 1136 | Mobile: +47 986 48 234
Email: [EMAIL PROTECTED]
Web:
Hello,
Here is some sample POM that exposes what could be done to separate
tests into different groups. Note that the same things could be done
using the groups tag for testNG. The interesting thing is that
execurtions can be merged (eg. mvn -Ptest1,test2 test) to group
several subgroups.
project
On Monday 03 September 2007 18:06:48 Dave Feltenberger wrote:
One approach I've seen used is to have a standard naming convention on your
test cases. Maven will automatically run classes named *Test.java (and I
believe any class that starts with Test),
OK, so Test* classes and files named
Kjetil Kjernsmo [EMAIL PROTECTED] writes:
Looking through the source tree, I see that we do allready have a naming
convention, but in terms of directory naming:
test:
functional/
integration/
performance/
unit/
where a test may have a path like:
I think Arnaud's advice is right if you're going to keep one project for
everything - set up the profiles. You may need to re-arrange the source
tree a little bit, though - looks like you have several different source
trees, one for each category of tests. I'm not sure how the surefire plugin
Hi all!
I'm new to Maven. In fact, I'm pretty new to the Java world, I just dropped by
some years ago, and I see things have progressed rapidly.
I'm migrating an old project to Maven, but there is something I don't quite
see how should be done.
We have a bunch of heavy tests, like performance
On 9/3/07, Kjetil Kjernsmo [EMAIL PROTECTED] wrote:
We have a bunch of heavy tests, like performance tests, some functional tests
and stuff, they can run for hours, so it is not something you launch
light-hearted. Usually, most of these tests would only be run prior to a
deployment to
