Book description
This is the digital version of the printed book (Copyright
© 2004).
Testing is not a phase. Software developers should not simply throw
software over the wall to test engineers when the developers have
finished coding. A coordinated program of peer reviews and testing
not only supplements a good software development process, it
supports it.
A good testing life cycle begins during the requirements elucidation phase of software development, and concludes when the product is ready to install or ship following a successful system test.
Nevertheless, there is no one true way to test software; the best one can hope for is to possess a formal testing process that fits the needs of the testers as well as those of the organization and its customers.
A formal test plan is more than an early step in the software testing process—it's a vital part of your software development life cycle. This book presents a series of tasks to help you develop a formal testing process model, as well as the inputs and outputs associated with each task. These tasks include:
review of program plans
development of the formal test plan
creation of test documentation (test design, test cases, test software, and test procedures)
acquisition of automated testing tools
test execution
updating the test documentation
tailoring the model for projects of all sizes
Whether you are an experienced test engineer looking for ways to improve your testing process, a new test engineer hoping to learn how to perform a good testing process, a newly assigned test manager or team leader who needs to learn more about testing, or a process improvement leader, this book will help you maximize your effectiveness.
Table of contents
- About This eBook
- Title Page
- Copyright Page
- Also Available from Dorset House Publishing
- Dedication
- Acknowledgments
- Contents
- Foreword
- Preface
-
Chapter 1. Introduction
- 1.1. Overview
- 1.2. The Software Development Life Cycle
- 1.3. The Formal Testing Life Cycle
- 1.4. Organizational Considerations
- 1.5. The Need for the Process Model
- 1.6. How to Use the Formal Testing Process Model
- 1.7. Input-Process-Output Models
- 1.8. Level 0 IPO Model for Formal Testing
- 1.9. Level 1 IPO Model for Formal Testing
- 1.10. Limitations Inherent in This Book’s Scope
- 1.11. What’s Next?
- Chapter 2. The Formal Testing Process Model: Level 1 IPO Diagrams
-
Chapter 3. Extract Test Information from Program Plans: Levels 2 and 3 IPO Diagrams
- 3.1. Overview
- 3.2. Extract Test Information from Program Plans-Level 2 IPO Diagram
- 3.3. Review Program Management Plan—Level 3 IPO Diagram
- 3.4. Review Quality Assurance Plan—Level 3 IPO Diagram
- 3.5. Review Software Development Plan—Level 3 IPO Diagram
- 3.6. Review Configuration Management Plan—Level 3 IPO Diagram
- 3.7. What’s Next?
- Chapter 4. Create Test Plan: Levels 2 and 3 IPO Diagrams
-
Chapter 5. Create Test Design, Test Cases, Test Software, and Test Procedures: Levels 2 and 3 IPO Diagrams
- 5.1. Overview
- 5.2. Create Test Design, Test Cases, Test Software, and Test Procedures—Level 2 IPO Diagram
- 5.3. Review Test Plan—Level 3 IPO Diagram
- 5.4. Create Test Design—Level 3 IPO Diagram
- 5.5. Review Test Design—Level 3 IPO Diagram
- 5.6. Create Test Cases—Level 3 IPO Diagram
- 5.7. Acquire Test Software-Build—Level 3 IPO Diagram
- 5.8. Acquire Test Software-Buy—Level 3 IPO Diagram
- 5.9. Create Test Procedures—Level 3 IPO Diagram
- 5.10. What’s Next?
-
Chapter 6. Perform Formal Test: Levels 2 and 3 IPO Diagrams
- 6.1. Overview
- 6.2. Perform Formal Test—Level 2 IPO Diagram
- 6.3. Hold Pretest Meeting—Level 3 IPO Diagram
- 6.4. Execute Test—Level 3 IPO Diagram
- 6.5. Determine Disposition of Incidents—Level 3 IPO Diagram
- 6.6. Hold Posttest Meeting—Level 3 IPO Diagram
- 6.7. Write Test Report—Level 3 IPO Diagram
- 6.8. What’s Next?
- Chapter 7. Update Test Documentation: Levels 2 and 3 IPO Diagrams
-
Chapter 8. Tailoring the Model
- 8.1. Overview
- 8.2. Using the Testing Process Model for Large, Safety-Critical, or Profit-Critical Programs
- 8.3. Using the Testing Process Model for Medium-Size Programs
- 8.4. Using the Testing Process Model on Small Projects
- 8.5. Using the Process Model with Extreme Programming
- 8.6. Starting from Scratch
- Chapter 9. Summing Up
- Appendices
- Glossary
- Bibliography
- Index
Product information
- Title: Best Practices for the Formal Software Testing Process: A Menu of Testing Tasks
- Author(s):
- Release date: July 2013
- Publisher(s): Addison-Wesley Professional
- ISBN: 9780133489309
You might also like
book
Managing the Testing Process: Practical Tools and Techniques for Managing Hardware and Software Testing
New edition of one of the most influential books on managing software and hardware testing In …
book
Effective Methods for Software Testing, Third Edition
Written by the founder and executive director of the Quality Assurance Institute, which sponsors the most …
book
Effective Software Testing: 50 Specific Ways to Improve Your Testing
explores fifty critically important best practices, pitfalls, and solutions. Gleaned from the author's extensive practical experience, …
book
Common System and Software Testing Pitfalls: How to Prevent and Mitigate Them: Descriptions, Symptoms, Consequences, Causes, and Recommendations
“Don’s book is a very good addition both to the testing literature and to the literature …