This document describes a collaborative testing presentation titled "Collaborative Testing: Catastic Version" which warns that it contains many cat-related jokes and images that some may find silly or excessive. It provides an agenda for the presentation covering introduction, coordination of collaborative testing, reasons for collaboration, what success looks like, and "cat collaboration". The document gives examples of current testing practices and their limitations. It proposes several ways teams can collaborate on testing, such as pairing testers, planning bug hunts, and testing end-to-end workflows using real user data. The presentation advocates making testing fun through activities like contests and team building. It acknowledges that not all individuals or teams will collaborate in the same way and that herding

1. 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.

2. 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

3. Well, How Did I Get Here?

4. Well, How Did I Get Here?

5. Purry-emptive Question Who is this WE?

7. Code coverage

8. Reviews and inspections

9. Functional Automated Tests

10. Automated Regression Tests

11. Internationalization/Globalization Tests

12. Performance Benchmarks

13. Compatibility Tests (systems, browsers)

14. Preview Customers (renamed Beta programs)Got green bar! Cheezburgernaw!

16. Code coverage

17. Reviews and inspections

18. Functional Automated Tests

19. Automated Regression Tests

20. Internationalization/Globalization Tests

21. Performance Benchmarks

22. Compatibility Tests (systems, browsers)

23. Preview Customers (renamed Beta programs)Got green bar! Cheezburgernaw!

24. Why This Picture?

25. The Chaseof the Green Bar Code Coverage != Product Coverage

26. What are we missing?

27. What are we missing? The User!

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

29. 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.

30. Multiple User Scenario Load Test File Throughput Test

31. Whatever Uncooperative cat is uncooperative.

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

33. 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

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

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

36. Bug Hunts Company wide directive to test some software.

37. 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.

38. 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.

39. 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.

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

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

42. Prizes

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

44. User Data

46. Studies

48. Existing customer

49. Potential customers

50. Optimistic future facing strategy

52. Missed (or deferred) bugs

53. Dot releases

55. Objective User Data Example

56. Output Examples

57. Output Examples

58. Output Examples

59. Output Examples

60. Output Examples

61. Output Examples

62. Output Examples

63. Output Examples

64. Output Examples

65. Herding Cats The best laid plans,…

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

67. Tizzy Some are sweet but shy

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

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

70. Tasklist Example

71. Tasklist Example

72. 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

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

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