Nice discussion of white box and developer-driven testing in Google Chrome comic book

I debated copying the scans from blogoscoped.com or referencing the images here, but I decided instead to refer you to the appropriate pages to be a good blog citizen.

Getting Scott McCloud to write a comic book announcing your product is a great idea. He did a great job distilling some complicated stuff into a very accessible piece. Tons of people will talk about the Google Chrome announcement and what it means for Microsoft and about using multiple processes for tabs.

One of the things that struck me though, was the nice discussion of white box automated testing. Also, a very simple and concise description of developer-driven testing. I am a huge proponent of these principles since I first worked on an XP project 8 years ago and became an XP coach. Every project I’ve worked on since has had a large test-driven development component and hard-core whitebox QEs (when I’ve had the resources). Doing automated stress testing on a browser is a no-brainer. Internet Explorer has been doing it forever. Google isn’t doing anything new or different here: fuzzing inputs isn’t new, and neither is reducing the test space to make automation run faster and results relevant for users. However, McCloud’s comic does a great job of explaining these ideas in a very simple manner. It’s a great tool for developers, QEs or engineering managers trying to explain why these things are important to others in their organization.

Check it out on pages 9, 10, and 11 of the Google Chrome comic book.

Leave a Reply

Your email address will not be published. Required fields are marked *