Book contents
- Frontmatter
- Contents
- Foreword
- Acknowledgments
- Testing IT
- 1 Introduction
- Part 1 The Traditional Testing Process
- Part 2 The Testing Process in the Real World: Illustrative Case Studies
- Part 3 The Appendices
- A Terms of Reference for Testing Staff
- B Testing Guides
- C Test Plan Document Template
- D Test Specification Document Template
- E Test Script Template
- F Test Result Record Form Template
- G Test Log Template
- H Test Certificate Template
- I Re-use Pack Checklist
- J Test Summary Report Template
- K Equivalence Partition Example
- L Boundary Analysis Example
- M State Transition Example
- N Automated Testing Tool Selection Criteria
- O Usability Testing Overview
- P Testing Process Health Check
- Q The Testing of Object-Oriented Software
- References
- Glossary
- Index
M - State Transition Example
Published online by Cambridge University Press: 06 September 2009
- Frontmatter
- Contents
- Foreword
- Acknowledgments
- Testing IT
- 1 Introduction
- Part 1 The Traditional Testing Process
- Part 2 The Testing Process in the Real World: Illustrative Case Studies
- Part 3 The Appendices
- A Terms of Reference for Testing Staff
- B Testing Guides
- C Test Plan Document Template
- D Test Specification Document Template
- E Test Script Template
- F Test Result Record Form Template
- G Test Log Template
- H Test Certificate Template
- I Re-use Pack Checklist
- J Test Summary Report Template
- K Equivalence Partition Example
- L Boundary Analysis Example
- M State Transition Example
- N Automated Testing Tool Selection Criteria
- O Usability Testing Overview
- P Testing Process Health Check
- Q The Testing of Object-Oriented Software
- References
- Glossary
- Index
Summary
Introduction
This appendix contains a worked example illustrating the testing technique of State Transition analysis described in Chapter 3, which the Test Analyst can use to select specimen data for use in testing the Application Under Test (AUT) as part of the test design process.
The Testing Problem
This example describes part of the specification for the software controlling the operation of a water pump:
▲ The pump can be in one of three states: Isolated, Ready, or Running. The pump cannot start (that is, move to the Running state) if it is Isolated
▲ Opening the water valve will move the pump from the Isolated into the Ready state. Closing the water valve when the pump is Ready will return it to the Isolated state
▲ Pressing a Start button when the pump is in the Ready state will start the pump and move it into the Running state. Pressing a Stop button when the pump is Running will stop the pump and move it into the Ready state.
Analyzing the Testing Requirements
To support the process of analyzing the above requirement, the Test Analyst draws a State Transition diagram to show graphically the states, their transitions, and the events causing those transitions (see Figure M.1).
- Type
- Chapter
- Information
- Testing ITAn Off-the-Shelf Software Testing Process, pp. 259 - 260Publisher: Cambridge University PressPrint publication year: 2001