- Expected bugs from that module
- Cost of each bug (wrong functionality, system crash, hanging, or just nothing happens)
- Amount of logic in that module
- Ideas about scenarios, tricks or tweaks that may not be handled well by the module
Wednesday, May 16, 2007
Testing Strategy
A good way to decide which testing strategy to use to test a module is to base your decision on the developer of that module who can give you information about:
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment