This presentation is about how to start from 0 percents of tests coverage and achieved more 85 percents in one year. I have described a couple approaches what I have invented with my Front End team. This presentation shows what work we did with Technical Debt and how our approaches affect team performance and code culture inside the project. Contacts: Facebook: https://www.facebook.com/mykolasavenko LinkedIn: https://www.linkedin.com/in/mykola-savenko/ Instagram: https://www.instagram.com/mykola.savenko/ GitHub: https://github.com/biosis21

1. From
0 to 85
tests
and beyond
Mykola Savenko
Lead Front End Engineer

4. How ?
1. Team acceptance
2. Set short and long term goals
3. Start with 50% of new business features estimation
4. New functionality should be covered > 70%
5. Seek out tech debt, prioritize and plan it
6. Simplify code
7. Write // TODO: test it
8. Team trade offs
9. Test optimization

5. 5
Team
Acceptance

6. 6
• I do not want to do it.
• Why do we need this ?
• What is the benefit of this tests ?
• We will spend a lot of time without business value.
• Time for tests supporting is too critical.

7. 7
Short and long
term goals

8. 8
Goals
Short
• Sprint
• Task
Long
• Program Increment
• 1/2 Year
• Year
> 76%
> 85%
Branch coverage
test strategy
ProductService
ProductModel
+ ~ 2%

9. 9
Code Metrics
Planned goals
before a sprint
start
Achieved
results in the
end of a sprint
Current metric
status

10. 10
50% of new business features
estimation

11. 11
A new functionality
> 70%

12. 12
Seek out,
Prioritize
Plan
technical debt

13. 13
Technical Debt working approach
Seek out PlanPrioritize
WSJF • Add to spreadsheet / Jira
• Setup timeline
• Set owner
up to 20 minutes each day

14. 14
Technical Debt Backlog

15. 15
Just one
more thing …

16. 16
Simplify code

17. 17

18. 18

19. 19
73 loc
15 loc
Before
After

20. 20
Write
// TODO: test it

21. 21

22. 22
Team
Trade offs

23. 23
Test
optimization

24. 24
Test optimization will make a build
potentially complete a lot faster than a
full build and test run
Atlassian

25. 25
1900 MB Memory Allocation 900 MB
Time Running~ 3 min ~ 1 min

26. 26
Don’t do it
• Add to the sprint w/o planning
• Do not merge request w/o tests

27. 27
Benefits are …
• Predictability
• Low barriers to entry
• Manageability
• Less effort implementation
• Readability
• Code understanding

28. 28
85%
50% 9%
5 (9 sp)23 (104 sp)
98
5%
Technical
debt
Test
coverage
Technical debt tasks
Sprints
Technical Progress

29. 29
Technical debt evolution

30. 30
Thank you