Exploration Through Example

Example-driven development, Agile testing, context-driven testing, Agile programming, Ruby, and other things of interest to Brian Marick
191.8 167.2 186.2 183.6 184.0 183.2 184.6

Wed, 14 Sep 2005

Behind closed doors

It seems that while I've been struggling with a single chapter of Scripting for Testers, Esther Derby and Johanna Rothman have written an entire book: Behind Closed Doors: Secrets of Great Management.

(I think the fourth complete rewrite will nail this chapter & the hardest part of the book. Smooth sailing from then on, he said with a confident grin, unaware of the iceberg looming behind him.)

(Just kidding, by the way: they've been working on this book for quite a while, and I'm sure it will show.)

## Posted at 07:29 in category /misc [permalink] [top]

An agile test plan template

Janet Gregory has provided a sample test plan she's used on agile projects. (In Word and RTF formats.)

It's common for the words "test plan" to be used for a list of descriptions of test cases. (Thus, you sometimes hear people on agile projects responding to the question "Where's your test plan?" by pointing to the automated test suite.) That's never made sense to me.

When I think of test planning, I think in terms of handoffs. At some point, the code is handed off from one set of people to another. For example, a release is a handoff from the production team to the users. That's the main handoff, but a geographically-distributed, multi-team project might have internal handoffs as well.

Everyone should want the receiver of the code to smile. Testing is the activity of predicting whether they actually will smile. Test planning is making sure that everything is in place for that activity to happen smoothly when it's time for it to happen. For example, machines may need to be bought for configuration testing, and the purchasing process may need to start several iterations before the testing starts.

I wrote a paper about that once (PDF).

## Posted at 07:12 in category /agile [permalink] [top]

About Brian Marick
I consult mainly on Agile software development, with a special focus on how testing fits in.

Contact me here: marick@exampler.com.




Agile Testing Directions
Tests and examples
Technology-facing programmer support
Business-facing team support
Business-facing product critiques
Technology-facing product critiques
Testers on agile projects

Permalink to this list


Working your way out of the automated GUI testing tarpit
  1. Three ways of writing the same test
  2. A test should deduce its setup path
  3. Convert the suite one failure at a time
  4. You should be able to get to any page in one step
  5. Extract fast tests about single pages
  6. Link checking without clicking on links
  7. Workflow tests remain GUI tests
Permalink to this list


Design-Driven Test-Driven Design
Creating a test
Making it (barely) run
Views and presenters appear
Hooking up the real GUI


Popular Articles
A roadmap for testing on an agile project: When consulting on testing in Agile projects, I like to call this plan "what I'm biased toward."

Tacit knowledge: Experts often have no theory of their work. They simply perform skillfully.

Process and personality: Every article on methodology implicitly begins "Let's talk about me."


Related Weblogs

Wayne Allen
James Bach
Laurent Bossavit
William Caputo
Mike Clark
Rachel Davies
Esther Derby
Michael Feathers
Developer Testing
Chad Fowler
Martin Fowler
Alan Francis
Elisabeth Hendrickson
Grig Gheorghiu
Andy Hunt
Ben Hyde
Ron Jeffries
Jonathan Kohl
Dave Liebreich
Jeff Patton
Bret Pettichord
Hiring Johanna Rothman
Managing Johanna Rothman
Kevin Rutherford
Christian Sepulveda
James Shore
Jeff Sutherland
Pragmatic Dave Thomas
Glenn Vanderburg
Greg Vaughn
Eugene Wallingford
Jim Weirich


Where to Find Me

Software Practice Advancement


All of 2006
All of 2005
All of 2004
All of 2003



Agile Alliance Logo