Lviv Direction QADay 2023 (Experience) КАТЕРИНА АБЗЯТОВА «Optimizing Testing Processes on Practical Cases» telegram: https://t.me/+IJODE0i4X65kNjcy fb: www.fb.com/goqaevent fb: www.fb.com/qaday.org linkedin: https://www.linkedin.com/company/goqa/ Сайт: www.qaday.org

1. Optimizing Testing Processes
on practical cases
September 2023

2. 2
Speaker:
Kateryna Abzyatova,
Senior Manual QA Engineer at Ciklum
● more than 10 years of professional
experience, working as a Manual QA engineer
● tested Desktop, Web, and Mobile applications
● passed 4 ISTQB certifications: Foundations,
Mobile, Agile tester and Advanced Test
Manager

3. 3
01
02
03
3
Onboarding
Agenda
Test Strategy/Test plan
Checklists/Test cases

4. 4
04
05
06
07
4
Defect management
Test execution process
Test reporting
Q&A

5. Onboarding
01

6. 6
01
02
03
From Chaos to Clarity
Missing onboarding checklist with all links
needed
Typical Onboarding Problems
Too short introduction to the product
Missing test documentation and clear
working flow

7. 7
From Chaos to Clarity
What helps?
when you are joining a new team
Writing down all steps,
useful links, tools,
common questions
Create page on
Confluence to collect all
needed information
Double check security
options for storing
passwords, is Google
docs allowed and etc.
Create a list of missed
testing documents,
templates, tips for
product setup, test data
and etc.
01 02 03 04

8. 8
From Chaos to Clarity
If you need to manage newcomers
Trainee/Junior
Help them to understand what’s
important
Create basic algorithm for
questions
Allocate time for review TCs and
testing
Ask for help your
TCoE/unit/Office
Help them grow up and delegate
tasks
Don’t forget that you also were a
beginner ;-)

9. Test Strategy/
Test Plan
02

10. 10
They are fully missing Not up to date
From Chaos to Clarity
Typical problems
with Test Strategy/Test plan
To short and not useful

11. 11
Test Strategy/Test plan
usually covers
- Overall Testing Process
- Types and levels for testing
- Test environments
- Target devices/browsers
- Testing scope
- Risks and mitigation plan
- Workflows for Stories, Bugs, Tasks
- Metrics
- Test Deliverables
- Roles and Responsibilities
- Tools
- DoR/DoD

12. Checklists /
Test cases
03

13. 13
01
02
03
From Chaos to Clarity
Usually created not in Jira: harder to track
Typical problems with Checklists
Not up to date or unclear structure
No understanding of testing detailisation
and real coverage

14. 14
To high
level, not
clear
From Chaos to Clarity
Typical problems with Test cases
Not
updated
Wrote in
different
approaches

15. 15
Analize available
product
documentation
We deliver technology services that reduce cost to serve and provide opportunities
to grow revenue.
When TCs is missing
Create product
structure and
Component list
Create template
for TCs
Discuss priorities with
product owner
Create at least high
level traceability
matrix
Create task for
regression TC creation in
every sprint
for regression
From Chaos to Clarity

16. Defect
management
04

17. 17
From Chaos to Clarity
➢ Big amount of old bugs in BTS
➢ Missing template for Bug creation:
- hard to find existing bug (duplicates creation)
- hard track metrics if some fields are left empty
- different approach for test data providing
➢ Defect left unassigned and no one is working on it long time
Typical problems
with defect management

18. Test
execution
process
05

19. 19
From Chaos to Clarity
The most common inconsistencies:
• new tab/button names,
• new navigations,
• not valid steps according to redesign,
• missing steps,
• different error message text,
• contradictions,
• new elements on screen are not covered by steps.
• Write down all questions and
what is not clear
• Focus on missing test data
• Focus on inconsistencies
Updating Existing TCs during execution

20. 20
Typical test execution problems
● Problems with test environment
● Missing test execution and
visibility of progress
● Missing template for closing
Story/Bug
● Not highlighting risks during
sprint
● Not track changes or new
agreement in User story

21. 21
ACs are not
detailed enough
From Chaos to Clarity
Typical problems
Requirements
were changed
without adding
comment / or
store in several
places
During testing User stories
Developers not
even take a look
on results of
implementation
Incorrect Fix
version/Environ
ment
01 02 03 04

22. Test reporting
06

23. 23
01
02
03
From Chaos to Clarity
Same report for everyone
Typical test reporting problems
Reports that no one read
Missing metrics

24. 24
PO/PM/Team doesn’t
want to implement the
changes
Actions items are not
tracked/implemented
From Chaos to Clarity
Typical problems
with Retrospective
Not everyone is
involved

25. Summary

26. Q&A

27. Thank you!