|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
| | ||
| Search | ||
| ||
2008 International Conference on Software Testing, Verification, and Validation
Trace-based Reflexive Testing of OO Programs with T2
April 09-April 11
ISBN: 978-0-7695-3127-4
| ASCII Text | x | ||
| Wishnu Prasetya, Tanya Vos, Arthur Baars, "Trace-based Reflexive Testing of OO Programs with T2," Software Testing, Verification, and Validation, 2008 International Conference on, pp. 151-160, 2008 International Conference on Software Testing, Verification, and Validation, 2008. | |||
| BibTex | x | ||
| @article{ 10.1109/ICST.2008.12, author = {Wishnu Prasetya and Tanya Vos and Arthur Baars}, title = {Trace-based Reflexive Testing of OO Programs with T2}, journal ={Software Testing, Verification, and Validation, 2008 International Conference on}, volume = {0}, year = {2008}, isbn = {978-0-7695-3127-4}, pages = {151-160}, doi = {http://doi.ieeecomputersociety.org/10.1109/ICST.2008.12}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - CONF JO - Software Testing, Verification, and Validation, 2008 International Conference on TI - Trace-based Reflexive Testing of OO Programs with T2 SN - 978-0-7695-3127-4 SP151 EP160 A1 - Wishnu Prasetya, A1 - Tanya Vos, A1 - Arthur Baars, PY - 2008 KW - unit testing KW - automated testing KW - trace based testing KW - sequence based testing VL - 0 JA - Software Testing, Verification, and Validation, 2008 International Conference on ER - | |||
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/ICST.2008.12
This paper presents an automatic trace-based unit testing approach to test object-oriented programs. Most automated testing tools test a class C by testing each of its methods in isolation. Such an approach works poorly if specifications are only partial, which is usually the case in practice. In contrast, our approach generates sequences of calls to the methods of C that are checked on-the-fly. This is more interactive, and has the side effect that methods are checking each other. Although simple, it seems to work quite well, even when specifications are only partially provided. We implement the approach in a tool called T2. It targets Java. It can test internal errors, Hoare triple specifications, class invariant, and even temporal properties. Furthermore, T2 accepts ’in-code’ specifications, these are specifications written in the specified class itself, and are written in plain Java; hence reducing the cost usually needed to maintain specifications to minimum.
Index Terms:
unit testing, automated testing, trace based testing, sequence based testing
Citation:
Wishnu Prasetya, Tanya Vos, Arthur Baars, "Trace-based Reflexive Testing of OO Programs with T2," icst, pp.151-160, 2008 International Conference on Software Testing, Verification, and Validation, 2008
Usage of this product signifies your acceptance of the Terms of Use.
