It is one of the famous excuses for developer not writing unit test. Presented in KTM JS, here I have discussed on what other benefits dev can achieve from unit test apart from problem findings.

1. Achyut Pokhrel
Leapfrog Technology

2. 2

3. 3

4. 4

5. Should you be your own judge?
Do you really need to
write a code to test a code
when you already have a team
dedicated to checking for problems?

6. Unit Test
A unit test is code that tests as small a piece of functionality (the unit) as possible,
in isolation.
Tests ensure:
1. The code meets expectations and specifications: Does what it says it should do.
2. The code continues to meet expectations over time: Avoiding regression.
6

7. 7
we don’t do testing for
production,
we make
code predictable,
scalable &
changeable
tackle the defects in user
workflow,
in the full spectrum of application
functionality

8. ● Problem solving
● Writing code
● Thinking & handling edge cases

9. So, what?
Why it matters?
9

10. Confidence is a key
10
Changing already tested code is both risky and costly.
If we have unit tests in place, then we can proceed for refactoring confidently.

11. Testable code
11
Trouble writing tests? The problem's not in your test suite. It's in your code.

12. 12
Find bug earlier
Easy to enhance in future
Development is faster

13. 13

14. Make process agile
Iterative and Incremental
Continuous Integration / Continuous Delivery

15. 15
Will you be your own judge?

16. 16
Thank you.
Any Queries?