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 Jul 2004

Three bills

Apparently there's something of a concerted push to get U.S. voters to contact their congresspeople about the need for verifiable paper trails in computer voting. I contacted mine today. I asked the senators to co-sponsor Senator Ensign's 'Voting Integrity and Verification Act,' # S 2437 or Senator Graham's amendment to HAVA ( # S 1980), and my representative to co-sponsor Rep. Holt's 'Voter Confidence and Increased Accessibility Act,' # HR 2239.

Phone numbers for legislators are easy to find.

Dutiful one that I am, it seems I should study the text of the bills to make sure I agree, but I don't have time. The general thrust seems right, and the crucial thing is to let our representatives know this is an important issue.

## Posted at 16:32 in category /misc [permalink] [top]

Draft Introduction posted

I've finished a draft of the Introduction to Driving Projects with Examples. The introduction is a fictional story of adding a feature to a product. My goal is twofold: to show the tasks involved in example-driven development, and to give a feel for what it should be like to work in such a project. For those with experience, I'm curious how this story compares to your own.

## Posted at 11:31 in category /examplebook [permalink] [top]

Agile Planet

Ian Davis has created an aggregator for Agile blogs called Agile Planet. One-stop shopping for all your agileoblogospheric needs.

## Posted at 08:14 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