| |
| |
Preface | |
| |
| |
| |
| |
Beautiful Testers | |
| |
| |
| |
Was It Good For You | |
| |
| |
| |
| |
Beautiful Testing Satifies Stakeholders | |
| |
| |
| |
For Whom Do We Test? | |
| |
| |
What Satisfies? | |
| |
| |
What Beauty Is External? | |
| |
| |
What Beauty Is Internal? | |
| |
| |
Conclusions | |
| |
| |
| |
Building Open Source Qa Communities | |
| |
| |
| |
Communication | |
| |
| |
Volunteers | |
| |
| |
Coordination | |
| |
| |
Events | |
| |
| |
Conclusions | |
| |
| |
| |
Collaboration Is The Cornerstone of Beautiful Performance Testing | |
| |
| |
| |
Settingthe Stage | |
| |
| |
100%?!? Fail | |
| |
| |
The Memory Leak Thai Wasn't | |
| |
| |
Can't Handle the Load? Change the UI | |
| |
| |
It Can't Be the Network | |
| |
| |
Wrap-Up | |
| |
| |
| |
Beautiful Process | |
| |
| |
| |
Just Peachy: Making Office Software More Reliable With Fuzz Testing | |
| |
| |
| |
User Expectations | |
| |
| |
What Is Fuzzing? | |
| |
| |
Why Fuzz Test? | |
| |
| |
Fuzz Testing | |
| |
| |
Future Considerations | |
| |
| |
| |
Bug Management and Test Case Effectiveness | |
| |
| |
| |
Bug Management | |
| |
| |
The First Step in Managing a Defect Is Defining It | |
| |
| |
Test Case Effectiveness | |
| |
| |
Case Study of the OpenSolaris Desktop Team | |
| |
| |
Conclusions | |
| |
| |
Acknowledgments | |
| |
| |
References | |
| |
| |
| |
Beautiful XMMP Testing | |
| |
| |
| |
Introduction | |
| |
| |
XMPP 101 | |
| |
| |
Testing XMPP Protocols | |
| |
| |
Unit Testing Simple Request-Response Protocols | |
| |
| |
Unit Testing Multistage Protocols | |
| |
| |
Testing Session initialization | |
| |
| |
Automated Interoperability Testing | |
| |
| |
Diamond in the Rough: Testing XML Validity | |
| |
| |
Conclusions | |
| |
| |
References | |
| |
| |
| |
Beautiful Large-Scale Test Automation | |
| |
| |
| |
Before We Start | |
| |
| |
What Is Large-Scale Test Automation? | |
| |
| |
The First Steps | |
| |
| |
Automated Tests and Test Case Management | |
| |
| |
The Automated Test Lab | |
| |
| |
Test Distribution | |
| |
| |
Failure Analysis | |
| |
| |
Reporting | |
| |
| |
Putting It All Together | |
| |
| |
| |
Beautiful Is Better Then Ugly | |
| |
| |
| |
The Value of Stability | |
| |
| |
Ensuring Correctness | |
| |
| |
Conclusions | |
| |
| |
| |
Testing A Random Number Generator | |
| |
| |
| |
What Makes Random Number Generators Subtle to Test? | |
| |
| |
Uniform Random Number Generators | |
| |
| |
Nonuniform Random Number Generators | |
| |
| |
A Progression of Tests | |
| |
| |
Conclusions | |
| |
| |
| |
Change-Centric Testing | |
| |
| |
| |
How to set Up the Document-Driven, Change-Centric Testing Framework? | |
| |
| |
Change-Centric Testing for Complex Code Development Models | |
| |
| |
What Have We Learned So Far? | |
| |
| |
Conclusions | |
| |
| |
| |
Software In Use | |
| |
| |
| |
A Connection to My Work | |
| |
| |
From the Inside | |
| |
| |
Adding Different Perspectives | |
| |
| |
Exploratory, Ad-Hoc, and Scripted Testing | |
| |
| |
Multiuser Testing | |
| |
| |
The Science Lab | |
| |
| |
Simulating Real Use | |
| |
| |
Testing in the Regulated World | |
| |
| |
At the End | |
| |
| |
| |
Software Development is a Creative Process | |
| |
| |
| |
Agile Development As Performance | |
| |
| |
Practice, Rehearse, Perform | |
| |
| |
Evaluating the Ineffable | |
| |
| |
Two Critical Tools | |
| |
| |
Software Testing Movements | |
| |
| |
The Beauty of Agile Testing | |
| |
| |
QA Is Not Evil | |
| |
| |
Beauty Is the Nature of This Work | |
| |
| |
References | |
| |
| |
| |
Test-Driven Development: Driving New Standards of Beauty | |
| |
| |
| |
Beauty As Proportion and Balance | |
| |
| |
Agile: A New Proportion and Balance | |
| |
| |
Test-Driven Development | |
| |
| |
Examples Versus Tests | |
| |
| |
Readable Examples | |
| |
| |
Permanent Requirement Artifacts | |
| |
| |
Testable Designs | |
| |
| |
Tool Support | |
| |
| |
Team Collaboration | |
| |
| |
Experience the Beauty of TDD | |
| |
| |
References | |
| |
| |
| |
Beautiful Testing as the Cornerstone of Business Success | |
| |
| |
| |
The Whole-Team Approach | |
| |
| |
Automating Tests | |
| |
| |
Driving Development with Tests | |
| |
| |
Delivering Value | |
| |
| |
A Success Story | |
| |
| |
PostScript | |
| |
| |
| |
Pealing The Glass Onion At Socialtext | |
| |
| |
| |
It's Not Business...It's Personal | |
| |
| |
Tester Remains On-Stage; Enter Beauty, Stage Right | |
| |
| |
Come Walk with Me, The Best Is Yet to Be | |
| |
| |
Automated Testing Isn't | |
| |
| |
Into Socialtext | |
| |
| |
A Balanced Breakfast Approach | |
| |
| |
Regression and Process Improvement | |
| |
| |
The Last Pieces of the Puzzle | |
| |
| |
Acknowledgments | |
| |
| |
| |
Beautiful Testing Is Efficient Testing | |
| |
| |
| |
SLIME | |
| |
| |
Scripting | |
| |
| |
Discovering Developer Notes | |
| |
| |
Oracles and Test Data Generation | |
| |
| |
Mindmaps | |
| |
| |
Efficiency Achieved | |
| |
| |
| |
Beautiful Tools | |
| |
| |
| |
Seeding Bugs to Find Bugs: Beautiful Mutation Testing | |
| |
| |
| |
Assessing Test Suite Quality | |
| |
| |
Watching the Watchmen | |
| |
| |
An AspectJ Example | |
| |
| |
Equivalent Mutants | |
| |
| |
Focusing on Impact | |
| |
| |
The Javalanche Framework | |
| |
| |
Odds and Ends | |
| |
| |
Acknowledgments | |
| |
| |
References | |
| |
| |
| |
Reference Testing as Beautiful Testing | |
| |
| |
| |
Reference Test Structure | |
| |
| |
Reference Test Extensibility | |
| |
| |
Building Community | |
| |
| |
| |
Clam Anti-Virus: Testing Open Source with Open Tools | |
| |
| |
| |
The Clam Anti-Virus Project | |
| |
| |
Testing Methods | |
| |
| |
Summary | |
| |
| |
Credits | |
| |
| |
| |
Web Application Testing With Windmill | |
| |
| |
| |
Introduction | |
| |
| |
Overview | |
| |
| |
Writing Tests | |
| |
| |
The Project | |
| |
| |
Comparison | |
| |
| |
Conclusions | |
| |
| |
References | |
| |
| |
| |
Testing One Million Web Pages | |
| |
| |
| |
In the Beginning... | |
| |
| |
The Tools Merge and Evolve | |
| |
| |
The Nitty-Gritty | |
| |
| |
Summary | |
| |
| |
Acknowledgments | |
| |
| |
| |
Testing Network Services in Multimachine Scenarios | |
| |
| |
| |
The Need for an Advanced Testing Tool in eBox | |
| |
| |
Development of ANSTE lo Improve the eBox QA Process | |
| |
| |
How eBox Uses ANSTE | |
| |
| |
How Other Projects Can Benefit from ANSTE | |
| |
| |
| |
Contributors | |
| |
| |
Index | |