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, 26 May 2004

Agile testing directions: the table of contents

Here is a set of links to my essays on agile testing directions. It's the same as the set on the right, but it's easier to link to.

Introduction
Tests and examples
Technology-facing programmer support
Business-facing team support
Business-facing product critiques
Technology-facing product critiques
Testers on agile projects
Postscript

 

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

When is an agile team working up to its potential? (continued)

(See the original.)

Some additional suggestions in email comments. (I know, I know, I should enable comments.)

  • Everyone on the team has an idea of what other people on the team are working on and can say why that is important work to do.

  • Add "overstressed" to "People should not feel unchallenged or frustrated or overworked."

  • Team are aggressive about adjusting to the changing environment. When things change the team are discussing how to address it in a positive way and not with head in hands crying "we're all doomed".

  • Team are constantly looking to continually optimise their performance and (to avoid local minima) are always looking for ways to make the end to end process more efficient.

  • If you look around the team you find most things are being built just in time, little is just sitting on a shelf waiting to be tested, read, commented on etc. e.g. little untested code lying around.

  • If you look at the end to end process you see a smooth flow of value add activities, all the way from ideas down to delivery. Queue and batch is used minimally, and only where needed.

Thanks to Jeffrey Fredrick, Dadi Ingolfsson, and Andy Schneider.

## Posted at 11:06 in category /agile [permalink] [top]

Update to Bang feature of ColumnFixture

Earlier, I described an update to the Fit ColumnFixture that lets you head a column with a name like "calc!", which means that "calc" is an operation that's not expected to produce any result. (Later columns check what the operation did.)

At Rick Mugridge's suggestion, I've updated it so that "error" tags can be used when the operation is expected to fail. That looks like this:


Normally, the column below the "bang" cell has nothing in it. However, the cells may use the "error" notation if the action is intended to fail. The next three columns show different options for what to do once a setter method fails as expected.

fit.ColumnFixtureBangTester
this will fail!
you can ignore()
you can check()
you can expect errors()
error

some ignored value that shows greyed out
an expected value
error

Source is at the same old place.

## Posted at 08:20 in category /fit [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.

 

Syndication

 

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

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

 

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

 

Join!

Agile Alliance Logo