lec10 - CPS406 Introduction to Software Engineering Testing...

Info iconThis preview shows pages 1–6. Sign up to view the full content.

View Full Document Right Arrow Icon
3/17/2009 1 CPS406: Introduction to Software Engineering Testing Adapted from: Object-Oriented Software Engineering, T. Lethbridge and R. Laganiere, 2005, Object-Oriented & Classical Software Engineering, S. Schach, 2006, Software Engineering, I. Sommerville, 2006, Software Engineering: An Object-Oriented Perspective, E. Braude, 2001 Overview Testing workflow in unified process Unit testing Integration testing System testing Acceptance testing Writing test cases and test plans Inspection vs. testing 2 Glass-box testing Black-box testing Detecting specific categories of defects
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
3/17/2009 2 Elaboration Unified Process Inception Construction Transition Requirements Analysis Design Implemen- tation 3 Test Unit Tests Integration tests . .. System tests Testing: the Big Picture 3. System test Packages of classes OO: Include use-cases Module combination 2. Integration tests tests 1. 4 Methods Combinations of methods in class Function Module Unit tests
Background image of page 2
3/17/2009 3 Golden Rules of Testing Goal of testing: maximize the number and severity of defects found per dollar spen severity of defects found per dollar spent thus: test early Limits of testing: Testing can only determine the presence of defects, never their absence 5 use proofs of correctness to establish “absence” Unit Testing The art of testing: Select a small, manageable set of test cases to Maximize the chances of detecting a fault while Maximize the chances of detecting a fault, while Minimizing the chances of wasting a test case Every test case must detect a previously undetected fault We need a method that will highlight as many faults as possible First black box test cases (testing to specifications 6 First black-box test cases (testing to specifications) Then glass-box methods (testing to code)
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
3/17/2009 4 Integration Testing Big bang testing versus incremental testing In big bang testing, you take the entire system and test it as a unit A better strategy in most cases is incremental testing : You test each individual subsystem in isolation Continue testing as you add more and more subsystems to the final product 7 Incremental testing can be performed horizontally or vertically , depending on the architecture Horizontal testing can be used when the system is divided into separate sub-applications System Testing System testing for COTS software Alpha, beta testing System testing for custom software The SQA group must ensure that the product passes the acceptance test Failing an acceptance test has bad consequences for the development organization 8
Background image of page 4
3/17/2009 5 System Testing for Custom Software The SQA team must try to approximate the acceptance test Black box test cases for the product as a whole Robustness of product as a whole Stress testing (under peak load) Volume testing (e.g., can it handle large input files?) All constraints must be checked All documentation must be Checked for correctness 9
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 6
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 09/29/2010 for the course COMPUTER S cps615 taught by Professor Pro during the Spring '10 term at Randolph College.

Page1 / 41

lec10 - CPS406 Introduction to Software Engineering Testing...

This preview shows document pages 1 - 6. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online