THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
JUnit tests are divided into two main categories: UnitTest and IntegrationTest.
1. UnitTest: is a test with very narrow and well defined scope. Any complex dependencies and interactions are stubbed or mocked. (See UnitTest.)
- Should use JUnit 4 syntax
- File name ends with *Test
- Should use Category annotation of type UnitTest
- Should complete in milliseconds
- Should generally test a single class
- Typically uses white-box testing, uses Mocks/Fakes and helps guarantee internal quality (quality of code and class design)
- Follows "A Set of Unit Testing Rules" by Michael Feathers
- A UnitTest should not do any of the following:
- communicate with a database
- communicate across the network
- access the file system
- prevent the running of other unit tests in parallel
- require anything special in the environment (such as editing config files or running an external process)
- A UnitTest should not do any of the following:
...