This document outlines a practical testing strategy for agile teams. It discusses challenges in agile testing and common principles such as shared responsibility and continuous testing. It recommends treating test automation as software development, with an agile mindset focused on value. The strategy suggests starting automation early to provide feedback, and following practices like code review. It provides tips for different testing activities like static testing, unit testing and performance testing. The overall message is that agile testing requires handling high value parts first, early and frequent testing, and for testing activities to work together continuously with a common strategy.

1. Practical Testing Strategy
for Agile Team
AgileCommunity.tw 組織者 David Ko
開發
建置
測試
上線

2. Who Am I?
2008 Adopt agile in large
organizations
Organizer of
Agile Tour Taipei/
DevOpsDays Taipei
Founder of
the agile community
Good at Design Sprint
David Ko
kojenchieh@gmail.com

3. • Vision
 Committed to making products in a
better way
 It also helps customers make
products in a better way
• Services
 Development & Delivery
 Counseling & Coaching
 Training & Certification
3

4. Agenda
Challenges in Agile/DevOps
Common Principles
Strategy for Test Automation
Tips for Testing Activities
Summary
4

5. 5
The testing was ignored before 2000 AD

6. Testing is ignored until XP appears
6
The reason for being valued is automation
http://www.extremeprogramming.org/map/code.html

7. Agile Testing = Automation?
7
Other testing activities
should not be performed?
Performance Test

8. Test times are often compressed
8
Analysis Design Coding Testing
分析
設計 開發
測試 分析
設計 開發
測試 分析
設計 開發
測試
Testing is not a phase, but how?

9. Is it possible to do all the tests
in a sprint?
9
分析
設計 開發
測試 分析
設計 開發
測試 分析
設計 開發
測試
Performance Test

10. Is that okay without automation?
10
Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5
10
20
30
40
50
60
Sprint 6
The number of features
to be handled
QA
Dev

11. Manual testing doesn't seem to be needed?
11
Do manual testers need to be thrown away?

12. Agenda
Challenges in Agile/DevOps
Common Principles
Strategy for Test Automation
Tips for Testing Activities
Summary
12

13. Common Principles
Team
Responsibility over
QA Responsibility Continuous Testing
over Last Testing
13

14. Skills of Team Members
14
Basic knowledge should be broad
Environment
Unique
technology
needs
to
be
deep
Testing
one
is
not
enough
Communication
More
is
better
More
is
better
Operation
Automation

15. Learn/Do what you don't know
15
Be automated,
or be killed
Testers Developers
Be able to create useful
test cases, or be killed
80/20 principle,
Let the probability be greater than 0

16. Assign by their Capability
16
Senior Testers
80%: manual, 20%: automated
Good at testing
Junior
Testers/Developers
80%: automated, 20%: manual
Good at coding
Balance the schedule
Outcome > output

17. Common Principles
Team
Responsibility over
QA Responsibility Continuous Testing
over Last Testing
17

18. Make good use of static testing
18
Don’t be a gatekeeper

19. Arranging Andon Mechanism
Static
Analysis
Build Install Smoke
Test
Build
1021
Build
1022
Build
1023
Build
1024
Andon = CI + Red Alert + Discipline

20. Plan is nothing, planning is everything
20
1 test case, need 5 mins for execution
1 bug, need 10 min for fixing and testing
100 Test cases, need 5 x 100 mins for execution
20 bugs are found, need 10 x 20 min for fixing and testing
Need 5 x 100 min for regression test
10 bugs are found, need 10 x 10 min for fixing and testing
Need 5 x 100 min for regression test
5 bugs are found, need 10 x 5 min for fixing and testing
Need 5 x 100 min for regression test
Estimation is not accurate because of poor quality

21. Agenda
Challenges in Agile/DevOps
Common Principles
Strategy for Test Automation
Tips for Testing Activities
Summary
21

22. Strategy for Test Automation
22
Treat automation as software
development
Automate with an agile
mindset
Value first over doing everything

23. Need to Follow up Good Practices
23
Code Review Shared Component
Refactoring Source Control

24. Senior Makes the Plan
24
Man that is good at
coding
Develop prototyping first
Define architecture and rules
Man that is not good at
coding/testing
Follow up the samples or rules to
add test cases

25. All People Need to Do Test Automation
25
The boss only knows you have 8 people
But actually only 2 that can write automation

26. Make Good Use of Existing Tools
26
Lots of learning resources, free,
high market share

27. Strategy for Test Automation
27
Treat automation as software
development
Automate with an agile
mindset
Value first over doing everything

28. 28

29. Start early, feedback in time
29
After the function is written, it starts to test
Waterfall Test when
code is done
Time Time
Bug
number
Bug
number

30. Correctness is Important
30
Not much, but accurate and correct

31. Strategy for Test Automation
31
Treat automation as software
development
Automate with an agile
mindset
Value first over doing everything

32. Anti Pattern: Ice Cream Combo
32
Manual Test
UI Test
Integration
Test
Unit
test

33. Test Pyramid
33
UI Test
Integration
Test
Unit test

34. Spirit of Test Pyramid
34
Need different
granularities
The proportion
of the higher level
should be less

35. The Suggested Proportion
35
UI Test
Integration
Test
Unit Test
10%
20%
70%

36. Testing Trophy
36
Integration Test
Unit Test
Static
Test
End-2-End
https://jobs.zalando.com/tech/blog/economic-perspective-testing/?gh_src=4n3gxh1
The more
it resembles
user behavior,
the more confident
it will be
High
Low

37. 大綱
Challenges in Agile/DevOps
Common Principles
Strategy for Test Automation
Tips for Testing Activities
Summary
37

38. Tips for Static Test – Multiple Checks
38
Three Amigos
meeting
UI mockup
review
Architecture
review
Test case review
Don’t rely on certain role or person

39. Tips for Unit Test
• Value first
– frequently used/major features
– Buggy areas
• Add for the part that was not covered before
– Instead of 100% coverage
• Add tests to reproduce bugs
• Execute when codes check-in
39

40. Tips for End-to-End Test
40
Integrate with
CI/CD
Broad first and
then deep
Great Opportunity
 Install/Uninstall
 Upgrade/Downgra
de
 BVT/Major/
Detailed
 Feature complete
 End of Sprint

41. Tips for Exploratory Test
41
Pair/Mob Testing
https://github.com/nairuzabulhul/Technical-Terms/wiki/What-is-Unit-Testing-in-Software-Development-%3F
Bug fixing
Bug Bash
Hardly Reproduce

42. Tips for Performance Test
42
Goal of
Tuning
Time
Proof of
Concept One user
connection
10 K users
connections
100 K user
connections
Progressive tuning
towards higher performance goals

43. Tips for User Acceptance Test
43
Cost
Feedback
Cycle
Low
Short
Long
High
Dev Stage
Later
Early
Sprint Review
Mob
Demo
Internal Beta
Eat Dog
Food
Design Sprint
Concept
Proof
External Beta
Next Version

44. Agenda
Challenges in Agile/DevOps
Common Principles
Strategy for Test Automation
Tips for Testing Activities
Summary
44

45. Agile testing strategy
45
Handle high value parts first
Automation
Early Frequent Value
Each Testing Activities
Work together Continuous
Comon Testing Strategy

46. 46
Agile Testing
does not mean Automation
Rather with Agile Spirit
Change quickly to cope with change

47. Q & A
47