TESTING BASED ON ERROR GUESSING NERINGA SIPAVIČIEN Ė IFM-2/4 It is not actually guessing. Good testers do not guess…

Slides:



Advertisements
Similar presentations
2017/3/25 Test Case Upgrade from “Test Case-Training Material v1.4.ppt” of Testing basics Authors: NganVK Version: 1.4 Last Update: Dec-2005.
Advertisements

Defect testing Objectives
Testing and Quality Assurance
SOFTWARE TESTING. INTRODUCTION  Software Testing is the process of executing a program or system with the intent of finding errors.  It involves any.
1 SOFTWARE TESTING Przygotował: Marcin Lubawski. 2 Testing Process AnalyseDesignMaintainBuildTestInstal Software testing strategies Verification Validation.
1 Software Engineering Lecture 11 Software Testing.
Developer Testing and Debugging. Resources Code Complete by Steve McConnell Code Complete by Steve McConnell Safari Books Online Safari Books Online Google.
Informatics 43 – May 7, Restatement of Goals for Testing Want to verify software’s correctness  Need to test  Need to decide on test cases  No.
Informatics 43 – May 5, Restatement of goals Want to verify software’s correctness  Need to test  Need to decide on test cases  No set of test.
1 CODE TESTING Principles and Alternatives. 2 Testing - Basics goal - find errors –focus is the source code (executable system) –test team wants to achieve.
Informatics 43 – April 30, What is a test case? An input to a system, and the correct output. An “input” may be complex. Example: – What is an input.
Software Testing and Quality Assurance
Testing an individual module
Functional Testing.
Software Testing Prasad G.
Chapter 11: Testing The dynamic verification of the behavior of a program on a finite set of test cases, suitable selected from the usually infinite execution.
1 Functional Testing Motivation Example Basic Methods Timing: 30 minutes.
Test Design Techniques
Ivan Stanchev QA Engineer System Integration Team Telerik QA Academy Telerik QA Academy.
University of Palestine software engineering department Testing of Software Systems Fundamentals of testing instructor: Tasneem Darwish.
Software Quality Assurance Lecture #8 By: Faraz Ahmed.
Chapter 8: Systems analysis and design
Objectives Understand the basic concepts and definitions relating to testing, like error, fault, failure, test case, test suite, test harness. Explore.
Introduction Telerik Software Academy Software Quality Assurance.
CMSC 345 Fall 2000 Unit Testing. The testing process.
The psychology of testing.  The mindset to be used while testing and reviewing is different to that used while developing software.  With the right.
Testing Basics of Testing Presented by: Vijay.C.G – Glister Tech.
Software Testing The process of operating a system or component under specified conditions, observing and recording the results, and making an evaluation.
Introduction to Software Testing. Types of Software Testing Unit Testing Strategies – Equivalence Class Testing – Boundary Value Testing – Output Testing.
Software testing techniques Software testing techniques Equivalence partitioning Presentation on the seminar Kaunas University of Technology.
Chapter 22 Developer testing Peter J. Lane. Testing can be difficult for developers to follow  Testing’s goal runs counter to the goals of the other.
Black-box Testing.
Software Testing Reference: Software Engineering, Ian Sommerville, 6 th edition, Chapter 20.
PROBLEM AREAS IN MATHEMATICS EDUCATION By C.K. Chamasese.
Chapter 1: Fundamental of Testing Systems Testing & Evaluation (MNN1063)
Chapter 8 Testing. Principles of Object-Oriented Testing Å Object-oriented systems are built out of two or more interrelated objects Å Determining the.
Software Engineering1  Verification: The software should conform to its specification  Validation: The software should do what the user really requires.
Test Case Designing UNIT - 2. Topics Test Requirement Analysis (example) Test Case Designing (sample discussion) Test Data Preparation (example) Test.
Software Quality Assurance and Testing Fazal Rehman Shamil.
Dynamic Testing.
1 Phase Testing. Janice Regan, For each group of units Overview of Implementation phase Create Class Skeletons Define Implementation Plan (+ determine.
Boundary Value Testing 1.A type of “Black box” functional testing –The program is viewed as a mathematical “function” –The program takes inputs and maps.
Software Testing Reference: Software Engineering, Ian Sommerville, 6 th edition, Chapter 20.
Mutation Testing Laraib Zahid & Mariam Arshad. What is Mutation Testing?  Fault-based Testing: directed towards “typical” faults that could occur in.
Informatics 43 – May 3, Restatement of goals Want to verify software’s correctness  Need to test  Need to decide on test cases  No set of test.
Verification vs. Validation Verification: "Are we building the product right?" The software should conform to its specification.The software should conform.
CS223: Software Engineering Lecture 25: Software Testing.
TESTING BASED ON ERROR GUESSING Rasa Zavistanavičiūtė, IFME-0/2.
Dynamic Black-Box Testing Part 1 What is dynamic black-box testing? How to reduce the number of test cases using: Equivalence partitioning Boundary value.
Equivalence Partitioning
Software testing techniques TESTING BASED ON ERROR GUESSING
Dr. Rozmie Razif bin Othman
CSCE 548 Secure Software Development Risk-Based Security Testing
PREPARED BY G.VIJAYA KUMAR ASST.PROFESSOR
Equivalence partitioning
Testing Tutorial 7.
Software Testing.
Testing and Debugging PPT By :Dr. R. Mall.
Black Box Testing PPT Sources: Code Complete, 2nd Ed., Steve McConnell
Software Testing An Introduction.
Chapter 8 – Software Testing
Types of Testing Visit to more Learning Resources.
Informatics 43 – May 3, 2016.
Informatics 43 – April 28, 2016.
Test Case Test case Describes an input Description and an expected output Description. Test case ID Section 1: Before execution Section 2: After execution.
Testing techniques and methods
Chapter 1: Boundary Value Testing
Java & Testing.
Chapter 7 Software Testing.
Presentation transcript:

TESTING BASED ON ERROR GUESSING NERINGA SIPAVIČIEN Ė IFM-2/4 It is not actually guessing. Good testers do not guess…

THE PSYCHOLOGY OF TESTING Identifying failures during testing may be perceived as criticism against the product and against the author. Testing is, therefore, often seen as a destructive activity, even though it is very constructive in the management of product risks. Looking for failures in a system requires curiosity, professional pessimism, a critical eye, attention to detail, good communication with development peers, and experience on which to base error guessing. 2Testing based on error guessing

ISTQB GLOSSARY ERROR GUESSING - A test design technique where the experience of the tester is used to anticipate what defects might be present in the component or system under test as a result of errors made, and to design tests specifically to expose them. 3Testing based on error guessing

ERROR GUESSING (1) Perhaps the most widely practiced technique. Tests are derived from the tester’s skill and intuition and their experience with similar applications and technologies. When used to augment systematic techniques, intuitive testing can be useful to identify special tests not easily captured by formal techniques, especially when applied after more formal approaches. 4Testing based on error guessing

ERROR GUESSING (2) However, this technique may yield widely varying degrees of effectiveness, depending on the testers’ experience. A structured approach to the error guessing technique is to enumerate a list of possible errors and to design tests that attack these errors. These defect and failure lists can be built based on experience, available defect and failure data, and from common knowledge about why software fails. Error guessing has no rules for testing, it only uses the tester‘s previous skills. 5Testing based on error guessing

GRAY-BOX Notice that this is what might be called a „gray-box“ test because it requires the tester to have some idea about: typical programming mistakes, how those mistakes become bugs, how those bugs manifest themselves as failures, and how we can force failures to happen. 6Testing based on error guessing

EXAMPLES (1) Date field what the tester think for 30 and 31 date entry, but with having an experience of 5-10 years they get have an intuitions and guess a date for 29 Feb. Division by zero. Submitting a form without entering values. Entering wrong data in the fields and checking software behavior. Entering invalid values (alphabets for digits and vice-versa). 7Testing based on error guessing

EXAMPLES (2) and dot(.) in ids (eg: Ignoring the default maximum and minimum characters to be entered in some fields (that is entering values greater than or less than the expected values). For event driven applications, test multiple processes concurrently. Test using data created through the system or real records, because programmers tend to create data that reflects what they are expecting.... 8Testing based on error guessing

ADVANTAGES Highly successful testers are very effective at quickly evaluating a program and running an attack that exposes defects. Can be used to complement other testing approaches (equivalence partitioning and boundary value analysis). It is more a skill then a technique that is well worth cultivating. It can make testing much more effective. 9Testing based on error guessing

DISADVANTAGES Depends on testers experience: Knowledge of the application under test (AUT); Knowledge of the related testing types done (to understand where defects were found during the test); Knowledge of the integrating applications with their behaviour of response; Knowledge of typical implementation errors (such as division by zero errors); Experience of testing similar or related systems (and knowing where defects have arisen previously in those systems). Can’t be used as only testing method. 10Testing based on error guessing

QUESTIONS 1.What is error guessing? 2.Why error guessing might be called a „gray-box“ test? 3.What are the examples for error guessing? 4.What are rules for error guessing? 5.What are the advantages for error guessing? 11Testing based on error guessing

THANK YOU! 12Testing based on error guessing

REFERENCES Rex Black „Advanced Software Testing Vol. 1“ ISTQB Glossary ISTQB Foundation Level Syllabus Ivan Stanchev, Teleric Academy 13Testing based on error guessing