Abstract
TACCLE tests an automated assembly system in which the expected outcomes cannot be precisely defined and the actual results cannot be directly observed.
- Andrews, J.H. and Zhang, Y. General test result checking with log file analysis. IEEE Transactions on Software Engineering 29, 7 (July 2003), 634--648. Google ScholarDigital Library
- Beizer, B. Software Testing Techniques. Van Nostrand Reinhold, New York, 1990. Google ScholarDigital Library
- Brand, D. and Zafiropulo, P. On communicating finite-state machines. Journal of the ACM 30, 2 (Apr. 1983), 323--342. Google ScholarDigital Library
- Chen, H.Y., Tse, T.H., and Chen, T.Y. TACCLE: A methodology for object-oriented software testing at the class and cluster levels. ACM Transactions on Software Engineering and Methodology 10, 1 (Jan. 2001), 56--109. Google ScholarDigital Library
- Fetzer, C., Felber, P., and Hogstedt, K. Automatic detection and masking of nonatomic exception handling. IEEE Transactions on Software Engineering 30, 8 (Aug. 2004), 547--560. Google ScholarDigital Library
- Goguen, J.A. and Malcolm, G., Eds. Software Engineering with OBJ: Algebraic Specification in Action. Kluwer Academic Publishers, Boston, 2000.Google ScholarCross Ref
- Milner, R. Communication and Concurrency. Prentice Hall International Series in Computer Science. Prentice Hall, Hemel Hempstead, Hertfordshire, U.K., 1989. Google ScholarDigital Library
- National Institute of Standards and Technology. The Economic Impacts of Inadequate Infrastructure for Software Testing. Final Report. Gaithersburg, MD, 2002; www.nist.gov/director/progofc/report02-3.pdf.Google Scholar
- Peters, D.K. and Parnas, D.L. Using test oracles generated from program documentation. IEEE Transactions on Software Engineering 24, 3 (Mar. 1998), 161--173. Google ScholarDigital Library
- van Gabbeek, R.J. and Weijland, W.P. Branching time and abstraction in bisimulation semantics. Journal of the ACM 43, 3 (May 1996), 555--600. Google ScholarDigital Library
- Weyuker, E.J. On testing non-testable programs. The Computer Journal 25, 4 (Nov. 1982), 465--470.Google ScholarCross Ref
- Briand, L., di Penta, M., and Labiche, Y. Assessing and improving state-based class testing: A series of experiments. IEEE Transactions on Software Engineering 30, 11 (Nov. 2004), 770--793. Google ScholarDigital Library
- Chen, H.Y., Tse, T.H., Chan, F.T., and Chen, T. Y. In black and white: An integrated approach to class-level testing of object-oriented programs. ACM Transactions on Software Engineering and Methodology 7, 3 (July 1998), 250--295. Google ScholarDigital Library
- Doong, R.-K. and Frankl, P.G. The ASTOOT approach to testing object-oriented programs. ACM Transactions on Software Engineering and Methodology 3, 2 (Apr. 1994), 101--130. Google ScholarDigital Library
- Pezze, M. and Young, M. Testing object-oriented software. In Proceedings of the 26th International Conference on Software Engineering (ICSE 2004) (Edinburgh, U.K.). IEEE Computer Society Press, Los Alamitos, CA, 2004, 739--740. Google ScholarDigital Library
Index Terms
- Testing object-oriented industrial software without precise oracles or results
Recommendations
Fault-based testing without the need of oracles
AbstractThere are two fundamental limitations in software testing, known as the reliable test set problem and the oracle problem. Fault-based testing is an attempt by Morell to alleviate the reliable test set problem. In this paper, we propose ...
Testing object-oriented software (abstract)
OOPSLA '92: Addendum to the proceedings on Object-oriented programming systems, languages, and applications (Addendum)Testing of object-oriented software is just as important as testing non-object-oriented software, but the process is fundamentally different because of such factors as information hiding, encapsulation, and inheritance. This tutorial teaches you the ...
Comments