Model Based Object-Oriented Software Testing-Reference-Cited by-同舟云学术

Model Based Object-Oriented Software Testing

Published:2019-10-15 Issue: Volume: Page:13-20
ISSN:2394-4099
Container-title:International Journal of Scientific Research in Science, Engineering and Technology
language:en
Short-container-title:IJSRSET

Author:

Kumar S. Saravana¹

Affiliation:

1. Assistant Professor, Department of Computer Science, Karpagam Academy of Higher Education, Coimbatore, Tamil Nadu, India

Abstract

Testing is an important phase of quality control in Software development. Software testing is necessary to produce highly reliable systems. The use of a model to describe the behavior of a system is a proven and major advantage to test. In this paper, we focus on model-based testing. The term model- based testing refers to test case derivation from a model representing software behavior. We discuss model-based approach to automatic testing of object oriented software which is carried out at the time of software development. We review the reported research result in this area and also discuss recent trends. Finally, we close with a discussion of where model-based testing fits in the present and future of software engineering.

Publisher

Technoscience Academy

Subject

General Medicine

Reference14 articles.

1. W. Prenninger, A. Pretschner, Abstractions for Model-Based Testing, ENTCS 116 (2005) 59- 71.

2. A. Pretschner, J. Philipps, Methodological Issuesin Model-Based Testing, in: [29], 2005, pp. 281-291.

3. J. Philipps, A. Pretschner, O. Slotosch,E. Aiglstorfer, S. Kriebel, K. Scholl, Model based test case generation for smart cards, in:Proc. 8th Intl. Workshop on Formal Meth. For Industrial Critical Syst., 2003, pp. 168-192.

4. G. Walton, J. Poore, Generating transition probabilities to support model-based software testing,Software: Practice and Experience 30 (10) (2000) 1095-1106.

5. A. Pretschner, O. Slotosch, E. Aiglstorfer,S. Kriebel, Model based testing for real-the inhouse card case study, J. Software Tools for Technology Transfer 5 (2-3) (2004) 140-157.