Hi,
as far as I can see, you have to treat test and production versions
differently anyway, at least in my case, because for example the database
settings in the testcase are different than in the production case, and
some property files are different.
One way this could be solved is to
Hello,
I just tried it and it works great!
As a sidenote, I also included *.xml files for the dbunit test data, so
it's not only testclasses that are copied.
Cheers,
Bo
Petar Tahchiev
Hello,
In agree with Martin. I've put my test classes in the src/test/java
directory, and they don't seem to be included in the cactified war, so they
have to be in the src/main/java directory..
regards, Bo
Ok, I think I have it running. There are some warning when I run maven,
but I guess that's what you're working on.
Cargo starts the webserver now, but no tests are ran.
How can I check what's missing? Some questions are:
1. what classes does cactus look for to test? Should I sepcify a suite
