Introduction

Unit testing is the process of testing a small individual part of a program to check whether it works correctly.

A unit can be a function, method, class, module, or any small piece of logic that can be tested independently.

In real software development, unit testing is usually one of the first levels of testing. It helps developers catch problems early before the code is combined with other modules.

Easy Real-Life Example

Bicycle:
Check brake
Check tyre
Check chain
Check bell

Software:
Test login function
Test calculation function
Test validation function
Test search function

Unit testing works in the same way. It checks small parts before trusting the complete system.

What is a Unit?

A unit is the smallest testable part of a program.

The exact meaning of a unit depends on the programming language and project design, but commonly it means a function, method, class, or small module.

What is Unit Testing?

Unit testing checks whether a single unit of code produces the expected result for given input.

It usually compares the actual output of the unit with the expected output.

Simple Example

Function:
isPassingMark(marks)

Requirement:
Return true if marks are 40 or above.

Input:
marks = 50

Expected Output:
true

Actual Output:
true

Result:
Test Passed

Why Unit Testing is Important

Unit testing is important because it helps find bugs early in the development process.

When a bug is found in a small function, it is usually easier to understand and fix than a bug found after the complete system is built.

Unit Testing in the Testing Levels

Unit testing is usually the first level of software testing.

Unit Testing
    ↓
Integration Testing
    ↓
System Testing
    ↓
Acceptance Testing

Unit testing checks individual parts. Integration testing checks how parts work together. System testing checks the full system. Acceptance testing checks whether the users accept the software.

Example: Function to Test

Suppose we have a function that calculates whether a student passes or fails.

FUNCTION isPassingMark(marks)
    IF marks >= 40 THEN
        RETURN true
    ELSE
        RETURN false
    END IF
END FUNCTION

We can write unit tests for this function using different inputs.

Unit Test Cases for the Function

Unit Testing Process

Unit testing can be followed as a simple step-by-step process.

1. Identify the unit to test
2. Understand expected behavior
3. Prepare test data
4. Execute the unit
5. Compare actual result with expected result
6. Mark test as pass or fail
7. Fix defects if needed
8. Re-run the test

Expected Result vs Actual Result

Unit testing compares what should happen with what actually happens.

AAA Pattern in Unit Testing

A common way to structure unit tests is the AAA pattern.

AAA stands for Arrange, Act, and Assert.

AAA Example in Pseudocode

TEST "Marks 50 should return true"

    // Arrange
    marks = 50
    expectedResult = true

    // Act
    actualResult = isPassingMark(marks)

    // Assert
    CHECK actualResult == expectedResult

END TEST

The AAA pattern makes tests clean, readable, and easy to understand.

Positive, Negative, and Boundary Unit Tests

Good unit tests should check different types of scenarios.

Boundary Values in Unit Testing

Boundary values are very important because many bugs happen near limits.

Requirement:
Marks must be from 0 to 100.

Important unit test values:
-1   → invalid
0    → valid
1    → valid
39   → fail
40   → pass
100  → valid
101  → invalid

These values help test both valid and invalid edges.

Manual Unit Testing vs Automated Unit Testing

Unit testing can be done manually, but in professional projects it is commonly automated using testing frameworks.

Unit Testing Frameworks

A unit testing framework helps developers write, run, and organize unit tests.

Different programming languages have different testing frameworks.

The concept of unit testing is language-neutral, even if the tools are different.

Example: Unit Testing a Calculator Function

Function

FUNCTION addNumbers(firstNumber, secondNumber)
    RETURN firstNumber + secondNumber
END FUNCTION

Unit Tests

TEST "Add two positive numbers"
    // Arrange
    firstNumber = 5
    secondNumber = 3
    expectedResult = 8

    // Act
    actualResult = addNumbers(firstNumber, secondNumber)

    // Assert
    CHECK actualResult == expectedResult
END TEST

TEST "Add positive and negative number"
    // Arrange
    firstNumber = 5
    secondNumber = -3
    expectedResult = 2

    // Act
    actualResult = addNumbers(firstNumber, secondNumber)

    // Assert
    CHECK actualResult == expectedResult
END TEST

These tests verify that the addition function works for different inputs.

Real-World Example: Shopping Cart Unit Tests

In an e-commerce application, a shopping cart may have many small units to test.

Student-Friendly Example: Grade Calculator Unit Tests

Function:
calculateGrade(marks)

Rules:
90 to 100 → A
75 to 89  → B
60 to 74  → C
40 to 59  → D
Below 40  → Fail
Invalid if marks are below 0 or above 100

Unit Test Cases:
marks = 95  → A
marks = 75  → B
marks = 60  → C
marks = 40  → D
marks = 39  → Fail
marks = -1  → Invalid
marks = 101 → Invalid

This example includes normal values, boundary values, and invalid values.

Unit Tests Should Be Isolated

A unit test should focus on one unit and avoid depending on unrelated systems.

If a unit test depends on a database, external API, network, or full user interface, it may become slow and unreliable.

Characteristics of Good Unit Tests

Good unit tests should be easy to run, easy to understand, and reliable.

What Unit Testing Can and Cannot Find

Unit testing is powerful, but it does not replace all other testing.

That is why unit testing should be combined with integration, system, acceptance, and regression testing.

Unit Testing and Regression Safety

Unit tests help protect existing behavior when code changes.

If a developer refactors a function and accidentally breaks it, a unit test can fail immediately and alert the developer.

Before change:
calculateDiscount(1000, 10) → 100

After refactoring:
Unit test still checks:
calculateDiscount(1000, 10) should return 100

If result changes unexpectedly:
Test fails

This gives developers confidence when improving or refactoring code.

Unit Testing and TDD

TDD stands for Test-Driven Development.

In TDD, developers write tests before writing the actual implementation code.

TDD Flow:
1. Write a failing test
2. Write minimum code to pass the test
3. Refactor the code
4. Run tests again

Beginners do not need to master TDD immediately, but they should understand that unit tests can also guide software design.

Common Beginner Mistakes in Unit Testing

Best Practices for Unit Testing

Prerequisites Before Learning Unit Testing

Students should understand the following topics before learning unit testing deeply:

Trace Table Example: Unit Testing a Discount Function

FUNCTION calculateDiscount(amount, discountPercentage)
    RETURN amount * discountPercentage / 100
END FUNCTION

Practice Activity: Write Unit Tests

Write unit test cases for the following function.

FUNCTION isEven(number)
    IF number MOD 2 == 0 THEN
        RETURN true
    ELSE
        RETURN false
    END IF
END FUNCTION

Sample Unit Test Cases

Test Case 1:
number = 2
Expected Result: true

Test Case 2:
number = 3
Expected Result: false

Test Case 3:
number = 0
Expected Result: true

Test Case 4:
number = -4
Expected Result: true

Test Case 5:
number = -7
Expected Result: false

Mini Quiz

Interview Questions on Unit Testing Introduction

Quick Summary