GeekArticles
Testing
CheckLists
Testing
CheckListsTesting Testability
Recently I overheard a conversation between a test analyst and a business analyst about how a function should be tested. The response from the business analyst was, "If it is not breaking the application, it must be working fine!" Testing staff comes across such scenarios where a part or functionality of the application under test is not "testable." The tests they carry out are not conclusive enough to say that the functionality is working as specified. In this week's article, Ipsita Chatterjee defines testability and looks at the benefits of incorporating it in the products. Also discussed are simple ways to monitor the incorporation of this non-functional requirement in the software development life cycle and a few industry myths about testability.
Sponsored Links
Read Next: Testing, A Streamlined Approach
Related Topics
Subscribe via RSS
CheckLists
- Graphical User Interface
- The Road to UML Is Paved with Good Intentions
- How to Choose between Exploratory and Scripted Testing
- Testing Testability
- Testing, A Streamlined Approach
- Open Checklist
- Creating Compelling Checklists
- Regression Test Suite Maintenance Techniques
- A Positive View of Negative Testing
- A Roadmap for Effective and Efficient Test Cases Review
