Introduction

Testing is the process of checking whether a program works correctly and meets the expected requirements.

Writing code is not enough. Developers must also verify that the code behaves correctly for normal inputs, wrong inputs, edge cases, and real-world usage.

Good testing improves software quality, reduces bugs, increases confidence, and makes future changes safer.

Easy Real-Life Example

Car Check:
Check brakes
Check lights
Check tyres
Check fuel
Check steering

Software Testing:
Check input
Check output
Check calculations
Check errors
Check user flow

Testing software is similar. Before releasing a program, we check whether it works safely and correctly.

What is Software Testing?

Software testing is the activity of evaluating a software application to check whether it works as expected.

Testing compares the actual result produced by the program with the expected result.

Simple Testing Example

Requirement:
If marks are 40 or above, result should be Pass.

Input:
marks = 45

Expected Output:
Pass

Actual Output:
Pass

Test Result:
Passed

If the actual output matches the expected output, the test passes. If not, the test fails.

Why Testing is Important

Testing is important because even small mistakes in software can create serious problems.

A small bug may cause wrong calculations, failed payments, security issues, data loss, poor user experience, or application crashes.

Common Terms in Testing

Students should understand some basic testing terms before learning testing deeply.

Levels of Testing

Software testing can happen at different levels. Each level checks a different part of the software.

Unit Testing

Unit testing checks a small unit of code, such as a function or method.

It is usually performed early and helps developers find bugs before different parts of the system are combined.

Example: Unit Test Idea

Function:
isPassingMark(marks)

Requirement:
Return true if marks are 40 or above.

Test Cases:
marks = 50  → expected true
marks = 40  → expected true
marks = 39  → expected false
marks = 0   → expected false

Unit testing checks whether a small piece of logic works correctly.

Integration Testing

Integration testing checks whether different modules work correctly together.

Sometimes individual modules work correctly, but problems appear when they communicate with each other.

Example:
Login Form Module
        ↓
Authentication Module
        ↓
User Database

Integration Test:
Check whether login form sends data correctly,
authentication checks credentials,
and database returns matching user information.

Integration testing helps find communication and data-flow problems between modules.

System Testing

System testing checks the complete software system.

It verifies whether the full application works according to requirements.

Student Management System Testing:
- Add student
- Update marks
- Search student
- Generate report
- Login and logout
- Validate permissions

System testing checks the application from an overall user and business perspective.

Acceptance Testing

Acceptance testing checks whether the software satisfies user or business expectations.

It is often performed by business users, clients, teachers, administrators, or product owners.

Acceptance Test Example:
A teacher checks whether the Student Management System can:
- Add students
- Enter marks
- Calculate grades
- Generate report cards

If the teacher accepts the behavior,
the feature may be considered ready.

Regression Testing

Regression testing checks whether existing features still work after code changes.

When developers fix bugs or add new features, they must ensure old functionality is not broken.

Example:
A new discount feature is added to an e-commerce app.

Regression testing checks:
- Login still works
- Cart still works
- Payment still works
- Invoice still works
- Old discount rules still work

Regression testing protects existing features from accidental breakage.

Manual Testing vs Automation Testing

Testing can be done manually by humans or automatically using tools and scripts.

What is a Test Case?

A test case is a documented set of steps used to verify a specific feature or behavior.

A good test case clearly explains what to test, what data to use, what steps to follow, and what result is expected.

Test Case Structure

Example Test Case: Login

Positive and Negative Testing

Testing should include both correct and incorrect situations.

Boundary Testing

Boundary testing checks values at the edge of allowed ranges.

Many bugs happen near minimum and maximum limits.

Requirement:
Marks must be between 0 and 100.

Boundary Test Values:
-1   → invalid
0    → valid
1    → valid
99   → valid
100  → valid
101  → invalid

Boundary testing is useful for marks, age, quantity, price, password length, and date ranges.

Edge Cases

An edge case is an unusual or extreme situation that may still happen.

Example Feature:
Calculate average marks.

Normal Case:
[80, 70, 90]

Edge Cases:
Empty marks list
Marks with zero
Marks above 100
Negative marks
Only one subject
Very large number of subjects

Testing edge cases helps make software more reliable.

Smoke Testing

Smoke testing is a quick basic test to check whether the main features of an application are working.

Smoke Test Example:
- Application opens
- Login page loads
- User can login
- Dashboard opens
- Logout works

If smoke testing fails, deeper testing may not be useful until the main issue is fixed.

Debugging and Testing

Testing finds problems. Debugging helps identify and fix the cause of those problems.

Student-Friendly Example: Grade Calculator Testing

Feature:
Grade Calculator

Requirement:
- 90 and above: A
- 75 to 89: B
- 60 to 74: C
- 40 to 59: D
- Below 40: Fail
- Marks must be 0 to 100

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

These test cases check normal values, boundary values, and invalid values.

Real-World Example: E-Commerce Checkout Testing

Best Practices for Testing

Common Beginner Mistakes

Prerequisites Before Learning Testing Basics

Students should understand the following topics before learning testing deeply:

Trace Table Example: Testing a Pass/Fail Program

IF marks >= 40 THEN
    result = "Pass"
ELSE
    result = "Fail"
END IF

Practice Activity: Write Test Cases

Write test cases for the following requirement.

Requirement:
A user can withdraw money if:
- Account balance is greater than or equal to withdrawal amount.
- Withdrawal amount must be greater than 0.

Sample Test Cases

Test Case 1:
balance = 1000, withdrawal = 500
Expected Result: Withdrawal allowed

Test Case 2:
balance = 1000, withdrawal = 1000
Expected Result: Withdrawal allowed

Test Case 3:
balance = 1000, withdrawal = 1200
Expected Result: Withdrawal denied

Test Case 4:
balance = 1000, withdrawal = 0
Expected Result: Invalid withdrawal amount

Test Case 5:
balance = 1000, withdrawal = -100
Expected Result: Invalid withdrawal amount

Mini Quiz

Interview Questions on Testing Basics

Quick Summary