KEY IDEA Use a diversified test strategy that will serve the mission.

Slides:



Advertisements
Similar presentations
Software Testing Technique. Introduction Software Testing is the process of executing a program or system with the intent of finding errors. It involves.
Advertisements

Lecture 8: Testing, Verification and Validation
SOFTWARE TESTING. INTRODUCTION  Software Testing is the process of executing a program or system with the intent of finding errors.  It involves any.
Practical Testing Techniques. Verification and Validation Validation –does the software do what was wanted? “Are we building the right system?” –This.
Using Probing Questions in Mathematics lessons Year 8 Level 5 Assessment Criteria What do you think?
IMSE Week 18 White Box or Structural Testing Reading:Sommerville (4th edition) ch 22 orPressman (4th edition) ch 16.
Management Information Systems. Top level managers Middle level managers Low level managers Operational Tactical Strategic.
Testing an individual module
Design Strategies. Design Strategies: Morphing It’s not always easy to design. We are going to look at a range of tasks that hopefully will help you in.
EE694v-Verification-Lect5-1- Lecture 5 - Verification Tools Automation improves the efficiency and reliability of the verification process Some tools,
BY RAJESWARI S SOFTWARE TESTING. INTRODUCTION Software testing is the process of testing the software product. Effective software testing will contribute.
1 Functional Testing Motivation Example Basic Methods Timing: 30 minutes.
TEST CASE DESIGN Prepared by: Fatih Kızkun. OUTLINE Introduction –Importance of Test –Essential Test Case Development A Variety of Test Methods –Risk.
October 15, 2004 – 1 Welcome IPMA and SolutionsIQ Professional Event Testing, Testing, 1…2…3… Improving software quality -- one bug at a time.
Black Box Software Testing Copyright © 2003 Cem Kaner & James Bach 1 Black Box Software Testing Fall 2004 PART DEVELOPING A PLAN FOR TESTING by Cem.
Copyright (c) Cem Kaner Black Box Software Testing (Academic Course - Fall 2001) Cem Kaner, J.D., Ph.D. Florida Institute of Technology Section:
Agenda Introduction Overview of White-box testing Basis path testing
Tools of Environmental ScienceSection 1 Section 1: Scientific Methods Preview Objectives The Experimental Method Observing Hypothesizing and Predicting.
Word Problems that Lead to Inequalities. Word Problem Solving Strategies Read through the entire problem. Highlight the important information and key.
4H1767 B 1.PPT INTRODUCTION STRATEGIC PLANNING METHOD OVERVIEW SITUATIONAL ANALYSIS POSITION IMPLEMENTATION PROGRAMS GOALS OBJECTIVES CONCLUSIONS PROJECTS.
CSE403 Software Engineering Autumn 2001 More Testing Gary Kimura Lecture #10 October 22, 2001.
1 BUILDING JAVA PROGRAMS CHAPTER 2 Pseudocode and Scope.
Break Out Session Agency/Client/PublisherRelationships.
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Project.
Theory and Practice of Software Testing
Condition Testing. Condition testing is a test case design method that exercises the logical conditions contained in a program module. A simple condition.
Bell Ringer: Draw yourself if you were a superhero.
Chapter 2 sect 1 Objectives List and describe the steps of the experimental method. Describe why a good hypothesis is not simply a guess. Describe the.
 A life cycle of product development is commonly referred as the “model”  A simple model contains five phases  Requirement analysis  Design  Development.
Word problems that lead to inequalities. Word Problem Solving Strategies Read through the entire problem. Highlight the important information and key.
Copyright (c) Cem Kaner. All Rights Reserved. 1 Black Box Software Testing (Professional Seminar) Cem Kaner, J.D., Ph.D. Professor of Computer.
NUR 152 MESA COMMUNITY COLLEGE Communication. Agreeing with the critic’s argument without defensiveness or agreement to change. Examples: A: “You people.
Prepared by: Fatih Kızkun
What is Software Test Automation?
Section 1: Scientific Methods
Put the name of your team here
Software Testing.
Software Engineering (CSI 321)
Section 1: Scientific Methods
Words Matter – Communication Strategies for Success
Quality Management Perfectqaservices.
CHAPTER 4 Test Design Techniques
New S.A.T.’s - Math.
Aim: What is the complex number?
Word problems that lead to inequalities
A test technique is a recipe these tasks that will reveal something
Verification and Validation Unit Testing
READING SQ3R Method.
Solving Differential Equations
Scientific Method 1. State the Problem 2. Research
Objectives List and describe the steps of the experimental method.
3-1 Inequalities and their Graphs
Chapter 7: Checking Comprehension
Day 74 Inequalities problem solving
Solving Differential Equations
How to write good. How to write good Background: Reading Read the papers. Then read them again. Then again. Write out the structure of the paper. If.
CSE403 Software Engineering Autumn 2000 More Testing
Planning longer answers:
Applying Use Cases (Chapters 25,26)
= x 2 = = 20 4 x 5 = = 16 4 x 4 = = 18 6 x 3 = = 12 2 x 6 = 12.
Section 1: Scientific Methods
Changing the Game The Logic Model
Building Health Skills
PSSA Prep Taking a Multiple Choice Test
The Experimental Method
Suitability Test Wednesday, 22 May 2019.
Factors, Primes and Multiples
Lunch and Learn Module:
Action title DUMMY SLIDE DUMMY SLIDE DUMMY SLIDE Situation
Unit III – Chapter 3 Path Testing.
Presentation transcript:

KEY IDEA Use a diversified test strategy that will serve the mission.

Test Strategy “How we plan to cover the product so as to develop an adequate assessment of quality.” A good test strategy is: Product-Specific Risk-focused Diversified Practical

Test Strategy Test Approach and Test Architecture are other terms commonly used to describe what I’m calling test strategy. Example of a poorly stated (and probably poorly conceived) test strategy: “We will use black box testing, cause-effect graphing, boundary testing, and white box testing to test this product against its specification.”

Test Strategy Makes use of test techniques. May be expressed by test procedures and cases. Not to be confused with test logistics, which involve the details of bringing resources to bear on the test strategy at the right time and place. You don’t have to know the entire strategy in advance. The strategy should change as you learn more about the product and its problems.

Test Cases/Procedures Test cases and procedures should manifest the test strategy. If your strategy is to “execute the test suite I got from Joe Third-Party”, how does that answer the prime strategic questions: How will you cover the product and assess quality? How is that practical and justified with respect to the specifics of this project and product? If you don’t know, then your real strategy is that you’re trusting things to work out.

Produce a test strategy for DecideRight Exercise Produce a test strategy for DecideRight

Test Strategy Heuristic: Diverse Half-Measures There is no single technique that finds all bugs. We can’t do any technique perfectly. We can’t do all conceivable techniques. Use “diverse half-measures”-- lots of different points of view, approaches, techniques, even if no one strategy is performed completely.

Strategy Heuristic: Function/Data Square Functions smoke testing Function testing Data reliability testing risk testing

The Fallacy of Repeated Tests: Clearing Mines

Totally Repeatable Tests Won’t Clear the Minefield mines fixes

Variable Tests are Therefore More Effective mines fixes

Exercise Find at least two situations where the heuristic: “Variable tests are better than repeated tests” is WRONG.