|
| |
|
| |
Requirements-driven testing: The first step to automation |
| |
|
| |
Prashanth Shidlaghatta
QA Architect - Compuware Corporation
Prashanth has over 10 years of experience as an information technology professional. He is a Subject Matter Expert on Compuware's Application Development Solution offering. He has worked as a senior consultant with leading finance, insurance, automobile and manufacturing organizations across North America to define MDA strategy for enterprise wide adoption. Prashanth current focus is on technologies and processes that bring more agility to software development.
ABSTRACT: Requirements-driven testing: The first step to automation Poor requirements lead directly to poor application quality. When business requirements are ambiguous, missing or just plain wrong, it is impossible for testers to confidently build a test plan that truly validates an application's business functionality. Instead, testers are force to "fly blind" and try to guess what the business expects the application to do. The results of this approach are disastrous: IDC research indicates that 70-80% of project failures stem directly from poor business requirements. The approach --called Requirements-driven testing--is specifically designed to address this problem. Requirements-driven testing improves application quality by enabling teams to capture better business requirements and directly leverage them in the testing process.
<<Back
|
| |
|
|
