The document discusses unit testing, defining it as testing the smallest piece of code in isolation. It provides an example of a unit (a math class with an Add method) and unit test (a test method that calls Add and asserts the expected result). It outlines considerations for unit testing like interfaces, data structures, and paths. It describes the unit testing procedure of using a driver and stubs to provide a complete testing environment and isolate the module under test.

1. Unit Testing
Saranya.V
AP/CSE,
Sri Vidya College of Engineering & Technology,
Virudhunagar

2. Definition
• The smallest piece of code software that can
be tested in isolation.

4. This is a Unit
• public class MyMath
• {
• public int Add(int i, int j)
• {
• return i + j;
• }
• }

5. This is a Unit Test
• public void MyAddTest()
• {
• MyMath m = new MyMath();
• Assert.AreEqual(m.Add(2, 3), 5);
• }

6. Unit Test Considerations
Interface
Module Local Data Structure
------------ Boundary Condition
------------ Error Handling Paths
------------ Independent Paths
------------
--------------
Test Cases

7. Unit Test Procedure
• In order to start a unit test, we need a
complete environment to provide all the
necessary things.
Driver
Interface
Module to Local Data Structure
be tested Boundary Condition
Error Handling Paths
Independent Paths
Stub Stub
Results Test Cases

8. • Stubs and drivers are used to provide a
complete environment.
• Stub is a dummy procedure.
• Stub may produce the expected behavior
using a simple table look up mechanism.
• Driver module contains Non Local Data
Structure.

9. Driver Module
Global data
Module Under Test
Stub Module
Unit test follows high cohesion.
Reduced number of test cases.