Why patterns?
Patterns are a way of helping people who design things. They were formalized by the architect Christopher Alexander. When done well, patterns accomplish at least three things:
They provide a vocabulary for problem-solvers. "Hey, you know, we should use a Null Object."
They focus attention on the forces behind a problem. That allows designers to better understand when and why a solution applies.
They encourage iterative thinking. Each solution creates a new context in which new problems can be solved.
Why test patterns?
We believe that testers lack a useful vocabulary, are hampered by rigid "one size fits all" methodologies, and face many problems whose solutions are underdescribed in the literature. Patterns can help with all of those things.
Moreover, the community of pattern writers is a healthy one that regularly spawns new and useful ideas. We testers should link up with it, and we might find its style of work useful as we look for new ideas.
What happens at the workshops?
We read (or "workshop") patterns to help their authors better express and understand them. This is an essential community-building activity.
We write patterns, individually or in pairs.
We talk about patterns. And other things
Applying Patterns to Software Testing