This document discusses testability and provides advice on several topics related to keeping testability under control, including problem, product, people, proactivity, productivity, pipeline, project, process, and philosophy. For each topic, common issues are identified and recommendations are provided, with an emphasis on taking a whole team approach and focusing on customers, risks, automation, decision making, and continuous improvement.

1. the pop art of
keeping testability
under control.
Tune your P’s
Kateryna Chernikova
Wix, Dnipro

2. Kateryna Chernikova
Wix, Dnipro
QA Guild master
katerynac@wix.com
https://www.linkedin.com/in/ekaterina-chernikova/
https://twitter.com/cykerochka

3. TESTABILITY
Best practice?
Must-have?
Achievable?
Measurable?

4. https://www.menti.com/

6. Problem
Product
People
Proactivity
Productivity
Pipeline
Project
Process
Philosophy
Production issues

7. Enrollment may
(very likely will)
depend on seniority.

8. Choose wisely!
Consume
responsibly.

9. It will cost a pretty
penny.

10. Don’t trust? Just try!

11. Problem
Product
People
Proactivity
Productivity
Pipeline
Project
Process
Philosophy
Production issues

12. PROBLEM
“ They told us to do
so! I’m just a QA,
management
should decide.

13. Problem
➤ Know customers’
needs, expectations,
context

14. ➤ Risks
Problem

15. PRODUCT
Let’s create the
product first, then
we’ll see how to test.

16. Product
➤ QA requirements
for development

17. ➤ “Automatability” -
an ability to be
automated
Data-hooks?
Element IDs?
End-points?
Test services?
Cleaning up?
Product

18. PEOPLE
Any team can
get this job done.

19. People
➤ Diversity matters

20. ➤ Seek for
inspiration around
People

21. ➤ teach`n`learn
Not separately.
People

22. PROACTIVITY
We’re doing good.
Nothing to change
unless we fail.

23. Proactivity
➤ Innovation sprints

24. ➤ Let (make?)
people talk
Proactivity

25. ➤ Retrospect to
become better
Proactivity

26. PRODUCTIVITY
I did so on my
previous project, it
worked like a charm!

27. Productivity
➤ 7 habits of
effective people

28. ➤ Urgency and/or
importance
Productivity

29. ➤ Boost your creativity
Productivity

30. PIPELINE
My changes
pushed. Test report is
coming soon. Or not
soon. Or not coming.

31. Pipeline
➤ Lightweighting loop
over Bureaucracy

32. ➤ Decision making
Pipeline

33. PROJECT
So we get a new FE dev.
Oh, and our QA will help
on other project for a little
while.

34. Project
➤ Reconsider
estimations -
predictability and
accuracy

35. ➤ Resources and
wastes
Project

37. ➤ Space
Project

38. PROCESS
Let’s just start
developing, guys,
camon! Sprint scope is
clear enough. And, btw,
we can save time on
skipping unit tests.

39. Process
➤ DoD and ready

40. ➤ Manage the tech
debt
Process

41. ➤ Tools are just tools.
Even if it is automation :)
Oh no!
He is back to Manual...
Process

42. PHILOSOPHY
Just let
developers develop.
And let testers test!

43. Philosophy
➤ Build a team to
build a product
Can we release
without Regression?
Of course
not

44. ➤ Whole team approach
Philosophy

45. ➤ Leadership,
management,
collaboration
Philosophy

46. PRODUCTION
ISSUES
It is our golden
customer of level 80!
We need to fix all of their
issues asap! No matter
what.

47. Production issues
➤ Controlled amount
of issues

48. ➤ Monitoring
Production issues

49. ➤ POC(s)
Point(s) of Contact
Production issues

50. Product
?. Problem
–. Process
Pipeline
Project
?. Philosophy
–. People
Proactivity
Productivity
Production issues
Have / Missing / Improve

51. WHEN? WHO? WHY?
According to project
development stage and
maturity.
All team as a single unit.
I hope why is not a
question anymore :)

52. Kateryna Chernikova
Wix, Dnipro
QA Guild master
Got a question?
katerynac@wix.com
https://www.linkedin.com/in/ekaterina-chernikova/
https://twitter.com/cykerochka