Content deleted Content added
I can find it in dozens of books, so it's obviously notable. Also I fixed the many wrongs things in this crappy stub. A summary of the fixes doesn't even fit in this summary box. |
|||
Line 1:
In [[software engineering]], '''basis path testing''', or '''structured testing''', is a [[white box]] method for designing [[test case]]s. The method analyzes the [[control flow graph]] of a program to find a set of linearly independent paths of [[execution (computing)|execution]]. The method normally uses McCabe' [[cyclomatic complexity]] to determine the number of linearly independent paths and then generates test cases for each path.<ref name="Westfall2008">{{cite book|author=Linda Westfall|title=The Certified Software Quality Engineer Handbook|year=2008|publisher=ASQ Quality Press|isbn=978-0-87389-730-3|pages=436-437}}</ref> The method guarantees complete [[code coverage]], but achieves that without covering all possible paths.<ref name="SrikantShankar2002">{{cite book|author1=Y.N. Srikant|author2=Priti Shankar|title=The Compiler Design Handbook: Optimizations and Machine Code Generation|year=2002|publisher=CRC Press|isbn=978-1-4200-4057-9|page=249}}</ref> The method has been widely used and studied.<ref name="Binder2000">{{cite book|author=Robert V. Binder|title=Testing Object-oriented Systems: Models, Patterns, and Tools|year=2000|publisher=Addison-Wesley Professional|isbn=978-0-201-80938-1|page=378}}</ref>
==References==
{{reflist}}
== External links ==
Line 17 ⟶ 8:
[[Category:Software testing]]
{{Software-eng-stub}}
|