We’re putting the final touches on submitting the Beautiful Testing manuscript for formatting and copyedit. The order of things might change, but this is how things are shaking out now:

  1. Was it good for you? – Linda Wilkinson brings her unique perspective to the tester’s psyche
  2. Beautiful testing satisfies stakeholders – Rex Black has been been satisfying stakeholders for 25 years. He explains how that is beautiful
  3. Building QA Communities – Open Source projects live and die by their supporting community. Clint Talbert and Martin Schroder share their experiences building a beautiful community of testers.
  4. Collaboration is the Cornerstone to Beautiful Performance Testing – Think performance testing is all about measuring speed? Scott Barber explains why, above everything else, beautiful performance testing needs to be collaborative
  5. Just Peachy: Making Office Software More Reliable with Fuzz Testing – To Kamran Khan, beauty in office suites is in the hiding complexity. Fuzzing is a test technique that follows that same pattern.
  6. Bug Management and Test Case Effectiveness – Brian Nitz and Emily Chen believe that how you track your test cases and bugs can be beautiful. They use their experience with OpenSolaris to illustrate this
  7. Beautiful XMPP Testing – Remko Troncon is deeply involved in the XMPP community. In this chapter he explains how the XMPP protocols are tested and their evolution from ugly to beautiful
  8. Beautiful Large Scale Test Automation – Working at Microsoft, Alan Page knows a thing or two about large scale test automation. He shares some of his secrets to making it beautiful
  9. Beautiful Is Better Than Ugly – Beauty has always been central to the development of Python. Neal Noritz, Michelle Levesque, and Jeffrey Yasskin point out that one aspect of beauty for a programming language is stability, and that achieving it requires some beautiful testing
  10. Testing a random number generator – John D Cook is a mathematician and applies a classic definition of beauty, one based on complexity and unity, to testing random number generators
  11. Change Centric Testing – Testing code that has not changed is neither efficient, nor beautiful says Murali Nandigama; change centric testing is
  12. Software in use – Karen Johnson shares how she tested a piece of medical software that has had direct impact on her non-work life
  13. Software Development is a Creative Process – Chris McMahon was a professional musician before coming to testing. It is not surprising then that he thinks beautiful testing has more to do with jazz bands than manufacturing organizations.
  14. Test Driven Development – Driving New Standards of Beauty – Jennitta Andrea shows how TDD can act as a catalyst for beauty in software projects
  15. Beautiful Testing as the Cornerstone of Business Success – Lisa Crispin discusses how a team’s commitment to testing is beautiful and how that can a key driver of business success
  16. Peeling the Glass Onion at Socialtext – Matt Heusser has worked at a number of different companies in his career, but in this chapter we see why he things his current employer’s process is not just good, but beautiful
  17. Beautiful Testing is Efficient Testing – Beautiful testing has minimal re-testing effort says Adam Goucher. He shares three techniques for to reducing it.
  18. Seeding Bugs to Find Bugs: Beautiful Mutation Testing – Trust is a facet of beauty. The implication is that if you can’t trust you test suite, then your testing can’t be beautiful. Andreas Zeller and David Schuler explain the how you can seed artificial bugs into your product to gain trust in your testing.
  19. Reference Testing as Beautiful Testing – Clint Talbert shows how Mozilla is rethinking their automated regression suite as a tool for anticipatory and forward-looking testing rather than just regression
  20. Clam Anti-Virus: Testing open source with open tools – Tomasz Kojm discusses how the Clam AV team chooses, and uses different testing tools and how the embodiment of the KISS principle is beautiful when it comes to testing.
  21. Web Application Testing with Windmill – Adam Christian gives readers and introduction to the Windmill project and how, while individiual aspects of web automation are not beautiful, their combination is.
  22. Testing One Million Web Pages – Tim Riley sees beauty beauty in the evolution and growth of a test tool that started as something simple and is now anything but.
  23. Testing network services in multi-machine scenarios – When trying for 100% test automation, the involvement of multiple machines for a single scenario can add complexity and non-beauty. Isaac Clerencia showcases ANSTE and how it can increase beauty in this type of testing.