NguyenAndrew/Unit-Testing-Guidelines

Unit Testing Guidelines that apply for any and all programming languages

Unit Testing Guidelines

1. Always add unit test for new business logic code, and always add/refactor unit tests for refactored business logic code.
2. Unit test code must be evaluated with the same level of quality as business logic code.
3. Any implicit unit test behavior, should be written explictily.
4. Make it easy to write new unit tests.
5. Make it easy to refactor existing unit tests.
6. Limit behavior of injected dependencies for any-and-all methods under tests. Do not overmock your mocks. Restrict the behavior of non-mocked dependencies to only expose required functionality.
7. All unit tests must run in a reasonable amount of time.
8. Unit test code must not be sent to production, without its corresponding business logic code. Business logic code must not be sent to production, without its corresponding unit test code.