Skip to main content

Better Test Cases Through Improved Testability

article
|
Summary

This paper defines testability and discusses its importance for software applications. We take a look at why it gets left out of most software components and why it needs to be there right at the design stage of the software development life cycle. It also examines common software controls from a testability point of view and suggests improvements that should be made to ensure better testability.

Software today is getting more and more complex. This complexity brings fresh challenges in testing the software UI and its underlying functionality. Test engineers have to worry about a lot of different kinds of software controls, interfaces between software modules, etc. Test engineers find some software modules easier to test than others. These test modules have "testability" built into them which helps the test engineers make better test cases faster, tests that are easier to automate and hence have better chances of catching bugs in the code.

This paper defines testability and discusses its importance for software applications. We take a look at why it gets left out of most software components and why it needs to be there right at the design stage of the software development life cycle. It also examines common software controls from a testability point of view and suggests improvements that should be made to ensure better testability.

About The Author

The opinions and positions expressed within these guest posts are those of the author alone and do not represent those of the TechWell Community Sites. Guest authors represent that they have the right to distribute this content and that such content is not violating the legal rights of others. If you would like to contribute content to a TechWell Community Site, email [email protected].

Community Sponsor

Lets Hang!

User Comments

0 comments

Not specified