DOCSLIB.ORG

Object Oriented Testing Techniques: Survey and Challenges

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Object Oriented Testing Techniques: Survey and Challenges ISSN:2229-6093 Prashant ,Int.J.Computer Technology & Applications,Vol 3 (2), 746-749 Object Oriented Testing Techniques: Survey and Challenges Prashant, Dept. Of I.T., Gurgaon College of Engg., Gurgaon, Haryana. [email protected] Abstract: Object-oriented programs involve many unique excellent structuring mechanism. They allow a features that are not present in their conventional system to be divided into well-defined units, which counterparts. Examples are message passing, may then be implemented separately. Second, classes synchronization, dynamic binding, object instantiation, support information hiding. Third, object-orientation persistence, encapsulation, inheritance, and polymorphism. encourages and supports software reuse. This may be Testing for such program is, therefore, more difficult than that for conventional programs. Object-orientation has achieved either through the simple reuse of a class in rapidly become accepted as the preferred paradigm for a library, or via inheritance, whereby a new class may large-scale system design. In this paper we have discussed be created as an extension of an existing one [2]. about how testing is being carried out in the Object These might cause some types of faults that are Oriented environment. To accommodate this, several new difficult to detect using traditional testing techniques. techniques have been proposed like fault-based techniques, To overcome these deficiencies, it is necessary to Scenario based, Surface structure testing, and Deep adopt an object-oriented testing technique that takes structural testing. these features into account. Keywords-Fault-based Testing, Scenario-based Testing, 2. TROUBLE MAKERS OF OBJECT ORIENTED Surface Structure Testing. SOFTWARE 1. INTRODUCTION Following are trouble makers of OO Software The testing of software is an important means of 2.1 Encapsulation A wrapping up of data and assessing the software to determine its Quality. With functions into a single unit is known as the development of Fourth generation languages encapsulation. This restricts visibility of object states (4GL), which speeds up the implementation process, and also restricts observability of intermediate test the proportion of time devoted to testing increased. results. Fault discovery is more difficult in this case. As the amount of maintenance and upgrade of 2.2 Polymorphism Polymorphism is one of the existing systems grow, significant amount of testing crucial features of OOP. It simply means one name will also be needed to verify systems after changes multiple forms. Because of polymorphism, all are made [1]. Most testing techniques were originally possible bindings have to be tested. All potential developed for the imperative programming paradigm, execution paths and potential errors have to be tested. with relative less consideration to object-oriented 2.3 Inheritance The mechanism of deriving a new features such as message passing, synchronization, class from an old one is called inheritance. The old dynamic binding, object instantiation, persistence, class is referred to as the base class and the new one encapsulation, inheritance, and polymorphism. is called the derived class or the subclass. Inheritance Objects may interact with one another with results in invisible dependencies between unforeseen combinations and invocations. The testing super/sub-classes. Inheritance results in reduced code of concurrent object-oriented systems has become a redundancy, which results in increased code most challenging task. Object-orientation has rapidly dependencies. If the function is erroneous in the base become accepted as the preferred paradigm for large class, it will be inherited in the derived class too. A scale system design. The reasons for this are well subclass can’t be tested without its super classes. known and understood. First, classes provide an 746 ISSN:2229-6093 Prashant ,Int.J.Computer Technology & Applications,Vol 3 (2), 746-749 3. THE TEST MODEL AND ITS CAPABILITIES Test the state behavior (attributes) of the The tools for automated testing are based upon class between methods certain models of software/programs and algorithms. Class testing is different from conventional testing in This mathematically defined test model consists of that Conventional testing focuses on following types of diagrams: input-process-output, whereas class testing focuses on each method. 3.1 Class Diagram: A class diagram or an object Test cases should be designed so that they are relation diagram (ORD) represents the relationships explicitly associated with the class and/or method to between the various classes and its type. Types of be tested. The purpose of the test should be clearly relationships are mainly: inheritance, aggregation, stated. Each test case should contain: and association. In object oriented programs there are three different relationships between classes they are A list of messages and operations that will inheritance, aggregation and association. be exercised as a consequence of the test A list of exceptions that may occur as the 3.2 Control Flow Graph: A control flow graph object is tested represents the control structure of a member function A list of external conditions for setup (i.e., and its interface to other member functions so that a changes in the environment external to the tester will know which is used and/or updated and software that must exist in order to properly which other functions are invoked by the member conduct the test) function. Supplementary information that will aid in 3.3 State Transition Diagram: A STD or an Object understanding or implementing the test State Diagram (OSD) represents the state behavior of Since object oriented software is rich in an object class. Now the state of a class is embodied encapsulation, Inheritance and Polymorphism the in its member variables which are shared among its following challenges are faced while performing methods. The OSD shows the various states of a class class testing. (various member variable values), and transitions It is difficult to obtain a snapshot of a class between them (method invocations). without building extra methods that display 4 . OBJECT ORIENTED TESTING TECHNIQUES the classes’ state. Each new context of use (subclass) requires Object – Oriented programming is centered around re-testing because a method may be concepts like Object, Class, Message, Interfaces, implemented differently (polymorphism). Inheritance, Polymorphism etc., Traditional testing Other unaltered methods within the subclass techniques can be adopted in Object Oriented may use the redefined method and need to environment by using the following techniques: be tested. Method testing Basis path, condition, data flow and loop Class testing tests can all apply to individual methods, Interaction testing but can’t test interactions between methods System testing 4.3 Integration Testing: Object Orientation does not Acceptance testing have a hierarchical control structure so conventional 4.1 Method Testing: Each individual method of the top-down and bottom up integration tests have little OO software has to be tested by the programmer. meaning. Integration testing can be applied in three This testing ensures Statement Coverage to ensure different incremental strategies: that all statements have been traversed atleast once, Thread-based testing, which integrates Decision Coverage to ensure all conditional classes required to respond to one input or executions and Path Coverage to ensure the execution event. the true and false part of the loop. Use-based testing, which integrates classes 4.2 Class Testing: Class testing is performed on the required by one use case. smallest testable unit in the encapsulated class. Each Cluster testing, which integrates classes operation as part of a class hierarchy has to be tested required to demonstrate one collaboration. because its class hierarchy defines its context of use. Integration testing is performed using the following New methods, inherited methods and redefined methods: methods within the class have to be tested. This For each client class, use the list of class testing is performed using the following approaches: methods to generate a series of random test Test each method (and constructor) within a sequences. Methods will send messages to class other server classes. 747 ISSN:2229-6093 Prashant ,Int.J.Computer Technology & Applications,Vol 3 (2), 746-749 For each message that is generated, careful attempt at "requirements elicitation". These determine the collaborating class and the scenarios will also tend to flush out interaction bugs. corresponding method in the server object. They are more complex and more realistic than fault For each method in the server object (that based tests often are. They tend to exercise multiple has been invoked by messages sent from the subsystems in a single test, exactly because that's client object), determine the messages that it what users do. The tests won't find everything, but transmits. they will at least cover the higher visibility For each of the messages, determine the next interaction bugs[4]. level of methods that are invoked and add 5.3 Surface Structure Testing: Object-oriented these into the test sequence. programming arguably encourages a different style of 4.4 System Testing: All rules and methods of interface. Rather than performing functions, users traditional systems testing are also applicable to may be given objects to fool around with in a direct object-oriented systems.
Load more

Recommended publications
  • Programming Paradigms & Object-Oriented
    4.3 (Programming Paradigms & Object-Oriented- Computer Science 9608 Programming) with Majid Tahir Syllabus Content: 4.3.1 Programming paradigms Show understanding of what is meant by a programming paradigm Show understanding of the characteristics of a number of programming paradigms (low- level, imperative (procedural), object-oriented, declarative) – low-level programming Demonstrate an ability to write low-level code that uses various address modes: o immediate, direct, indirect, indexed and relative (see Section 1.4.3 and Section 3.6.2) o imperative programming- see details in Section 2.3 (procedural programming) Object-oriented programming (OOP) o demonstrate an ability to solve a problem by designing appropriate classes o demonstrate an ability to write code that demonstrates the use of classes, inheritance, polymorphism and containment (aggregation) declarative programming o demonstrate an ability to solve a problem by writing appropriate facts and rules based on supplied information o demonstrate an ability to write code that can satisfy a goal using facts and rules Programming paradigms 1 4.3 (Programming Paradigms & Object-Oriented- Computer Science 9608 Programming) with Majid Tahir Programming paradigm: A programming paradigm is a set of programming concepts and is a fundamental style of programming. Each paradigm will support a different way of thinking and problem solving. Paradigms are supported by programming language features. Some programming languages support more than one paradigm. There are many different paradigms, not all mutually exclusive. Here are just a few different paradigms. Low-level programming paradigm The features of Low-level programming languages give us the ability to manipulate the contents of memory addresses and registers directly and exploit the architecture of a given processor.
    [Show full text]
  • Bioconductor: Open Software Development for Computational Biology and Bioinformatics Robert C
    View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by Collection Of Biostatistics Research Archive Bioconductor Project Bioconductor Project Working Papers Year 2004 Paper 1 Bioconductor: Open software development for computational biology and bioinformatics Robert C. Gentleman, Department of Biostatistical Sciences, Dana Farber Can- cer Institute Vincent J. Carey, Channing Laboratory, Brigham and Women’s Hospital Douglas J. Bates, Department of Statistics, University of Wisconsin, Madison Benjamin M. Bolstad, Division of Biostatistics, University of California, Berkeley Marcel Dettling, Seminar for Statistics, ETH, Zurich, CH Sandrine Dudoit, Division of Biostatistics, University of California, Berkeley Byron Ellis, Department of Statistics, Harvard University Laurent Gautier, Center for Biological Sequence Analysis, Technical University of Denmark, DK Yongchao Ge, Department of Biomathematical Sciences, Mount Sinai School of Medicine Jeff Gentry, Department of Biostatistical Sciences, Dana Farber Cancer Institute Kurt Hornik, Computational Statistics Group, Department of Statistics and Math- ematics, Wirtschaftsuniversitat¨ Wien, AT Torsten Hothorn, Institut fuer Medizininformatik, Biometrie und Epidemiologie, Friedrich-Alexander-Universitat Erlangen-Nurnberg, DE Wolfgang Huber, Department for Molecular Genome Analysis (B050), German Cancer Research Center, Heidelberg, DE Stefano Iacus, Department of Economics, University of Milan, IT Rafael Irizarry, Department of Biostatistics, Johns Hopkins University Friedrich Leisch, Institut fur¨ Statistik und Wahrscheinlichkeitstheorie, Technische Universitat¨ Wien, AT Cheng Li, Department of Biostatistical Sciences, Dana Farber Cancer Institute Martin Maechler, Seminar for Statistics, ETH, Zurich, CH Anthony J. Rossini, Department of Medical Education and Biomedical Informat- ics, University of Washington Guenther Sawitzki, Statistisches Labor, Institut fuer Angewandte Mathematik, DE Colin Smith, Department of Molecular Biology, The Scripps Research Institute, San Diego Gordon K.
    [Show full text]
  • Paradigms of Computer Programming
    Paradigms of computer programming l This course aims to teach programming as a unified discipline that covers all programming languages l We cover the essential concepts and techniques in a uniform framework l Second-year university level: requires some programming experience and mathematics (sets, lists, functions) l The course covers four important themes: l Programming paradigms l Mathematical semantics of programming l Data abstraction l Concurrency l Let’s see how this works in practice Hundreds of programming languages are in use... So many, how can we understand them all? l Key insight: languages are based on paradigms, and there are many fewer paradigms than languages l We can understand many languages by learning few paradigms! What is a paradigm? l A programming paradigm is an approach to programming a computer based on a coherent set of principles or a mathematical theory l A program is written to solve problems l Any realistic program needs to solve different kinds of problems l Each kind of problem needs its own paradigm l So we need multiple paradigms and we need to combine them in the same program How can we study multiple paradigms? l How can we study multiple paradigms without studying multiple languages (since most languages only support one, or sometimes two paradigms)? l Each language has its own syntax, its own semantics, its own system, and its own quirks l We could pick three languages, like Java, Erlang, and Haskell, and structure our course around them l This would make the course complicated for no good reason
    [Show full text]
  • The Machine That Builds Itself: How the Strengths of Lisp Family
    Khomtchouk et al. OPINION NOTE The Machine that Builds Itself: How the Strengths of Lisp Family Languages Facilitate Building Complex and Flexible Bioinformatic Models Bohdan B. Khomtchouk1*, Edmund Weitz2 and Claes Wahlestedt1 *Correspondence: [email protected] Abstract 1Center for Therapeutic Innovation and Department of We address the need for expanding the presence of the Lisp family of Psychiatry and Behavioral programming languages in bioinformatics and computational biology research. Sciences, University of Miami Languages of this family, like Common Lisp, Scheme, or Clojure, facilitate the Miller School of Medicine, 1120 NW 14th ST, Miami, FL, USA creation of powerful and flexible software models that are required for complex 33136 and rapidly evolving domains like biology. We will point out several important key Full list of author information is features that distinguish languages of the Lisp family from other programming available at the end of the article languages and we will explain how these features can aid researchers in becoming more productive and creating better code. We will also show how these features make these languages ideal tools for artificial intelligence and machine learning applications. We will specifically stress the advantages of domain-specific languages (DSL): languages which are specialized to a particular area and thus not only facilitate easier research problem formulation, but also aid in the establishment of standards and best programming practices as applied to the specific research field at hand. DSLs are particularly easy to build in Common Lisp, the most comprehensive Lisp dialect, which is commonly referred to as the “programmable programming language.” We are convinced that Lisp grants programmers unprecedented power to build increasingly sophisticated artificial intelligence systems that may ultimately transform machine learning and AI research in bioinformatics and computational biology.
    [Show full text]
  • Scripting: Higher- Level Programming for the 21St Century
    . John K. Ousterhout Sun Microsystems Laboratories Scripting: Higher- Cybersquare Level Programming for the 21st Century Increases in computer speed and changes in the application mix are making scripting languages more and more important for the applications of the future. Scripting languages differ from system programming languages in that they are designed for “gluing” applications together. They use typeless approaches to achieve a higher level of programming and more rapid application development than system programming languages. or the past 15 years, a fundamental change has been ated with system programming languages and glued Foccurring in the way people write computer programs. together with scripting languages. However, several The change is a transition from system programming recent trends, such as faster machines, better script- languages such as C or C++ to scripting languages such ing languages, the increasing importance of graphical as Perl or Tcl. Although many people are participat- user interfaces (GUIs) and component architectures, ing in the change, few realize that the change is occur- and the growth of the Internet, have greatly expanded ring and even fewer know why it is happening. This the applicability of scripting languages. These trends article explains why scripting languages will handle will continue over the next decade, with more and many of the programming tasks in the next century more new applications written entirely in scripting better than system programming languages. languages and system programming
    [Show full text]
  • Six Canonical Projects by Rem Koolhaas
    5 Six Canonical Projects by Rem Koolhaas has been part of the international avant-garde since the nineteen-seventies and has been named the Pritzker Rem Koolhaas Architecture Prize for the year 2000. This book, which builds on six canonical projects, traces the discursive practice analyse behind the design methods used by Koolhaas and his office + OMA. It uncovers recurring key themes—such as wall, void, tur montage, trajectory, infrastructure, and shape—that have tek structured this design discourse over the span of Koolhaas’s Essays on the History of Ideas oeuvre. The book moves beyond the six core pieces, as well: It explores how these identified thematic design principles archi manifest in other works by Koolhaas as both practical re- Ingrid Böck applications and further elaborations. In addition to Koolhaas’s individual genius, these textual and material layers are accounted for shaping the very context of his work’s relevance. By comparing the design principles with relevant concepts from the architectural Zeitgeist in which OMA has operated, the study moves beyond its specific subject—Rem Koolhaas—and provides novel insight into the broader history of architectural ideas. Ingrid Böck is a researcher at the Institute of Architectural Theory, Art History and Cultural Studies at the Graz Ingrid Böck University of Technology, Austria. “Despite the prominence and notoriety of Rem Koolhaas … there is not a single piece of scholarly writing coming close to the … length, to the intensity, or to the methodological rigor found in the manuscript
    [Show full text]
  • Comparing Bioinformatics Software Development by Computer Scientists and Biologists: an Exploratory Study
    Comparing Bioinformatics Software Development by Computer Scientists and Biologists: An Exploratory Study Parmit K. Chilana Carole L. Palmer Amy J. Ko The Information School Graduate School of Library The Information School DUB Group and Information Science DUB Group University of Washington University of Illinois at University of Washington [email protected] Urbana-Champaign [email protected] [email protected] Abstract Although research in bioinformatics has soared in the last decade, much of the focus has been on high- We present the results of a study designed to better performance computing, such as optimizing algorithms understand information-seeking activities in and large-scale data storage techniques. Only recently bioinformatics software development by computer have studies on end-user programming [5, 8] and scientists and biologists. We collected data through semi- information activities in bioinformatics [1, 6] started to structured interviews with eight participants from four emerge. Despite these efforts, there still is a gap in our different bioinformatics labs in North America. The understanding of problems in bioinformatics software research focus within these labs ranged from development, how domain knowledge among MBB computational biology to applied molecular biology and and CS experts is exchanged, and how the software biochemistry. The findings indicate that colleagues play a development process in this domain can be improved. significant role in information seeking activities, but there In our exploratory study, we used an information is need for better methods of capturing and retaining use perspective to begin understanding issues in information from them during development. Also, in bioinformatics software development. We conducted terms of online information sources, there is need for in-depth interviews with 8 participants working in 4 more centralization, improved access and organization of bioinformatics labs in North America.
    [Show full text]
  • Technological Advancement in Object Oriented Programming Paradigm for Software Development
    International Journal of Applied Engineering Research ISSN 0973-4562 Volume 14, Number 8 (2019) pp. 1835-1841 © Research India Publications. http://www.ripublication.com Technological Advancement in Object Oriented Programming Paradigm for Software Development Achi Ifeanyi Isaiah1, Agwu Chukwuemeka Odi2, Alo Uzoma Rita3, Anikwe Chioma Verginia4, Okemiri Henry Anaya5 1Department of Maths/Comp Sci/Stats/Info., Faculty of science, Alex Ekwueme University, Ndufu-Alike 2Department of Computer Science, Ebonyi State University-Abakaliki. 3Alex Ekwueme University, Ndufu-Alike, 4Department of Maths/Comp Sci/Stats/Info., Faculty of science, Alex Ekwueme University, Ndufu-Alike 5Department of Maths/Comp Sci/Stats/Info., Faculty of science, Alex Ekwueme University, Ndufu-Alike Abstract and personalization problems. Take for instance, a lot of sophisticated apps are being produced and release in the Object oriented programming paradigm in software market today through the application of OOP. Almost desktop development is one of the most popular methods in the apps are being converted to mobile apps through Java, C++, information technology industry and academia as well as in PHP & MySQL, R, Python etc platform which form the many other forms of engineering design. Software testimony of OOP in the software industries. Software development is a field of engineering that came into existence developer has been revolving using procedural language for owing to the various problems that developers of software the past decade before the advent of OOP. The relationships faced while developing software projects. This paper analyzes between them is that procedural languages focus on the some of the most important technological innovations in algorithm but OOP focuses on the object model itself, object oriented software engineering in recent times.
    [Show full text]
  • Object Oriented Database Management Systems-Concepts
    View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by Global Journal of Computer Science and Technology (GJCST) Global Journal of Computer Science and Technology: C Software & Data Engineering Volume 15 Issue 3 Version 1.0 Year 2015 Type: Double Blind Peer Reviewed International Research Journal Publisher: Global Journals Inc. (USA) Online ISSN: 0975-4172 & Print ISSN: 0975-4350 Object Oriented Database Management Systems-Concepts, Advantages, Limitations and Comparative Study with Relational Database Management Systems By Hardeep Singh Damesha Lovely Professional University, India Abstract- Object Oriented Databases stores data in the form of objects. An Object is something uniquely identifiable which models a real world entity and has got state and behaviour. In Object Oriented based Databases capabilities of Object based paradigm for Programming and databases are combined due remove the limitations of Relational databases and on the demand of some advanced applications. In this paper, need of Object database, approaches for Object database implementation, requirements for database to an Object database, Perspectives of Object database, architecture approaches for Object databases, the achievements and weakness of Object Databases and comparison with relational database are discussed. Keywords: relational databases, object based databases, object and object data model. GJCST-C Classification : F.3.3 ObjectOrientedDatabaseManagementSystemsConceptsAdvantagesLimitationsandComparativeStudywithRelationalDatabaseManagementSystems Strictly as per the compliance and regulations of: © 2015. Hardeep Singh Damesha. This is a research/review paper, distributed under the terms of the Creative Commons Attribution- Noncommercial 3.0 Unported License http://creativecommons.org/licenses/by-nc/3.0/), permitting all non-commercial use, distribution, and reproduction inany medium, provided the original work is properly cited.
    [Show full text]
  • Future Generation Supercomputers II: a Paradigm for Cluster Architecture
    Future Generation Supercomputers II: A Paradigm for Cluster Architecture N.Venkateswaran§,DeepakSrinivasan†, Madhavan Manivannan†, TP Ramnath Sai Sagar† Shyamsundar Gopalakrishnan† VinothKrishnan Elangovan† Arvind M† Prem Kumar Ramesh Karthik Ganesan Viswanath Krishnamurthy Sivaramakrishnan Abstract Blue Gene/L, Red Storm, and ASC Purple clearly marks that these machines although significantly diverse along the In part-I, a novel multi-core node architecture was proposed afore-mentioned design parameters, offer good performance which when employed in a cluster environment would be ca- during ”Grand Challenge Application” execution. But fu- pable of tackling computational complexity associated with ture generation applications might require close coupling of wide class of applications. Furthermore, it was discussed previously independent application models, as highlighted in that by appropriately scaling the architectural specifications, NASA’s report on Earth Science Vision 2030[2], which in- Teraops computing power could be achieved at the node volves simulations on coupled climate models, such as ocean, level. In order to harness the computational power of such atmosphere, biosphere and solid earth. These kind of hybrid a node, we have developed an efficient application execution applications call for simultaneous execution of the compo- model with a competent cluster architectural backbone. In nent applications, since the execution of different applica- this paper we present the novel cluster paradigm, dealing tions on separate clusters
    [Show full text]
  • The Graph-Oriented Programming Paradigm
    The Graph-Oriented Programming Paradigm Olivier Rey Copyright ©2016 Olivier Rey [email protected] October 26 2016 Preliminary Version Abstract 1.2 Common Use Cases for Attributed Directed Graph Databases Graph-oriented programming is a new programming paradigm that de- fines a graph-oriented way to build enterprise software, using directed At the time this article is being written, attributed directed attributed graph databases on the backend side. graph databases are mostly used: This programming paradigm is cumulating the benefits of sev- • In Internet social applications, eral other programming paradigms: object-orientation, functional pro- gramming, design by contract, rule-based programming. However, it • For Big Data purposes, is consistent in itself and does not depend on any other programming paradigms. It is also simpler and more intuitive than the other pro- • For recommendation algorithms in retail or assimilated gramming paradigms. Moreover, it shows astonishing properties in businesses, terms of software evolution and extensibility. This programming paradigm enables to develop long lasting busi- • In fraud detection based on pattern matching, ness applications that do not generate any technical debt. It provides a radically different answer to the maintenance and evo- • In some other more restricted areas such as reference data lutions phases compared to other programming paradigms. Its use is management, identity management or network modeling. particularly adapted for applications that must manage high complex- ity, evolving regulations and/or high numbers of business rules. This article will not speak about those common graph With graph-oriented programming, software can evolve structurally database use cases, and we will direct the reader to the mas- without having to redesign it, to migrate the data or to perform non sive documentation available on the Internet on those topics.
    [Show full text]
  • Pdf: Software Testing
    Software Testing Gregory M. Kapfhammer Department of Computer Science Allegheny College [email protected] I shall not deny that the construction of these testing programs has been a major intellectual effort: to convince oneself that one has not overlooked “a relevant state” and to convince oneself that the testing programs generate them all is no simple matter. The encouraging thing is that (as far as we know!) it could be done. Edsger W. Dijkstra [Dijkstra, 1968] 1 Introduction When a program is implemented to provide a concrete representation of an algorithm, the developers of this program are naturally concerned with the correctness and performance of the implementation. Soft- ware engineers must ensure that their software systems achieve an appropriate level of quality. Software verification is the process of ensuring that a program meets its intended specification [Kaner et al., 1993]. One technique that can assist during the specification, design, and implementation of a software system is software verification through correctness proof. Software testing, or the process of assessing the func- tionality and correctness of a program through execution or analysis, is another alternative for verifying a software system. As noted by Bowen, Hinchley, and Geller, software testing can be appropriately used in conjunction with correctness proofs and other types of formal approaches in order to develop high quality software systems [Bowen and Hinchley, 1995, Geller, 1978]. Yet, it is also possible to use software testing techniques in isolation from program correctness proofs or other formal methods. Software testing is not a “silver bullet” that can guarantee the production of high quality software systems.
    [Show full text]