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

Fri, 04 Aug 2006

Workshop on Agile performance testing - Exeter, England

Posted at the request of Ross Collard, organizer.

WOPR7 is a workshop on agile performance testing. See www.performance-workshop.org for details, including how to apply.

It will be held in Exeter, England on October 12 - 14, 2006 (Thursday - Saturday). WOPR7 is a peer-level mini-conference, invitation-only, deliberately small and collegial, and free. James Bach will conduct a related one-day tutorial on Wednesday, October 11, also free.

Prior WOPR workshops have uniformly been rated outstanding. WOPR6, for example, was held on the Google campus in California last April, and attracted 120 applicants for the 20 seats available.

Some myths may make people ambivalent about applying to attend WOPR7 --

Myth 1.. Travel to the U.K. is a hassle / we do not have a budget for European travel / the food is bad in England. Actually, Exeter is a delightful, semi-medieval university town. The climate will be great in October. So will the camaraderie.

Myth 2.. "In my organization, we do not do agile performance testing and thus do not have any experience reports (ERs) to share on this topic." In response, I ask questions like: "Well, do you test and compare the performance iteratively?", and "Do you have to be agile and respond adroitly to fast changing conditions, often under tight deadlines?" They always say: "Of course! But we do not rigorously follow XP, Scrum, etc."

Myth 3.. "I would like to go to WOPR7 as a participant but have no ER to submit, so I know I will not be selected." We have room for motivated beginners as well as experts.

Myth 4.. "I would like to go to WOPR7 and I do have a story (an ER), but it could not possibly be selected over ones by Harty, Sabourin, Pearl, Barber, etc.". See comment above on myth #3.

## Posted at 07:43 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