Collaborative testingultimateoverview

Collaborative Testing:Catastic Version
Lanette Creamer
Spark Quality LLC
June 2011
Warning: Cat haters, those who are allergic to puns, clownery, and other silly antics which may or may not be fun based on personal taste and mood are advised to tune out while they still can as this version contains maximum cats per slide and is a stress test for the meme tolerance of Mozilla employees. Neither Mozilla nor Lanette will be held responsible for any cats in costumes, or anyone leaving the internet due to cat photo overdose.

Agenda
Intro
Some ways to coordinate collaborative testing that work in practice
Why collaboration?
What does success look like?
Cat collaboration (a.k.a. herding cats)
Q & A
Fun and Games

Well, How Did I Get Here?

Purry-emptive Question
Who is this WE?

Current Testing Frequently Performed
Unit testing (sometimes TDD and/or ATDD)
Code coverage
Reviews and inspections
Functional Automated Tests
Automated Regression Tests
Internationalization/Globalization Tests
Performance Benchmarks
Compatibility Tests (systems, browsers)
Preview Customers (renamed Beta programs)
Got green bar! Cheezburgernaw!

Why This Picture?

The Chaseof the Green Bar
Code Coverage != Product Coverage

What are we missing?

What are we missing?
The User!

Cross Species?
Collaboration What?
Real life collaboration from small to large

Conpurrency Test
What Testers Can Do
Many ideas for the whole org, but this is what can be done by any group with more than one tester or any single tester who can get cooperation from others.

Multiple User Scenario
Load Test
File Throughput Test

Whatever
Uncooperative cat is uncooperative.

Volunteers!
Community is good, when you are stumped.
Or even when you want a different perspective.

A Note on Volunteers
Volunteer testers deserve to be appreciated, respected, and helped to contribute effectively by an activity leader who helps them succeed.*
*More on this later

Area Rotation
Areas of focus switch every # weeks or days.

Tester Pairing
Two testers sit side by side and work together on the same testing challenges.

Bug Hunts
Company wide directive to test some software.

Bug Harvests/Bash
Planned time boxed focus on a feature after a major change or a late fix to get more coverage in a short time period.

Team Exploratory Testing
Time based exploratory test charters are run by individuals, but may be planned by the entire team. Larger team can prioritize, create, review and improve over time.

Workflow Testing
End to End testing across user workflow paths using known data to replicate real users when possible, and personas as a placeholder until more user data is available.

Keeping it Real
End to End test are better when all of the data is as real as we possibly can make it.

Food, Fun, Friends
Complex Teambuilding
Bring the Pizza*
*Exception
No Potlucks
Please.
U bring pizza.
I bring de CRAZIIE!

Prizes

Promote Projects
Useful, Hilarious, Memorable
Fun is still legal! Act now!

User Data

User Inclusion Checklist
Objective Data
Usage data
Studies
Opt In Tracking
Marketing & Product Owners
User testimonials
Existing customer
Potential customers
Optimistic future facing strategy
Sales data
Tech Support
Top Issues
Missed (or deferred) bugs
Dot releases
Usage

Workflow Scorecard Example

Objective User Data Example

Output Examples

Herding Cats
The best laid plans,…

Stardusta.k.a. ChubChub, Chub-a-Love
Some have issues

Tizzy
Some are sweet but shy

Kitty Snuggle Time
With time*, they may grow to like it
* love, patience, band-aids, ice packs, ear plugs, prayer, medication

But you can’t win them all
*Success does not look the same for every team
Ashley

Tasklist Example

We can promote it, but how does this collaborative testing work anyhow? Where are the specifics?
Testing for the User Experience is a technical paper which was voted best paper of PNSQC 2008.
Read it for free at http://blog.testyredhead.com/files/90240-78758/TestingfortheUserExperienceFinal.pdf

Q&A
Lanette.creamer@gmail.com
http://blog.testyredhead.com
Twitter @lanettecream

Testing Gamehttp://mothereffingtextshadow.com/
Email Issues by 6/17/2011 to Lanette.creamer@gmail.com
Non-Harmful, Reproducible, Unique, Hilarious Issues Plz

Collaborative testingultimateoverview

by lanettecream

Accessibility

Categories

Upload Details

Usage Rights

3 Embeds 3

Statistics

Collaborative testingultimateoverview Presentation Transcript

http://twitter.com	1
http://paper.li	1
https://web.tweetdeck.com	1