I’ve loved the next sentence, read here:
The more tests the more attention they need. We can reduce the time we spend on nurturing by writing test only against public method. Public methods are contract. If we specify some contract we will rather not change it as often as private methods. If you feel that you have to test private method it is a sign of a bad design (it’s called “code smell”). Probably functionality of this method belongs elsewhere.
You should read this, if you haven’t already. Thanks Mr. Fowler for that magnificent piece of work.
By default, when you build your project with Maven, it will run the entire unit tests of your project.
$ mvn install
$ mvn package
However, if any of unit test is failed, it will force Maven to abort the building process. In real life, you may still need to build your project even unit test is failed.
To skip it, use -Dmaven.test.skip=true option to tell Maven that you want to skip running the entire unit test. For example,
$ mvn install -Dmaven.test.skip=true
$ mvn package -Dmaven.test.skip=true
Now, when you build your project build, all unit tests will be ignored.