Agile Testing Model |
|
Here are James (left) and Bret (right) working the weekend at Ward's Portland, Oregon office.
The question they faced is how does the creativity of the tester mesh with the creativity of the developer day to day throughout a project? There was a sparkling moment when all felt some insight had been reached. That's why the camera came out. Here is a detail of the diagram James is holding.
The diagram shows humans operating a software product through two different interfaces: the gui and the test api. The automation fixtures are a generalization of this framework's Fixtures. That is, software modules that interpret domain oriented specifications under the interactive supervision of (again) a creative human. Although this diagram could describe lots of test automation systems, those systems couldn't be called agile unless the paths ...
Aside on Collaboration: James is particularly interested in generation and insisted it be included in the diagram. His enthusiasm added a lot to the sparkle of the moment. We had been browsing the CalculatorExample and discussing how it was that refreshing the browser cause new test cases to be generated, run and presented. The generator is the jokingly simple http:hp35.cgi that Ward wrote in response to an observation Bret made on this web site at its founding. So Bret encouraged Ward who encouraged James and around again. Such is collaboration.
|
|
Last edited October 16, 2002 Return to WelcomeVisitors |