The document discusses unit testing, which involves testing individual functions of code to increase quality and reduce bugs. Unit tests are automated tests written by developers to test standalone functions, provide instant feedback on changes, and increase confidence in the code. However, unit tests only test individual functions and are not relevant for testing non-functional aspects or full integration and end-to-end tests. Maintaining unit tests for frequently changing code can also be time consuming.

1. UNIT TESTING
DAVID TZEMACH
WWW.DTVISIONTECH.COM
FEB 21 2016

2. OVERVIEW
• THE MAIN TARGET OF UNIT TESTING IS TO RUN LOGICAL TESTS ON THE
SMALLEST PIECE OF CODE (A SINGLE FUNCTION AT A TIME).
• UNIT TESTS WILL INCREASE THE QUALITY OF THE CODE AND REDUCE THE
NUMBER OF BUGS ON ADVANCE TESTING PHASES.
• PERFORMED BY THE DEVELOPMENT TEAM (NOT PART OF THE QA
EFFORT).

3. THE BENEFITS OF UNIT TESTING

4. THE FIRST TESTING LAYER
UNIT TESTS ARE THE FIRST LAYER OF TESTS, WHEN EXECUTED WELL,
WE WILL REDUCE THE % TO FIND BUGS ON ADVANCED PHASES OF
THE DEVELOPMENT.

5. INCREASE THE CODE DOCUMENTATION
UNIT TESTS WILL INCREASE THE CODE DOCUMENTATION OF AN
APPLICATION. WHICH WILL HELP OTHER DEVELOPERS TO ACCESS
AND LEARN HOW THE FUNCTION WORKS.

6. INSTANT FEEDBACK
AS A DEVELOPER, YOU HAVE THE POWER TO MODIFY THE CODE AND GET
AN INSTANT APPROVAL REGARDING THE CHANGE, THIS IS A GREAT POWER
THAT WILL INCREASE THE EFFECTIVENESS OF THE DEVELOPMENT PROCESS.

7. UNIT TESTS WILL HELP TO REDUCE THE RISK
UNIT TESTS THAT RUN ALL THE TIME WILL HELP TO FIND A NEW CODE THAT
ACCIDENTALLY ENTERED FROM UNEXPECTED RESOURCES (OTHER TEAMS,
DEVELOPERS FROM THE SAME TEAM ETC.)

8. UNIT TESTS ARE AUTOMATED TESTS!
IT’S SIMPLE, UNIT TESTS ARE AUTOMATED TESTS THAT CAN RUN
WITHOUT ANY LIMITATION FROM THE POINT THAT THE DEVELOPER
AS FINISHED TO WRITE THEM.

9. HELP TO INCREASE THE CONFIDENCE IN CODE
EXECUTING UNIT TESTS IS GREAT TOOL FOR DEVELOPERS TO GAIN
CONFIDENCE IN THEIR CODE (ANY CODE CHANGES WILL BE
VALIDATED STARTING FROM THE POINT THAT THE TEST IS
CREATED).

10. THE LIMITATIONS OF UNIT TESTS

11. SINGLE TESTING LAYER
UNIT TESTS ARE RELEVANT WHEN YOU NEED TO TEST A
STANDALONE FUNCTION, YOU CANNOT RUN THESE TESTS TO
VALIDATE A MORE ADVANCED TESTING LAYER (END TO END,
INTEGRATIONS ETC.).

12. FUNCTIONAL VS. NUN-FUNCTIONAL
UNIT TESTS ARE NOT RELEVANT TO THE NUN-FUNCTIONAL SIDE
OF TESTING AND THEREFORE YOU CANNOT VALIDATE TESTING
TYPES THAT ARE RELATED TO THIS CATEGORY (USABILITY, GUI
ETC.)

13. RELEVANT TO DEVELOPMENT ONLY
UNIT TESTS ARE NOT RELEVANT TO QA, THE PERSONS WHICH
WRITE AND EXECUTE THEM ARE THE DEVELOPERS ONLY, AND
THEREFORE THE QA TEAM CANNOT BASE THEIR TESTS ON THIS
COVERAGE.

14. MAINTENANCE
WORKING ON METHODS THAT FREQUENTLY CHANGED (LIKE
COMPLEX ALGORITHMS) WILL INCREASE THE MAINTENANCE EFFORT
AND THE INVESTMENT OF THE DEVELOPMENT TEAM.

15. TIMELINES
EVERY CODE MAY HOLD THOUSANDS OF METHODS WITH
DIFFERENT COMPLEXITY, THE TIME FACTOR BECOMES HIGHER WHEN
YOU NEED TO DESIGN TEST SCENARIOS FOR ALL OF THOSE
METHODS.

16. FOR ADDITIONAL KB’S PLEASE
VISIT MY BLOG
WWW.DTVISIONTECH.COM