Testing Dojo Łukasz Kempny Autor: Łukasz KempnyCopyright© Future Processing 2012

What is a Dojo?  Dojo is a Japanese term which literally means "place of the way".  The term can refer to a formal training place for any of the Japanese do arts  Typically it is considered the formal gathering place for students to conduct training, examinations and other related encounters.

What is a Testing Dojo?  Meeting where testers come together to work on a testing challenge.  The testing challenge can consist of testing a product, or generate test ideas for a particular software, or even exercise bug reporting.  Testing without schedule pressures and deadlines.  A way to train testers new to the profession in a collaborative manner.

Equipment  A meeting room large enough for the group  Access to a computer  A video projector so everyone can see what's happening  Pen and paper, a flipchart or a whiteboard to take notes

Roles  Tester has the power over the keyboard and interacts with the software.  Recorder takes session notes and makes sure to get reproducible steps noted down.  Observer (1+) watches the performance, thinks about suggestions for improvements and gives observations about communication.  Facilitator makes sure that the rules of the dojo are followed.

Tester  As the tester has the control over the keyboard, he interacts with the program.  It's crucial for the tester to expose his testing ideas about what to try or not to try and describe his mental model to the audience.

Recorder  The recorder takes session notes about the activities.  In a single tester setup the tester is simultaneously the recorder and he has to take care about his own session notes.  In a paired setup there is a dedicated person for this.

Observers  One or more observers, depending on the size of the group.  The observers take notes about the process (including interactions between tester and recorder or spoken thoughts and test activities).  Observers should monitor the testing activities and the interactions between the pair, rather than watch the screen.

Facilitator  The facilitator picks the mission for the dojo.  Facilitator enforces the rules like switching timeframes.  At the end facilitator moderates the feedback activity.  The facilitator can also take on the role of the tester, recorder or observer.

Mechanics – how it works?  Facilitator starts with introducing rules.  The session facilitator should change so that everyone gets the opportunity to lead a small group of people.  Any testing can be done by a single tester in front of the computer or in a paired setup.  The missions vary between testing a product, evaluating the usage of the following tools or using a new approach to check if we could incorporate it into our testing process.

Single tester  The person with access to the keyboard takes on the role of the tester and the others fulfill the role of observers.  The tester is replaced by another participant from the audience on a previously agreed upon time.  The new tester then continues to follow the mission tackling the product under test.  When the individual tester may get stuck, he may ask for support from the audience.  The tester must explain every step of his thoughts for the observers to follow the individual actions.

Paired session  Two participants sit in front of the computer.  The tester is working on the keyboard, while the recorder writes down the test ideas and discovered bugs.  After a previously agreed timeframe, the tester goes back to the group of observers. The recorder takes over the role of the tester and one of the observers becomes the new recorder.  They need to clarify their steps so that everyone from the observers understands what they're doing.

Missions  Test This  Evaluate Tools  Learn New Approaches

Test this  The classic mission involves testing an application.  The variety of applications includes open source programs, commercial software available in your organization or even your company latest product.  Such a session can end up as a bugfest.  We can focus the session on a particular aspect of the application like usability problems.  We can also pick test automation, though this needs more planning and preparation.

Evaluate tools  A mission to evaluate a tool could use mindmaps for test ideas or try out a particular test tool for the whole session.  The product under test is usually the tool itself, but you can run it also for a common program that you test at work and compare the results directly with your daily work.  Evaluating tools serves mainly the purpose to decide whether or not you may use it on a more regular basis.

Learn new approaches  There are many testing approaches to try out.  You could focus the mission on some particular mnemonic like FCC CUTS VIDS to generate test ideas.  Like tools evaluations, this type of mission aims to try out and learn about new approaches.  After these sessions, the whole team will have made some experience and can make a more informed decision about the usefulness of the approach.

FCC CUTS VIDS  Feature tour  Complexity tour  Claims tour  Variability tour  Interopeability tour  Data tour  Structure tour  Configuration tour  User tour  Testability tour  Scenario tour

Reflection  Take some time after each session to think about it and share observations.  Keep the discussion focused on suggestions (each participant provide specific suggestions of what can be improved).  On a meta-level you should also think about things to change after each dojo. The group should make the decisions.  After the reflection, the team votes for the next facilitator, the time and place for the next dojo.

Summary  Testing Dojos help your team gain a shared understanding of their approaches to testing.  New testers can directly see how a more senior tester would tackle the program, while a more senior tester can get new insights from the fresh perspective of the rookies.  A Testing Dojo conducted with project managers and programmers can bring transparency to testing process.

Links  polsku polsku   

Testing Dojo in FP ?  Monthly meetings?  QA + DEV?  Topics?  Responsible for project? LQA?  Added value?  Meeting place?  Schedule?