(c) Dr. Wolfgang J. Schneider 2003 - 2006 GENERAL TESTING PRINCIPLES Dr. Wolfgang J. Schneider 2003 – 2006.

Slides:



Advertisements
Similar presentations
Testing Relational Database
Advertisements

Adaptive Testing Technique Ajay Chhokra and Jitender Danwani.
Damian Gordon. Born May 11, 1930 Died August 6, 2002 Born in Rotterdam, Netherlands A Dutch computer scientist, who received the 1972 Turing Award for.
Test process essentials Riitta Viitamäki,
Basic Concepts Snejina Lazarova Senior QA Engineer, Team Lead CRMTeam Dimo Mitev Senior QA Engineer, Team Lead SystemIntegrationTeam Telerik QA Academy.
IS 214 Needs Assessment and Evaluation of Information Systems Managing Usability © Copyright 2001 Kevin McBride.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 23 Slide 1 Software testing.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 23 Slide 1 Software testing.
SE 555 Software Requirements & Specification Requirements Validation.
The Basics of Software Testing
Software Testing Name: Madam Currie Course: Swen5431 Semester: Summer 2K.
FUNDAMENTAL TEST PROCESS
Software Testing Prasad G.
1 CMPT 275 Software Engineering Requirements Analysis Process Janice Regan,
Dr. Wolfgang J. Schneider FUNDAMENTAL TEST PROCESS Dr. Wolfgang J. Schneider 2003 – 2006.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 23 Slide 1 Software testing.
Dr. Wolfgang J. Schneider FUNDAMENTAL TEST PROCESS Dr. Wolfgang J. Schneider 2003 – 2006.
University of Palestine software engineering department Testing of Software Systems Fundamentals of testing instructor: Tasneem Darwish.
1. Topics to be discussed Introduction Objectives Testing Life Cycle Verification Vs Validation Testing Methodology Testing Levels 2.
Chapter 1: Introduction to Software Testing Software Testing
DKT311 Software Engineering Dr. Rozmie Razif bin Othman.
University of Palestine software engineering department Testing of Software Systems Fundamentals of testing instructor: Tasneem Darwish.
CS 217 Software Verification and Validation Week 6, Summer 2014 Instructor: Dong Si
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Error reports as a source for SPI Tor Stålhane Jingyue Li, Jan M.N. Kristiansen IDI / NTNU.
© 2008 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice Testing 29/Apr/2009 Petr Panuška.
Software Testing Testing types Testing strategy Testing principles.
Dr. Wolfgang J. Schneider FUNDAMENTAL TEST PROCESS Dr. Wolfgang J. Schneider 2003 – 2006.
Software Development Life Cycle (SDLC) Presented by The Smartpath Information System An ISO 9001:2008 Certified Organization
QA and Testing. QA Activity Processes monitoring Standards compliance monitoring Software testing Infrastructure testing Documentation testing Usability.
Chapter 1: Fundamental of Testing Systems Testing & Evaluation (MNN1063)
Software Engineering1  Verification: The software should conform to its specification  Validation: The software should do what the user really requires.
Software Quality Assurance SOFTWARE DEFECT. Defect Repair Defect Repair is a process of repairing the defective part or replacing it, as needed. For example,
Software Testing. System/Software Testing Error detection and removal determine level of reliability well-planned procedure - Test Cases done by independent.
Putting Experience to the test
Software Quality Assurance and Testing Fazal Rehman Shamil.
Adaptive Processes © Adaptive Processes Simpler, Faster, Better Defect Testing Testing programs to establish the presence of system defects.
1 Phase Testing. Janice Regan, For each group of units Overview of Implementation phase Create Class Skeletons Define Implementation Plan (+ determine.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 23 Slide 1 Software testing.
IS4500 – SOFTWARE QUALITY ASSURANCE TESTING STRATEGIES Copyright © 2012 by Martin Schedlbauer, Ph.D. All Rights Reserved. Do Not Duplicate or Distribute.
“The Role of Experience in Software Testing Practice” A Review of the Article by Armin Beer and Rudolf Ramler By Jason Gero COMP 587 Prof. Lingard Spring.
SOFTWARE TESTING SOFTWARE TESTING Presented By, C.Jackulin Sugirtha-10mx15 R.Jeyaramar-10mx17K.Kanagalakshmi-10mx20J.A.Linda-10mx25P.B.Vahedha-10mx53.
Week # 4 Quality Assurance Software Quality Engineering 1.
Lecture 3 Software Testing Fundamentals Prof. Mostafa Abdel Aziem Mostafa.
Introduction to Software Testing Maili Markvardt.
Software engineering - 2 Section 8. QUIZ Show how it is possible to determine the height of a tall building with the aid of a barometer.
Testing Integral part of the software development process.
DR. WOLFGANG J. SCHNEIDER GMBH International Information Technology Consultants Dr. Wolfgang J. Schneider Certified IT Consultant.
ISQB Software Testing Section Meeting 10 Dec 2012.
Dr. Rozmie Razif bin Othman
Module A Fundamentals of Testing
SEVERITY & PRIORITY RELATIONSHIP
Unit -1 Fundamentals of Testing Testing principles, Fundamental test process, The psychology of testing
Software Testing An Introduction.
(c) Dr.Wolfgang J. Schneider
Software engineering – 1
BASICS OF SOFTWARE TESTING Chapter 1. Topics to be covered 1. Humans and errors, 2. Testing and Debugging, 3. Software Quality- Correctness Reliability.
UNIT-1 SOFTWARE TESTING FUNDAMENTALS
CS-4349 Software Testing & Implementation
Software Quality Assurance
UNIT-1 SOFTWARE TESTING FUNDAMENTALS
Lecture 09:Software Testing
Software testing.
Introducing ISTQB Agile Foundation Extending the ISTQB Program’s Support Further Presented by Rex Black, CTAL Copyright © 2014 ASTQB 1.
CS240: Advanced Programming Concepts
Summary.
© Oxford University Press All rights reserved.
System analysis and design
Chapter 7 Software Testing.
Introduction to Software Testing
Presentation transcript:

(c) Dr. Wolfgang J. Schneider GENERAL TESTING PRINCIPLES Dr. Wolfgang J. Schneider 2003 – 2006

(c) Dr. Wolfgang J. Schneider Acknowledgement Most of the content has been developed by ISTQB and its affiliates for fair use. The copy right of those parts is with them. The layout has been developed by us.

(c) Dr. Wolfgang J. Schneider General Testing Principles INTRODUCTION Over the past 40+ years, a number of testing principles have been suggested by different authors. They offer general guidelines common for all testing.

(c) Dr. Wolfgang J. Schneider General Testing Principles Testing shows Presence of Defects Testing shows Presence of Defects Exhaustive Testing is Impossible Exhaustive Testing is Impossible Early Testing Early Testing Defect Clustering Defect Clustering Pesticide Paradox Pesticide Paradox Testing is Context Dependent Testing is Context Dependent Absence-of-Errors Fallacy Absence-of-Errors Fallacy

(c) Dr. Wolfgang J. Schneider General Testing Principles Testing shows Presence of Defects Testing shows Presence of Defects Exhaustive Testing is Impossible Exhaustive Testing is Impossible Early Testing Early Testing Defect Clustering Defect Clustering Pesticide Paradox Pesticide Paradox Testing is Context Dependent Testing is Context Dependent Absence-of-Errors Fallacy Absence-of-Errors Fallacy

(c) Dr. Wolfgang J. Schneider General Testing Principles Testing shows Presence of Defects Testing shows Presence of Defects Exhaustive Testing is Impossible Exhaustive Testing is Impossible Early Testing Early Testing Defect Clustering Defect Clustering Pesticide Paradox Pesticide Paradox Testing is Context Dependent Testing is Context Dependent Absence-of-Errors Fallacy Absence-of-Errors Fallacy

(c) Dr. Wolfgang J. Schneider General Testing Principles Testing shows Presence of Defects Testing shows Presence of Defects Exhaustive Testing is Impossible Exhaustive Testing is Impossible Early Testing Early Testing Defect Clustering Defect Clustering Pesticide Paradox Pesticide Paradox Testing is Context Dependent Testing is Context Dependent Absence-of-Errors Fallacy Absence-of-Errors Fallacy

(c) Dr. Wolfgang J. Schneider General Testing Principles Testing shows Presence of Defects Testing shows Presence of Defects Exhaustive Testing is Impossible Exhaustive Testing is Impossible Early Testing Early Testing Defect Clustering Defect Clustering Pesticide Paradox Pesticide Paradox Testing is Context Dependent Testing is Context Dependent Absence-of-Errors Fallacy Absence-of-Errors Fallacy

(c) Dr. Wolfgang J. Schneider General Testing Principles Testing shows Presence of Defects Testing shows Presence of Defects Exhaustive Testing is Impossible Exhaustive Testing is Impossible Early Testing Early Testing Defect Clustering Defect Clustering Pesticide Paradox Pesticide Paradox Testing is Context Dependent Testing is Context Dependent Absence-of-Errors Fallacy Absence-of-Errors Fallacy

(c) Dr. Wolfgang J. Schneider General Testing Principles Testing shows Presence of Defects Testing shows Presence of Defects Exhaustive Testing is Impossible Exhaustive Testing is Impossible Early Testing Early Testing Defect Clustering Defect Clustering Pesticide Paradox Pesticide Paradox Testing is Context Dependent Testing is Context Dependent Absence-of-Errors Fallacy Absence-of-Errors Fallacy

(c) Dr. Wolfgang J. Schneider General Testing Principles Testing shows Presence of Defects Testing shows Presence of Defects Exhaustive Testing is Impossible Exhaustive Testing is Impossible Early Testing Early Testing Defect Clustering Defect Clustering Pesticide Paradox Pesticide Paradox Testing is Context Dependent Testing is Context Dependent Absence-of-Errors Fallacy Absence-of-Errors Fallacy

(c) Dr. Wolfgang J. Schneider General Testing Principles Testing shows Presence of Defects Testing shows Presence of Defects Exhaustive Testing is Impossible Exhaustive Testing is Impossible Early Testing Early Testing Defect Clustering Defect Clustering Pesticide Paradox Pesticide Paradox Testing is Context Dependent Testing is Context Dependent Absence-of-Errors Fallacy Absence-of-Errors Fallacy

(c) Dr. Wolfgang J. Schneider Testing shows Presence of Defects

(c) Dr. Wolfgang J. Schneider Testing shows Presence of Defects Testing can show you that defects are there. Testing cannot prove that there are no defects.

(c) Dr. Wolfgang J. Schneider Testing shows Presence of Defects Testing can show you that defects are there. Testing cannot prove that there are no defects.

(c) Dr. Wolfgang J. Schneider Testing shows Presence of Defects Testing can show you that defects are there. Testing cannot prove that there are no defects.

(c) Dr. Wolfgang J. Schneider Testing shows Presence of Defects

(c) Dr. Wolfgang J. Schneider Testing shows Presence of Defects Testing reduces the probability of undiscovered defects remaining in the software. But, even if no defects are found, it is not a proof of correctness.

(c) Dr. Wolfgang J. Schneider Testing shows Presence of Defects Testing reduces the probability of undiscovered defects remaining in the software. But, even if no defects are found, it is not a proof of correctness.

(c) Dr. Wolfgang J. Schneider Testing shows Presence of Defects Testing reduces the probability of undiscovered defects remaining in the software. But, even if no defects are found, it is not a proof of correctness.

(c) Dr. Wolfgang J. Schneider Testing shows Presence of Defects Testing cannot prove that there are no defects. If no defects are found, it is not a proof of correctness.

(c) Dr. Wolfgang J. Schneider Exhaustive Testing is Impossible

(c) Dr. Wolfgang J. Schneider Exhaustive Testing is Impossible Testing everything (all combinations of inputs and preconditions) is not feasible except for trivial cases. Instead of exhaustive testing, we use risk and priorities to focus testing efforts.

(c) Dr. Wolfgang J. Schneider Exhaustive Testing is Impossible Testing everything (all combinations of inputs and preconditions) is not feasible except for trivial cases. Instead of exhaustive testing, we use risk and priorities to focus testing efforts.

(c) Dr. Wolfgang J. Schneider Exhaustive Testing is Impossible Testing everything (all combinations of inputs and preconditions) is not feasible except for trivial cases. Instead of exhaustive testing, we use risk and priorities to focus testing efforts.

(c) Dr. Wolfgang J. Schneider Exhaustive Testing is Impossible Testing everything (all combinations of inputs and preconditions) is not feasible except for trivial cases. Instead of exhaustive testing, we use risk and priorities to focus testing efforts.

(c) Dr. Wolfgang J. Schneider Early Testing

(c) Dr. Wolfgang J. Schneider Early Testing Testing activities should start as early as possible in the software or system development life cycle They should be focused on defined objectives

(c) Dr. Wolfgang J. Schneider Early Testing Testing activities should start as early as possible in the software or system development life cycle They should be focused on defined objectives

(c) Dr. Wolfgang J. Schneider Early Testing Testing activities should start as early as possible in the software or system development life cycle They should be focused on defined objectives

(c) Dr. Wolfgang J. Schneider Early Testing Testing activities should start as early as possible in the software or system development life cycle They should be focused on defined objectives

(c) Dr. Wolfgang J. Schneider Early Testing Testing activities should start as early as possible in the software or system development life cycle They should be focused on defined objectives

(c) Dr. Wolfgang J. Schneider Defect Clustering

(c) Dr. Wolfgang J. Schneider Defect Clustering A small number of modules contain most of the defects discovered during pre-release testing, or show the most operational failures.

(c) Dr. Wolfgang J. Schneider Defect Clustering A small number of modules contain most of the defects discovered during pre-release testing, or show the most operational failures. A SMALL NUMBER OF MODULES CONTAIN MOST OF THE DEFECTS

(c) Dr. Wolfgang J. Schneider Pesticide Paradox

(c) Dr. Wolfgang J. Schneider Pesticide Paradox If the same tests are repeated over and over again, eventually the same set of test cases will no longer find any new bugs.

(c) Dr. Wolfgang J. Schneider Pesticide Paradox Most vintage testers call this the Mine Field Effect Mine Field Effect

(c) Dr. Wolfgang J. Schneider Pesticide Paradox To overcome this effect, the test cases need to be regularly reviewed and revised, and new and different tests need to be written to exercise different parts of the software or system to potentially find more defects.

(c) Dr. Wolfgang J. Schneider Testing is Context Dependent Testing is done differently in different contexts. For example, safety-critical software is tested differently from an e-commerce site.

(c) Dr. Wolfgang J. Schneider Testing is Context Dependent Testing is done differently in different contexts. For example, safety-critical software is tested differently from an e-commerce site.

(c) Dr. Wolfgang J. Schneider Testing is Context Dependent Testing is done differently in different contexts. For example, safety-critical software is tested differently from an e-commerce site.

(c) Dr. Wolfgang J. Schneider Testing is Context Dependent Testing is done differently in different contexts. For example, safety-critical software is tested differently from an e-commerce site.

(c) Dr. Wolfgang J. Schneider Testing is Context Dependent Testing is done differently in different contexts. For example, safety-critical software is tested differently from an e-commerce site. RISK

(c) Dr. Wolfgang J. Schneider Absence-of-Errors Fallacy Finding and fixing defects does not help if the system built is unusable and does not fulfill the users needs and expectations and expectations

(c) Dr. Wolfgang J. Schneider Absence-of-Errors Fallacy Finding and fixing defects does not help if the system built is unusable and does not fulfill the users needs and expectations

(c) Dr. Wolfgang J. Schneider Absence-of-Errors Fallacy Finding and fixing defects does not help if the system built is unusable and does not fulfill the users needs and expectations

(c) Dr. Wolfgang J. Schneider GENERAL TESTING PRINCIPLES

(c) Dr. Wolfgang J. Schneider General Testing Principles Testing shows Presence of Defects Testing shows Presence of Defects Exhaustive Testing is Impossible Exhaustive Testing is Impossible Early Testing Early Testing Defect Clustering Defect Clustering Pesticide Paradox Pesticide Paradox Testing is Context Dependent Testing is Context Dependent Absence-of-Errors Fallacy Absence-of-Errors Fallacy

DR. WOLFGANG J. SCHNEIDER GMBH International Information Technology Consultants Professional Testing Solutions Telecommunications and Utility Billing Systems Euro Preparation for Companies in New EU Member Countries EDIFACT – DATANORM – ELDANORM – ETIM Interfaces Data Exchange with Banks and Credit Card Companies Total Quality Management – Good Manufacturing Practices IT Service Management - IT Infrastructure Library (ITIL) Knowledge Management Solutions IT Fitness for GAAP – IAS – FASB Balanced Scorecard Take Advantage of 30+ Years of IT Experience ! Dr. Wolfgang J. Schneider - Start