2. Agile Testing; 2009
More Agile Testing: Oct 2014
Co-authored with Lisa Crispin
Website:
www.agiletester.com
www.agiletester.ca
DragonFire Inc.
www.janetgregory.ca
@janetgregoryca
janet@agiletester.ca
2
3. Let’s learn a bit about your experiences
- Less than 100 people
- Larger than 1,000 employees
- Larger than 5,000
- Different cities, same time zone (or 1 hr. apart)
- Time zones more than 7 hrs difference
- More than 3 remote teams
- Others?
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
29. • 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
29
30. • Power of 3
30
• Repeat verbal conversations in writing
• Question
• Draw pictures
• Test ideas
31. • Aim for short feedback cycles
• Remove dependencies early
• Start with a test to remove assumptions
31
@janetgregoryca
32. 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
35. Some of the challenges
Plan for testing
Key testing practices that work across teams
35
Sharing is caring
@janetgregoryca
36. Sharing information, that is
Transparency means less blame
• No hiding
• No secrets
• No gaming the system
The hard part is making it visible
36
@janetgregoryca
37. • Share dependencies
• Same vision
• Same goal
• Accessible to all
• Keep everyone “in
the loop”
37
@janetgregoryca
42. 42
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!
43. 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
www.agiletester.ca
www.agiletester.com
Contact info
www.janetgregory.ca
Email: janet@agiletester.ca
Twitter: janetgregoryca
43
