1 841f06OOmutation22Nov7 Exam 2 – Nov 9. 2 841f06OOmutation22Nov7 Articles u Frankl u Parnas u Chen-Kao (OCF graph) u Glass-etal (Viewpoints) u Kuhn-Wallace.

Slides:



Advertisements
Similar presentations
Internal Assessment Your overall IB mark (the one sent to universities after the IB test) in any IB science course is based upon two kinds of assessments.
Advertisements

Mutation Testing Tim Dakeyne. What is Mutation? Where data is changed a small amount, which may or may not change its function Evolution of life Languages.
Software Regression Testing Speaker: Jerry Gao Ph.D. San Jose State University URL:
MUTATION TESTING. Mutation testing is a technique that focuses on measuring the adequacy (quality) of test data (or test cases). Modify a program by introducing.
Grey Box testing Tor Stålhane. What is Grey Box testing Grey Box testing is testing done with limited knowledge of the internal of the system. Grey Box.
Of 17 Assessing the Influence of Multiple Test Case Selection on Mutation Experiments Marcio E. Delamaro and Jeff Offutt George Mason University & Universidade.
Mutation Testing Presented by Sharath Kumar Garlapati Vinesh Thummala.
CLEANROOM SOFTWARE ENGINEERING
1 Software Testing and Quality Assurance Lecture 9 - Software Testing Techniques.
Software Testing and Quality Assurance
A CONTROL INSTRUMENTS COMPANY The Effectiveness of T-way Test Data Generation or Data Driven Testing Michael Ellims.
1 Software Testing and Quality Assurance Lecture 30 - Introduction to Software Testing.
The CONVERSE Project: Tough on Change, Tough on the Causes of Change. Improving Software in Engine Controllers University of York John McDermid, John Clark.
Data Structures and Programming.  John Edgar2.
Software Testing For CSE 3902 Matt Boggus. Terms: Setup / Exercise / Verify / Teardown Setup - whatever needs to be prepared before the code can be run.
CLEANROOM SOFTWARE ENGINEERING.
Ron Kratzke, Vitech Corporation MBSE for System Testing Managing the development of system testing using the principles of Model.
Design Space Exploration
Generalization through a series of replicated experiments on maintainability Erik Arisholm.
Validation Metrics. Metrics are Needed to Answer the Following Questions How much time is required to find bugs, fix them, and verify that they are fixed?
Class Specification Implementation Graph By: Njume Njinimbam Chi-Chang Sun.
© SERG Dependable Software Systems (Mutation) Dependable Software Systems Topics in Mutation Testing and Program Perturbation Material drawn from [Offutt.
Software Logic Mutation Testing Presented by Gary Kaminski.
Article for last Tuesday u “Enhancing Software Testing by Judicious Use of Code Coverage Information” 1 540f07testing20nov06.
Human Computer Interaction CSC User System Interface CSC Class Meeting 7 October 9, 2012.
Chapter 13: Regression Testing Omar Meqdadi SE 3860 Lecture 13 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Grey Box testing Tor Stålhane. What is Grey Box testing Grey Box testing is testing done with limited knowledge of the internal of the system. Grey Box.
Test Drivers and Stubs More Unit Testing Test Drivers and Stubs CEN 5076 Class 11 – 11/14.
Software Reliability in Nuclear Systems Arsen Papisyan Anthony Gwyn.
1 Exam2 Review 841f07exam2review24nov Q1 - Parnas 841f07exam2review24nov27 2 Parnas discussed that software is difficult because failures are not.
15 Nov 2005 Jones - IASTED/SEA 1 Automated Support for Test-Driven Specification Edward L. Jones IASTED SEA Conference Phoenix, Arizona October 14-16,
When to Test Less Presented by Lan Guo. Introduction (1) Methods of software testing: functional, coverage, and user-oriented Phases of software testing:
Statistik.atSeite 1 Norbert Rainer Quality Reporting and Quality Indicators for Statistical Business Registers European Conference on Quality in Official.
Software Testing. Software testing is the execution of software with test data from the problem domain. Software testing is the execution of software.
Today’s Agenda  Final Exam: 12:30am-1:50pm, 12/6 (Tue)  Final Review Software Testing and Maintenance 1.
1 Exam2 Review 841f07exam2review24nov Q1 - Parnas 841f07exam2review24nov27 2 Parnas discussed that software is difficult because failures are not.
First delivery of the course Software Quality and Testing Katerina Zdravkova, Anastas Mišev
Mutation Testing G. Rothermel. Fault-Based Testing White-box and black-box testing techniques use coverage of code or requirements as a “proxy” for designing.
Center for Reliability Engineering Integrating Software into PRA B. Li, M. Li, A. Sinha, Y. Wei, C. Smidts Presented by Bin Li Center for Reliability Engineering.
Testing OO software. State Based Testing State machine: implementation-independent specification (model) of the dynamic behaviour of the system State:
Software Engineering1  Verification: The software should conform to its specification  Validation: The software should do what the user really requires.
1 Pre-exam2 Discussion Exam 2 Thurs, Nov 15 th 150 pts, 2 crib sheets allowed 841f07exam2preview23nov13 1.
Chapter 24 객체지향 응용프로그램 테스팅 Testing Object-Oriented Applications 임현승 강원대학교 Revised from the slides by Roger S. Pressman and Bruce R. Maxim for the book.
Some facts about the cal() program February 5, 2015 Paul Ammann, SWE 437 with thanks to Bob Kurtz.
Object-Oriented Design Concepts University of Sunderland.
1 Using a Fault Hierarchy to Improve the Efficiency of DNF Logic Mutation Testing Gary Kaminski and Paul Ammann ICST 2009.
CSM06: Information Retrieval Notes about writing coursework reports, revision and examination.
Mutation Testing Breaking the application to test it.
1841f06detprob3 Testing Basics Detection probability.
1 Preview of Exam 2 - Thurs 4/3 u 150 pts u Readings SOS Articles OCL spec u x 11,both sides, handwritten cribsheet allowed (turn in with exam) u.
Software Testing Sudipto Ghosh CS 406 Fall 99 November 23, 1999.
PPP Accounting: What should we be trying to achieve. Ken Wild.
Chapter 8 Testing the Programs. Integration Testing  Combine individual comp., into a working s/m.  Test strategy gives why & how comp., are combined.
Simple Criteria of Choosing the Right Binary Trading Software.
Mutation Testing Laraib Zahid & Mariam Arshad. What is Mutation Testing?  Fault-based Testing: directed towards “typical” faults that could occur in.
SOFTWARE TESTING AND QUALITY ASSURANCE. Software Testing.
Testing Integral part of the software development process.
Scientific Literature and Communication Unit 3- Investigative Biology b) Scientific literature and communication.
A Review of Software Testing - P. David Coward
Object oriented system development life cycle
Mid-term Exam Account for 20% of the grade 100 points in total
Improving Test Suites for Efficient Fault Localization
Fabiano Ferrari Software Engineering Federal University of São Carlos
An Empirical Evaluation of the MuJava Mutation Operators
Chapter 10 – Software Testing
CS5103 Software Engineering
Who Guards the Guards? On the Validation of Test Case Migration
Mastery Assessment in Teaching Statistics
Mitigating the Effects of Flaky Tests on Mutation Testing
Mutation Testing Faults are introduced into the program by creating many versions of the program called mutants. Each mutant contains a single fault. Test.
Presentation transcript:

1 841f06OOmutation22Nov7 Exam 2 – Nov 9

2 841f06OOmutation22Nov7 Articles u Frankl u Parnas u Chen-Kao (OCF graph) u Glass-etal (Viewpoints) u Kuhn-Wallace (fault interactions) u Nagappan (STREW) u May-etal (stat model) u Kim-Clark-McDermid (OO mutations) u Derezinska (OO mutations)

3 841f06OOmutation22Nov7 Exam Preview u Last year’s exam was based on different articles (other than Parnas) u Questions last year Parnas’ calculations Extending a concept from a paper Explaining a concept from a paper Explaining statistical concepts

4 841f06OOmutation22Nov7 Tuesday, Nov 7th u Investigating the effectiveness of object- oriented testing strategies using the mutation method u Object-Oriented Mutation to Asses the Quality of Tests u Do Making Meaning for the two articles and submit by by 8am, Tues 11/7

5 841f06OOmutation22Nov7 Object-Oriented Mutations to Assess the Quality of Tests Anna Derezinska 29 th EuroMicro Conference

6 841f06OOmutation22Nov7 OO mutation ops for code and spec

7 841f06OOmutation22Nov7 Mutants Mutants 2, 9 and 24 were equivalent mutants. Mutant 11 was also not killed by any test from the basic test set. An additional test - Direction_indicator_lights_2 was developed to kill this mutant. Final minimal set of tests consists of 5 test cases, 4 from the basic set of functional tests and this additional test. This test set kills all non-equivalent mutants.

8 841f06OOmutation22Nov7 Results

9 841f06OOmutation22Nov7 Results The selected minimal test suite satisfies the coverage criteria with 83% coverage for functions and 85% for code lines. For 8 classes (from 17) the coverage was maximal. The above-discussed tests were also compared with another test set randomly generated and selected to maximize coverage of the code. In the comparison to the minimal selected test set, the coverage decreased to 43% for function calls and to 52% for line hits.

10 841f06OOmutation22Nov7 Investigating the effectiveness of object-oriented testing strategies using the mutation method Kim, Clark, and McDermid Software Testing, Verification and Reliability 2001

11 841f06OOmutation22Nov7 Table IX – traditional mutations

12 841f06OOmutation22Nov7 Table X – CM mutations

13 841f06OOmutation22Nov7 Coverage The majority of the mutants that the methods fail to kill, indicating inadequacies in the test sets of the methods, are related to program coverage. None of the OO methods explicitly require statement coverage, so it appears that these methods do not execute every statement of the program. This shortcoming can be easily fulfilled by applying traditional coverage methods such as control-flowtesting. In order to be effective, some kinds of coverage methods should be used with the OO methods.

14 841f06OOmutation22Nov7 Results The CM results also show that the OO methods, although they are claimed to be adequate for OO systems, are not particularly effective at dealing with a few OO features, especially the information hiding feature represented by the AMC operator. Special attention is required for those features in the testing of OO software.