Talk on ITWeekendDnipro 2018

1. Holy "Test Pyramid"
How it ruins your life

2. About
Yaroslav Pernerovsky
@ysparrow

3. About
https://qaguild-slack.herokuapp.com/

4. About
http://automation-remarks.com/podcast/

5. Unit
Integration
E2E

6. Unit
Integration
E2E
Manual

7. a

11. • http://blog.codepipes.com/testing/software-testing-antipatterns.html

12. Unit
Integration
E2E
White-box
Independent units
Mocks/stubs
White/Black-box
Some deployment
External systems
Black-box
Fully deployed system
Real life scenarios

13. Integration
ü uses database
ü uses network to call another
component/application
ü external system (MQ, mail server etc.)
ü reads/writes files or performs other I/O
ü does not rely on source code, uses
deployed binary instead
http://blog.codepipes.com/testing/software-testing-antipatterns.html

14. What is wrong with
the Pyramid?

15. It is a theoretical
metaphor

16. It is almost
unachievable in
real world

17. Unit
Integration
E2E
Created by
Developers
Sometimes by Developers
Sometimes by Testers
Usually by Testers

19. Contexts differences
Communication issues
Industry stereotypes

20. Developers
should create all
the tests to build
the canonical
test pyramid

22. Become a "developer"
Talk to each other
Brake stereotypes

23. What is wrong with
the tests in
Pyramid?

24. CC=3 CC=2 CC=4++
CC=3 CC=2 CC=4
=9
=24

25. Having the "wrong" kind of tests
Unit
Integration

26. Having the "wrong" kind of tests
Unit
Integration

27. Having the "wrong" kind of tests
Unit
Integration
GUI

28. Testing the wrong functionality
Core
Critical
Other

29. 20%

30. Code coverage

31. Codepipes Testing Metrics (CTM)
Metric Name Description Ideal value Usual value
Problematic
value
PDWT
% of
Developers
writing tests
100% 20%-70%
Anything less
than 100%
PBCNT
% of bugs
that create
new tests
100% 0%-5%
Anything less
than 100%
PTVB
% of tests
that verify
behavior
100% 10%
Anything less
than 100%
PTD
% of tests
that are
deterministic
100% 50%-80%
Anything less
than 100%
http://blog.codepipes.com/testing/software-testing-antipatterns.html

32. 0% 100%Code coverage
effortneeded

33. 0% 100%Code coverage
Valuefromtests

34. Treating TDD as a religion
ü you can write tests before
ü you can write tests at the same time
ü you can write tests after
ü you can never write tests
http://blog.codepipes.com/testing/software-testing-antipatterns.html

35. Itogi podvedyom
ü Triangle is a mental abstraction
ü It should be treated as abstraction
ü Think before act
ü Don't blame yourself
ü Use right metrics
ü Improve your programming skills
ü Right tests over making triangles
ü Do not hesitate to kill shitty tests