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, 19 Jul 2006

Agile 2006 Topics

Here are things on my mind these days. If you're at Agile 2006, and you have experience to offer, please let me listen to your story.

  • When people start working on business-facing tests, where do they end up? I'd like to hear stories of what you tried, what you persisted in doing, what you slid back from, what you rightfully rejected.

    (Background: I don't have the same knowledge of the steady state of testing as I do of other aspects of the project. For example, if you told me you have standups, but didn't pair, I'd shrug. Not unusual. If you told me your team always programmed in pairs but didn't have standups, I'd be surprised. For business-facing testing, I don't know what to be surprised at and what to shrug at.)

  • Part of what happens in some Agile projects is a transition from this style of testing:

    to this:

    In the first, there's a limited amount of testing, almost exclusively manual, through the same interface the user uses. The transition is to a lot more automated testing of pieces of the system and fewer end-to-end tests (be they automated, manual exploratory, or a combination). This frequently causes concern: how will we be sure the pieces fit together?

    What happened in your project? Did the concern go away? Was it time that did it, or did you find some other way to convince people? What did you do before the concern went away?

  • Tell me the story of your product director. How uncomfortable was she at the start? What were her big worries? How comfortable did she get? How did that happen?

Thanks. I should be easy to spot. I still look roughly like the picture at the top of the page, though with a mustache and dorky goatee now. Something like this:

## Posted at 16:05 in category /conferences [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