Abstract
Program testing is the most used technique for analytical quality assurance. A lot of time and effort is devoted to this task during the software lifecycle, and it would be useful to have a means for estimating this testing effort. Such estimates could be used, on one hand, for guiding construction and, on the other, to help organise the development process and testing. Thus the effort needed for testing is an important quality attribute of a program; they call it its testability. They argue that a relevant program characteristic contributing to testability is the number of test cases needed for satisfying a given test strategy. They show how this can be measured for glass (white) box testing strategies based on control flow. In this case, one can use structural measures defined on control flowgraphs which can be derived from the source code. In doing so, two well researched areas of software engineering testing strategies and structural metrication are brought together.< >
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
