Emily Bache

Testing is not just for testers any more. One of the most important parts of an agile transition is getting us developers to change our attitude and start writing tests alongside our code. Many teams are adopting a policy of writing unit tests for all new features, and some even plot the rising code coverage at every build. All this testing activity has reverberations around the whole project team, not least for the dedicated testers. What will they do with their day when the software they are given has already passed several thousand automated unit tests? Project managers may start wondering if all these green tests are in fact a green light to ship the product. What if some tests are missing, how would they know? In this talk I'd like to take a look at the big picture of testing on an agile project, and talk about how developers and everyone else on the team should reason about their agile testing strategy.

This is one of several scheduled "fishbowl" discussions, which aim to get the conversation going in this corner of the conference. This particular fishbowl will initially contain Michael Feathers and Geoff Bache. The idea is that you have 5 chairs, you may only speak when you sit on a chair, and one must be empty at all times. If someone sits on the last chair, someone else must get up. The chairs are initially occupied by two or three of the conference speakers, to get the discussion going. Other conference participants are encouraged to join in by sitting on an empty chair. Anyone sitting in the fishbowl who finds they no longer have anything they really want to say, should consider giving up their place.

This is one of several scheduled "fishbowl" discussions, which aim to get the conversation going in this corner of the conference. This particular fishbowl will initially contain Diana Larsen, Jimmy Nilsson and Jurgen Appelo. The idea is that you have 5 chairs, you may only speak when you sit on a chair, and one must be empty at all times. If someone sits on the last chair, someone else must get up. The chairs are initially occupied by two or three of the conference speakers, to get the discussion going. Other conference participants are encouraged to join in by sitting on an empty chair. Anyone sitting in the fishbowl who finds they no longer have anything they really want to say, should consider giving up their place.

This is one of several scheduled "fishbowl" discussions, which aim to get the conversation going in this corner of the conference. This particular fishbowl will initially contain Marcus Ahnve, Niclas Nilsson and Rikard Thulin. The idea is that you have 5 chairs, you may only speak when you sit on a chair, and one must be empty at all times. If someone sits on the last chair, someone else must get up. The chairs are initially occupied by two or three of the conference speakers, to get the discussion going. Other conference participants are encouraged to join in by sitting on an empty chair. Anyone sitting in the fishbowl who finds they no longer have anything they really want to say, should consider giving up their place.

This is one of several scheduled "fishbowl" discussions, which aim to get the conversation going in this corner of the conference. This particular fishbowl will initially contain Henrik Kniberg and Erik Lundh. The idea is that you have 5 chairs, you may only speak when you sit on a chair, and one must be empty at all times. If someone sits on the last chair, someone else must get up. The chairs are initially occupied by two or three of the conference speakers, to get the discussion going. Other conference participants are encouraged to join in by sitting on an empty chair. Anyone sitting in the fishbowl who finds they no longer have anything they really want to say, should consider giving up their place.