Introduction into testing in large and distributed organizations that are practicing agile methods. Ideas, practices and tools to help develop open communication, deal with cultural differences both within an organization and across continents specifically related to testing activities.
1. Janet Gregory, DragonFire Inc.
Copyright 2018
Agile Testers Conference 2018
an on-line experience
Twitter: @janetgregoryca
2. Agile Testing; 2009
More Agile Testing: Oct 2014
Co-authored with Lisa Crispin
https://agiletester.ca
https://agiletestingfellow.com
2
DragonFire Inc.
https://janetgregory.ca
@janetgregoryca
janet@agiletester.ca
3. Some of you will in in organizations that are:
- Less than 100 people
- Larger than 1,000 employees
- Larger than 5,000
- In different cities, same time zone (or 1 hr. apart)
- Have time zones more than 7 hrs difference
- More than 3 remote teams …
3
10. • Bureaucracy
• Reporting needs (real or imagined)
• Orders handed down ….
• Too many concurrent projects
@janetgregoryca
11. • Organizational controls – regulatory, internal
• Working with third parties
• Involving customers in other locations
• ERP system integration
11
@janetgregoryca
15. ReleasePlanning Team A
Planning
Test Mind Map
Team B
Planning
Team C
Planning
Team D
Planning
Release
Test Matrix
Release
Test Planning
/ Approach
16.
17. Lots of Stuff Shopping
Release 1.5
DataIntegrity
Look&Feel
Calculations
Currency
Localization
DevicesiPad
DevicesiPhone
BoundaryConditions
Load/Performance
Security
Store customer information
Add to shopping cart
Calculate shipping costs
Mobile iOs - view only
Next feature
Legend
Good to Go
Some testing; could use more
Major issue
No testing done
Not applicable `
23. Each team responsible
for delivering their
feature -- completely
Specialist teams report
to the “owner” feature
team.
23
24. Over-riding test strategy on how …. but
• Understand who is testing what
• What are the overlaps?
• Where are the gaps?
• Co-ordination between teams?
• ASK: Who, when, how???
24
@janetgregoryca
26. • Classes of tools
• Involve teams in choosing tools
• One size does not fit all
◦ But … be aware of too many tools for support or
cross-training
26
27. • Same version control
◦ Understand the branching and merging approach
• Same CI environment
◦ Use to visualize test results
• Accessible & stable test environments
◦ Know what versions of applications are in each
environment
27
28. Some of the challenges
Plan for testing
Key testing practices that work across teams
28
Sharing is caring
@janetgregoryca
31. • Power of 3
31
• Repeat verbal conversations in writing
• Question
• Draw pictures
• Test ideas
32. • Aim for short feedback cycles
• Remove dependencies early
• Start with a test to remove assumptions
32
@janetgregoryca
33. We can use tests and examples for shared
understanding and common language
For example, create a function to add 2 numbers
-2 + 1 = -1
2.0 + 1.050 = 3.050
2.0 + 1 = 3.0
2 + 1 = 3
36. • What is the state of testability of your
architecture?
◦ Can you simplify it for automation?
• Regulatory
◦ simplest thing you can possibly do
◦ Consider NECESSARY artifacts – can you automate
• Working with third parties (internal / external)
◦ Remove dependencies
◦ Create fast feedback loops
36
37. • Examples (tests) show desired behaviour
• Tests can provide fast feedback
• Remember -- know your team!
37
@janetgregoryca
38. Some of the challenges
Plan for testing
Key testing practices that work across teams
38
Sharing is caring
@janetgregoryca
39. Sharing information, that is
Transparency means less blame
• No hiding
• No secrets
• No gaming the system
The hard part is making it visible
39
@janetgregoryca
40. • Share dependencies
• Same vision
• Same goal
• Accessible to all
• Keep everyone “in
the loop”
40
@janetgregoryca
46. • Schedules
◦ Overlapping times
◦ Meetings
◦ Share the pain
• Use retrospectives
◦ Identify problem areas
◦ Experiment with solutions
46
@janetgregoryca
48. 48
Final note:
I’m not advocating distributed teams or
out-sourcing but if you are faced with those
problems, I hope you can use some of these
ideas to help manage your agile testing.
and
Agile ≠ NO DOCUMENTATION
Know your own context!
49. • Practices for Scaling Lean & Agile Development: Large,
Multisite and Offshore Product Development with Large-Scale
Scrum, Craig Larman and Bas Vodde, Addison-Wesley, 2010
• Agile Software Development in the Large: Diving into the
Deep, Jutta Eckstein, Dorset House, 2004
• More Fearless Change: Patterns for introducing new ideas,
Linda Rising and Mary Lynn Manns
• More Agile Testing: Learning Journeys for the Whole Team,
Janet Gregory and Lisa Crispin, Addison-Wesley, 2015
• Explore It!, Elisabeth Hendrickson, Pragmatic Bookshelf
• Practical Testing in DevOps, Katrina Clokie, LeanPub
49
50. Agile Testing: A Practical Guide for Testers and Agile Teams
More Agile Testing: Learning Journeys for the Whole Team
By Janet Gregory and Lisa Crispin
https://agiletester.ca
https://agiletestingfellow.com
Contact info
www.janetgregory.ca
Email: janet@agiletester.ca
Twitter: janetgregoryca
50
Course: Whole Team Approach to
Agile Testing and Quality