Software testability: Difference between revisions

Revision as of 14:34, 18 August 2014

Revision as of 20:42, 19 August 2014

Line 33:

== Testability hierarchy ==

Based on the amount of test cases required to construct a complete test suite in each context (i.e. a test suite such that, if it is applied to the implementation under test, then we collect enough information to precisely determine whether the system is correct or incorrect according to some specification), a testability hierarchy with the following testability classes has been proposed: <ref> I. Rodríguez, L. Llana, P. Rabanal (2014) “A General Testability Theory: Classes, properties, complexity, and testing reductions”. IEEE Transactions on Software Engineering. doi link: http://doi.ieeecomputersociety.org/10.1109/TSE.2014.2331690 </ref><ref> I. Rodríguez (2009) "A General Testability Theory". CONCUR 2009, Springer, LNCS 5710, pp.572–586. doi: 10.1007/978-3-642-04081-8_38</ref>

* Class I: there exists a finite complete test suite.

Line 74:

== References ==

{{Reflist}}

* Robert V. Binder: Testing Object-Oriented Systems: Models, Patterns, and Tools, ISBN 0-201-80938-9

* Stefan Jungmayr: [http://www.dissertation.de/index.php3?active_document=/FDP/sj929.pdf Improving testability of object-oriented systems], ISBN 3-89825-781-9