Testing: Chapter 13 "You make it, I’ll break it".

Slides:



Advertisements
Similar presentations
Object Oriented Analysis And Design-IT0207 iiI Semester
Advertisements

Testing Relational Database
Lecture 8: Testing, Verification and Validation
Chapter 12 Prototyping and Testing Design of Biomedical Devices and Systems By Paul H. King Richard C. Fries.
DETAILED DESIGN, IMPLEMENTATIONA AND TESTING Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
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.
System/Software Testing Error detection and removal determine level of reliability well-planned procedure - Test Cases done by independent quality assurance.
1 SOFTWARE TESTING Przygotował: Marcin Lubawski. 2 Testing Process AnalyseDesignMaintainBuildTestInstal Software testing strategies Verification Validation.
1 Software Engineering Lecture 11 Software Testing.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 23 Slide 1 Software testing.
Chapter 9 Testing the System, part 2. Testing  Unit testing White (glass) box Code walkthroughs and inspections  Integration testing Bottom-up Top-down.
Illinois Institute of Technology
Creator: ACSession No: 12 Slide No: 1Reviewer: CSE300Advanced Software EngineeringJanuary 2006 Testing Strategy CSE300 Advanced Software Engineering University.
1 Software Testing and Quality Assurance Lecture 1 Software Verification & Validation.
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.
Types and Techniques of Software Testing
BY RAJESWARI S SOFTWARE TESTING. INTRODUCTION Software testing is the process of testing the software product. Effective software testing will contribute.
Introduction to Computer Technology
©Ian Sommerville 1995 Software Engineering, 5th edition. Chapter 22Slide 1 Verification and Validation u Assuring that a software system meets a user's.
Dr. Pedro Mejia Alvarez Software Testing Slide 1 Software Testing: Building Test Cases.
CSCE 548 Secure Software Development Risk-Based Security Testing.
Software Testing Content Essence Terminology Classification –Unit, System … –BlackBox, WhiteBox Debugging IEEE Standards.
1 Software Testing (Part-II) Lecture Software Testing Software Testing is the process of finding the bugs in a software. It helps in Verifying and.
Chapter 1: Introduction to Software Testing Software Testing
Software Systems Verification and Validation Laboratory Assignment 3 Integration, System, Regression, Acceptance Testing Assignment date: Lab 3 Delivery.
CMSC 345 Fall 2000 Unit Testing. The testing process.
Software Testing Testing principles. Testing Testing involves operation of a system or application under controlled conditions & evaluating the results.
SOFTWARE TESTING Scope of Testing  The dynamic Indian IT industry has always lured the brightest minds with challenging career.
Testing Basics of Testing Presented by: Vijay.C.G – Glister Tech.
Software Development Software Testing. Testing Definitions There are many tests going under various names. The following is a general list to get a feel.
J1879 Robustness Validation Hand Book A Joint SAE, ZVEI, JSAE, AEC Automotive Electronics Robustness Validation Plan The current qualification and verification.
This chapter is extracted from Sommerville’s slides. Textbook chapter
1 Introduction to Software Testing. Reading Assignment P. Ammann and J. Offutt “Introduction to Software Testing” ◦ Chapter 1 2.
Software Testing Definition Software Testing Module ( ) Dr. Samer Odeh Hanna.
Testing, Testing & Testing - By M.D.ACHARYA QA doesn't make software but makes it better.
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.
SOFTWARE TESTING. Introduction Software Testing is the process of executing a program or system with the intent of finding errors. It involves any activity.
Software Testing Mehwish Shafiq. Testing Testing is carried out to validate and verify the piece developed in order to give user a confidence to use reliable.
Software Quality Assurance and Testing Fazal Rehman Shamil.
 Software Testing Software Testing  Characteristics of Testable Software Characteristics of Testable Software  A Testing Life Cycle A Testing Life.
HNDIT23082 Lecture 09:Software Testing. Validations and Verification Validation and verification ( V & V ) is the name given to the checking and analysis.
1 Phase Testing. Janice Regan, For each group of units Overview of Implementation phase Create Class Skeletons Define Implementation Plan (+ determine.
This chapter is extracted from Sommerville’s slides. Textbook chapter 22 1 Chapter 8 Validation and Verification 1.
Software Testing Reference: Software Engineering, Ian Sommerville, 6 th edition, Chapter 20.
SOFTWARE TESTING SOFTWARE TESTING Presented By, C.Jackulin Sugirtha-10mx15 R.Jeyaramar-10mx17K.Kanagalakshmi-10mx20J.A.Linda-10mx25P.B.Vahedha-10mx53.
What is a software? Computer Software, or just Software, is the collection of computer programs and related data that provide the instructions telling.
SOFTWARE TESTING LECTURE 9. OBSERVATIONS ABOUT TESTING “ Testing is the process of executing a program with the intention of finding errors. ” – Myers.
Verification vs. Validation Verification: "Are we building the product right?" The software should conform to its specification.The software should conform.
Software Testing. Purpose: Find errors! not prove that the program does not have them Types of tests: Unit Test Integration Test Function Test Load Test.
SOFTWARE TESTING Date: 29-Dec-2016 By: Ram Karthick.
Product Validation Adapted from the NASA Systems Engineering Handbook for CSULB EE 400D by Alia Bonetti.
PREPARED BY G.VIJAYA KUMAR ASST.PROFESSOR
CSCE 548 Secure Software Development Risk-Based Security Testing
Testing Tutorial 7.
Software Testing.
Rekayasa Perangkat Lunak Part-13
SOFTWARE TESTING OVERVIEW
Quality Management Perfectqaservices.
Verification & Validation
Chapter 10 Verification and Validation of Simulation Models
Lecture 09:Software Testing
Verification and Validation Unit Testing
J1879 Robustness Validation Hand Book A Joint SAE, ZVEI, JSAE, AEC Automotive Electronics Robustness Validation Plan Robustness Diagram Trends and Challenges.
Testing and Test-Driven Development CSC 4700 Software Engineering
Static Testing Static testing refers to testing that takes place without Execution - examining and reviewing it. Dynamic Testing Dynamic testing is what.
Software Testing.
TYPES OF TESTING.
"You make it, I’ll break it"
Presentation transcript:

Testing: Chapter 13 "You make it, I’ll break it"

8/21/2015Page 2 Purpose: Does the product as a whole perform up to specifications? (validation?) Does it perform under normal, upper, and lower limits wrt the environment? Does it meet or exceed all claims (verification)?

Testing defined establishing confidence that a device does what it is supposed to do the process of operating a device with the intent of finding errors detecting specification errors and deviations from the specification 8/21/2015Page 3

Testing continued… verifying that a system satisfies its specified requirements or identifying differences between expected and actual results the process of operating a device or component under specified conditions, observing or recording the results, and making an evaluation of some aspect of the system or component. 8/21/2015Page 4

Testing … Is a positive act of destruction. Is needed for good product development Is necessary for consumer satisfaction… 8/21/2015Page 5

8/21/2015Page 6 Stressors: (depend on requirements…) TemperatureHumidity AltitudeShock VibrationEMI Cell phone, pagersBrownouts ESDSpillage ShippingPower Surges

8/21/2015Page 7 Figure 13-1 Requirements checklist

8/21/2015Page 8 Customer Misuse: Coffee spillage Drop in toilet Use as a seat Cross-connecting Reverse polarity Dirty hands Unplugging via jerk on cable

8/21/2015Page 9 Testing requires that you define failure! Intended application? Anticipated environment? Lifetime? Value vs. time Sunken ships make good coral reefs in time …

8/21/2015Page 10 Types of testing: Event testing – cycling, time to failure Environmental – operating & storage Altitude Threshold (door, elevator, bricks… ) Vibration ISTA shipping test EMI (standards!, see next slide: )

8/21/2015Page 11 EN 1000 series standards Radiated electric field immunity Fast transients Surge, line, magnetic Dips, variations, V, F variation On/off, ESU Walkie-talkie, cell phone ESU, etc.

Failure Definition For each test and for each device, a failure must be defined. This definition depends on the intended application and the anticipated environment. What is considered a failure for one component or device may not be a failure for another. The test protocol should be as detailed as possible in defining the failure. 8/21/2015Page 12

8/21/2015Page 13 We want to test some power supplies to prove a MTBF goal of 50,000 hours of operation. How many units do we test and for how long, assuming one failure and 90% confidence level? (sample size)(test time) = MTBF goal (7.779)/2 (sample size)(test time) = 50,000 (7.779)/2 = 194,475 unit-hours

8/21/2015Page 14 MTBF goal = (sample size)(test time) (2)/Χ 2 α;2r+2 Determining Sample Size and Test Length Confidence level = 1 ‑ α, where α is the risk factor and r = the number of failures Using the 90% confidence level, α = 0.10 & no failures (r=0) (Sample size)(test time) = (MTBF goal)( Χ 2 α;2 )/2 (sample size)(test time) = MTBF goal (4.61)/2 to prove a MTBF goal of 50,000 hours of operation: (sample size)(test time) = 50,000 (4.61)/2 = 115,250 unit-hours Example

Types of Testing: Verification Procedures that attempt to determine that the product of each phase of the development process is an implementation of a previous phase, i.e., it satisfies it. Each verification activity is a phase of the testing life cycle… 8/21/2015Page 15

Types of Testing: Validation Validation is the process of evaluating a system or component during or at the end of the development process to determine whether it satisfies specified requirements

Types of Testing: Black Box Black box testing is a data driven testing scheme. The tester views the device or program as a black box, i.e., the tester is not concerned about the internal behavior and structure. The tester is only interested in finding circumstances in which the device or program does not behave according to its specification 8/21/2015Page 17

Types of Testing: White Box White box testing is concerned with the degree to which test cases exercise or cover the structure of the device or program. The ultimate while box test is an exhaustive path test. 8/21/2015Page 18

Types of testing: Software Module … Integration … System … Acceptance … 8/21/2015Page 19

Types of testing:Fuctional This type of testing verifies that given all the expected inputs then all of the expected outputs are produced. This type of testing is termed success oriented testing because the tests are expected to produce successful results. 8/21/2015Page 20

Types of testing - continued Robustness Testing Stress Testing Safety testing Regression Testing 8/21/2015Page 21

8/21/2015Page 22 Types of testing, continued Life test/reliability Customer misuse Fluid spillage Weight test Keyed connections Time related Failure related (MTBF)

Questions? 8/21/2015Page 23