Editorial Reviews. Review. Review of the first edition: “I think this is a great testing book, both from academic and industrial perspectives. I believe Ammann and. Gary Kaminski, Paul Ammann, Jeff Offutt, Better predicate testing, Proceedings of the 6th International Workshop on Automation of Software. Title: Introduction to software testing / Paul Ammann, George Mason. University, Jeff Offutt, George Mason University. Description: Edition 2. — Cambridge.
|Published (Last):||1 May 2014|
|PDF File Size:||6.41 Mb|
|ePub File Size:||8.31 Mb|
|Price:||Free* [*Free Regsitration Required]|
We think you have liked this presentation.
If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower.
Published by Amie Cooper Modified over 3 years ago. Is a car correct?
Is a subway system correct? Evaluating software by observing its execution Test Failure: Execution of a test that results in a software failure Debugging: The location or locations in the program that contain the fault must be reached Infection: The state of the program must be incorrect Propagation: An IT professional who is in charge of one or more technical test activities Designing test inputs Producing test values Running test scripts Analyzing results Reporting results to developers and managers Test Manager: Amkann the overall functionality of the system Acceptance testing: Is the software acceptable to the user?
Paul Ammann & Jeff Offutt – ppt download
Test each class, file, module, component Integration testing: Test an entire class as sequences of calls method mA1 method mB1 method mA2 method mB2 Inter-method testing: Test pairs of methods in the same class Intra-method testing: A collection of rules and a process that define test requirements Cover every statement Cover every functional requirement Test Requirements: Test Design— a Criteria-Based Design test values to satisfy coverage criteria or other engineering goal This is the most technical job in software testing Requires knowledge of: Test Am,ann b Human-Based Design test values based on domain knowledge of the program and human knowledge of testing This is much harder than it may seem to developers Criteria-based approaches can be blind to special situations Requires knowledge of: Test Automation Embed test values into executable scripts This is slightly less technical Requires knowledge of programming Requires very little theory Often requires solutions to difficult problems related ocfutt observability and controllability Can be boring for test designers Programming is out of reach for many domain experts Who is responsible for determining and embedding the expected outputs?
Test Evaluation Evaluate results of testing, report to developers This is much harder than offutf may seem Requires knowledge of: Sets policy, organizes team, interfaces with development, chooses criteria, decides how much automation is needed, … Test maintenance: Save tests for reuse as software evolves Requires cooperation of test designers and automators Deciding when to trim the test suite is partly policy and partly technical — and in general, very hard!
Tests should be put in configuration control Test documentation: Introduction to Software Testing Chapter 9.
Introduction to Software Testing Chapter 2. Ch 4 The Process page 1CS Building Software is Difficult often delivered late often over budget always with errors must be a custom solution complexity.
Introduction to Software Testing Chapter 1 Introduction Paul Ammann & Jeff Offutt – ppt download