Developers love to develop, hate to test, though testing is more critical than everything. Ok maybe not everything. But when bugs happen, it runs hell.
Testing is a never-will-finish process and it is impossible to test every scenario. In a project where resources for full scale testing are limited, and developers themselves needs to be the testers, a shorter and more concise testing process is needed.
Minimal Testing Process is such a process. It is categorized into 4 parts that addresses:
- New features/changes
- Frequently used functionalities
- Critical functionalities
- Complex or error-prone use cases
Any test cases that are neither new, frequently used, critical nor complex are dropped. Simple.