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.
## Posted at 12:47 in category /agile
When is an agile team working up to its potential? (continued)
Some additional suggestions in email comments. (I know, I know, I should
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
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
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
Update to Bang feature of ColumnFixture
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.
|this will fail!
|you can ignore()
|you can check()
|you can expect errors()
some ignored value that shows greyed out
|an expected value
Source is at the
## Posted at 08:20 in category /fit