Testing for Developers
I have been passsed the slightly unusual request to provide a 10 point check list for testing. The intention is that this would be passed to developers as a guide in the style of ' if you have done the following things, then your code quality should not be too far wrong' (note that this is not intended to replace the current detailed unit/integration test guidelines). As a kick off I have suggested
1. Identify and create any common code templates early in design
2. Plan unit testing prior to coding (i.e. don't test code against actual code outcomes)
3. Ensure you understand the design and purpose of the component.
4. Identify all component interfaces and verify that the expected calls are supported by the related components
5. Ensure that there is an error handler both for expected and unexpected code interuption.
6. Test interfaces for valid and invalid parameter passing (black box)
7. Test all significant paths though the component (white box)
8. Document any assumptions that have been made in the coding
I have to do this for system testing as well so I will repeat this post in another forum.
Any advice welcome.
Re: Testing for Developers
I feel 5 may be tricky for junior developers. 2 is difficult to follow in real life situations but if you can stick to that then surely you would be one adding greatr value for your project if it is a long term project.