There are two flavors of software (and firmware) tests: the functionality test plan and the try-to-break-it test.
The functionality test plan involves writing test plans to test functionalities and requirements. The try-to-break-it test involves using the software in an unexpected manner without a pre-written test plan.
Managers usually lobby for the functionality test plan and developers usually lobby for the try-to-break-it test.
Both tests are important and both tests must be performed after every new release.
The try-to-break-it test verifies the quality of newly added functionalities. On the other hand, the functionality test plan verifies that all previously added functionalities are still working.
Manager: Why do we need the try-to-break-it test?
Developer: Because we need to test new functionalities now.
Developers: Why do we need the functionality test plan?
Manager: Because we need to test current functionalities in the future after new releases.
The functionality test plan should be updated after running the try-to-break-it test to include tests for all new functionalities.
What do you think?
1 response so far ↓
Gaurav Pandey // September 21, 2007 at 4:10 am
How different would be consider this from Positive or negative testing?
From positive, I would mean - Testing to pass
From negative, I would mean - Testing to fail.
You must be logged in to post a comment.