- Copyright
- About the Author
- Acknowledgments
- We Want to Hear from You!
- Introduction
- I. The Big Picture
- 1. Software Testing Background
- 2. The Software Development Process
- 3. The Realities of Software Testing
- Testing Axioms
- It's Impossible to Test a Program Completely
- Software Testing Is a Risk-Based Exercise
- Testing Can't Show That Bugs Don't Exist
- The More Bugs You Find, the More Bugs There Are
- The Pesticide Paradox
- Not All the Bugs You Find Will Be Fixed
- When a Bug's a Bug Is Difficult to Say
- Product Specifications Are Never Final
- Software Testers Aren't the Most Popular Members of a Project Team
- Software Testing Is a Disciplined Technical Profession
- Software Testing Terms and Definitions
- Summary
- Quiz
- Testing Axioms
- II. Testing Fundamentals
- 4. Examining the Specification
- 5. Testing the Software with Blinders On
- 6. Examining the Code
- 7. Testing the Software with X-Ray Glasses
- III. Applying Your Testing Skills
- 8. Configuration Testing
- An Overview of Configuration Testing
- Approaching the Task
- Decide the Types of Hardware You'll Need
- Decide What Hardware Brands, Models, and Device Drivers Are Available
- Decide Which Hardware Features, Modes, and Options Are Possible
- Pare Down the Identified Hardware Configurations to a Manageable Set
- Identify Your Software's Unique Features That Work with the Hardware Configurations
- Design the Test Cases to Run on Each Configuration
- Execute the Tests on Each Configuration
- Rerun the Tests Until the Results Satisfy Your Team
- Obtaining the Hardware
- Identifying Hardware Standards
- Configuration Testing Other Hardware
- Summary
- Quiz
- 9. Compatibility Testing
- 10. Foreign-Language Testing
- 11. Usability Testing
- 12. Testing the Documentation
- 13. Testing for Software Security
- 14. Website Testing
- 8. Configuration Testing
- IV. Supplementing Your Testing
- V. Working with Test Documentation
- VI. The Future
A crash is when your competitor's program dies. When your program dies, it is an “idiosyncrasy.” Frequently, crashes are followed with a message like “ID 02.” “ID” is an abbreviation for “idiosyncrasy” and the number that follows indicates how many more months of testing the product should have had. | ||
| --Guy Kawasaki, “The Macintosh Way” | ||
I love deadlines. I especially like the whooshing sound they make as they go flying by. | ||
| --Douglas Adams, author of “The Hitch Hiker's Guide to the Galaxy” | ||
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.