Bhupendra Bhardwaj wrote:
Hi all,
I was running the tests in the systests module and saw 16 failures out
of 45
tests. Some of those even throwing NullPointerException.
Those tests are not up to date with the changes in the trunk. And I think
the reason behind that is that those tests don't get run with mvn.
I am thinking of updating the pom to get those tests run with mvn. I
wanted
to check with all if there was a reason why those were not setup to
run with
mvn at first place. If those are supposed to be run seperately and not
with
mvn then there is nothing to make sure that those are run.
My philosophy is to run all tests by default, but provide switches for
developers to select subsets to focus on a particular area. If there are
tests "on the side" that aren't run by default, typically they get
forgotten.
The only exception I would make is stress or performance tests that
need to run for many minutes or even hours. To avoid forgetting they
should be run regularly by an automated build - which is coming soon I
believe :)
Cheers,
Alan.
