whole team approach to testing, illustrated

1

The Whole-Team Approach to Testing, Illustrated:

Choosing a New GUI Test Tool

ØREDEV 2012

Lisa CrispinCopyright 2012, Lisa Crispin

Copyright 2012: Lisa Crispin

2

About me…

Tester, agile team member

Agile Testing: A Practical Guide for Testers and Agile Teams; Addison Wesley 2009


Whole-Team Approach is: • Meaningful commitment to quality• Shared vision of product• Diversity of skills, experience, viewpoint


Is this rebellion?What’s rebellious here?

“Control is ultimately held by the doers”

6

A recent example from my last team…


7

A Problem: User Mistakes

Users mis-type bank account numbers => many phone calls for Operations


8

A solution: Dojo

Type-ahead select lists (& other features)


A new problem

We want to help users avoid mistakes, but we can’t have production code that’s not protected by automated tests


Looking to the future…

Dojo would improve UX on our new UI…

Let’s research possible solutions.


Team meeting

Do we need training? Consulting?


Sys admin volunteers to do a spike

Selenium 2 Webdriver does the job!


A framework spike

• Testers research framework options • Sys admin spikes homegrown framework “George”

• Architect spikes open-source framework “Geb”


14

First “Bake-off”

“George” “Geb”


15

Proof of Concept with Geb

• Developers write tests for new UI page

•Testers and sys admin integrate tests into Jenkins CI

• Pros: developers more involved in GUI test design

• Cons: Learning curve for testers, result reporting


16

Time for another experiment


17

Another bake-off

Robot Framework vs. Xebium• Xebium uses FitNesse framework• Robot Framework result reporting excellent


18

Proof of Concept with RF

• Sys admin helps install, integrate w/ Jenkins, customize test results, example page objects

• Testers write tests for same pages as Geb tests

• Friends help with Se 2 keywords


Next Steps

Dojo training

Test design & RF training

Get started in a good direction


Whole Team FTW!

• Team commitment to improve site• Sys admin, architect, developers, testers, DBAs all worked on experiments

• Gave us confidence to experiment, find the best solution for us

• We could go forward with plans to improve UX, reduce user mistakes


Another Experiment, Another Team: API Automation• Team wants to do SBE/ATDD for API• Also need better regression test coverage


Slightly different approach• Tester/dev pair spiked 1 week• Presented results to team• Consensus – too much overlap w/ existing tests

Should have


Second automation spike

• API console• Team consensus – explore, enhance, expand

• Spike for doc generation• Team consensus – go with it

• Continue to build on strategy


Tips for Experimenting

• Divide and conquer• Sub-teams• Time boxed• Pros and Cons• Pof concept

• Rinse and repeat


Your experiences & ideas?

• Has your whole team pulled together to solve a problem?

• Have you tried a “divide and conquer” approach?

• Do you have problems that might be solved more easily if people in multiple positions helped?

What small experiment will YOU try?


27

Some Agile Testing Resources• lisacrispin.com• janetgregory.ca• exampler.com• [email protected]• testobsessed.com• testingreflections.com• dhemery.com• gojko.net• shino.de

28

Agile Testing: A Practical Guide for Testers and Agile Teams

By Lisa Crispin and Janet Gregory

www.agiletester.ca

29

Experiences of Test Automation

Dorothy Graham and Mark Fewster

Copyright 2012: Lisa Crispin Copyright 2008 Janet Gregory, DragonFire

30

Specification by ExampleHow successful teams deliver the right software

Gojko Adzic

Case studies from > 50 teams

Copyright 2012: Lisa Crispin Copyright 2008 Janet Gregory, DragonFire

31

ATDD by ExampleA practical guide to Acceptance Test-Driven development

Markus Gaertner

Copyright 2012: Lisa Crispin 32

All Proceeds to Charity!

Beautiful Testing: Leading Professionals Reveal How They Improve Software

Edited by Tim Riley, Adam Goucher

Includes chapter by yours truly

whole team approach to testing, illustrated

Technology