But testing is not a routine process, it is a constant exploration methods and is an evolution of good ideas. Beautiful Testing offers 23 essays from 27 leading testers and developers that describe the quality and testing techniques that make art. Through personal anecdotes, you'll learn how each professional develop beautiful ways of testing a wide range of products - valuable knowledge that you can apply to your own project. Here is an example of what you'll find inside: Microsoft's Alan Page knows much about large scale test automation, and shares some secrets on how to make it beautiful Scott Barber explains why performance testing need a collaborative process, not just an exercise in measuring the speed of Karen Johnson's professional experience he describes how his personal life intersected during the test Rex Black medical software reveals how satisfying the stakeholders over the past 25 years is a wonderful thing Mathematician John D. Cook applied the classical definition of beauty, according to the complexity and unity, for testing random number generator All author royalties will be donated to Nothing But Nets campaign to save lives by preventing malaria, a disease that kills millions of children in Africa each year. If you're going to run the test more than 3 times, thinking hard about automating it. This may test # 10, # 35 and # 99. But if you start on test # 1 and methodically work your way to test # 100 you can not get to # 35 and probably not # 99. Always take time to think through testing before jumping in. This includes talking with the developer, spoke through the test with others, and write the plan and asked for feedback. Are tests done _before_ ready features, or at least soon after. Tests carried out a week after the feature is a hundred times better then test a month later. And a thousand times better then the test is 6 months later. Not just to show them the test plan and send a bug report. And they are eager to help you out when developing a test case!