On 3/8/07, Alan Conway <[EMAIL PROTECTED]> wrote:
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.
Now we are using maven, so maven provides features to include/exclude tests in pom. And on command line , to exclude running the test we use -Pfastinstall. To run only tests we can use "mvn test" and to run only one test we can use "mvn -Dtest=<testname>" 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.
Right. Stress and performance tests shouldn't be part of default mvn run. Automated build will be run at specific time everyday or at whatever interval we configure it. But for developers, who are committing code to the trunk, they should be able to run mvn and see if something is broken.That is what I was doing and didn't realise that certain tests don't get executed only. I will be fixing those tests, which aren't working and if all feel it is good idea to put those as part of mvn run, then will do that too. Regards, Bhupendra B
