What is a Dry Run?

A dry run is the process of manually checking the execution of an algorithm, pseudocode, flowchart, or program step by step without actually running it on a computer.

In a dry run, the programmer behaves like the computer. They read each instruction carefully, update variable values manually, check conditions, follow loops, and write down the output. This helps students understand how the program works internally.

Dry runs are very useful for beginners because they help identify logical mistakes before writing or executing actual code. They also help students understand how variables change during program execution.

Easy Real-Life Example

In programming, a dry run is like rehearsal. Before depending on the computer to run the code, the programmer checks the logic manually.

Why Do We Need Dry Run?

Dry run is needed because a program may look correct but still produce wrong output because of logical mistakes. By manually tracing the program, students can see exactly where the logic goes wrong.

What is a Trace Table?

A trace table is a table used during a dry run to record the values of variables, conditions, and output at each step of an algorithm or program.

Trace tables make dry runs organized. Instead of keeping values in memory, students write them in a table so they can clearly see how each variable changes.

Dry Run vs Debugging

Dry run and debugging are related, but they are not exactly the same. Dry run is usually done manually before or during coding, while debugging is often done after running the program and finding an issue.

Steps to Perform a Dry Run

Students can perform a dry run using a simple structured process.

Example 1: Dry Run to Add Two Numbers

Problem Statement

Pseudocode

START
SET number1 = 10
SET number2 = 20
SET sum = number1 + number2
DISPLAY sum
END

Trace Table

Final Output

30

Example 2: Dry Run for Even or Odd

Problem Statement

Pseudocode

START
SET number = 8

IF number MOD 2 == 0 THEN
    DISPLAY "Even"
ELSE
    DISPLAY "Odd"
END IF

END

Trace Table

Final Output

Even

Example 3: Dry Run with Loop

Problem Statement

Pseudocode

START
SET i = 1

WHILE i <= 5 DO
    DISPLAY i
    SET i = i + 1
END WHILE

END

Trace Table

Final Output

1
2
3
4
5

Example 4: Dry Run to Find Largest of Three Numbers

Pseudocode

START
SET A = 10
SET B = 25
SET C = 15

SET max = A

IF B > max THEN
    SET max = B
END IF

IF C > max THEN
    SET max = C
END IF

DISPLAY max
END

Trace Table

Final Output

25

Java Code Example with Dry Run

Below is a Java program. Students can dry run it using a trace table.

public class Main {
    public static void main(String[] args) {
        int total = 0;

        for (int i = 1; i <= 5; i++) {
            total = total + i;
        }

        System.out.println("Total: " + total);
    }
}

Trace Table

Final Output

Total: 15

Rules for a Good Dry Run

A good dry run should be organized and accurate. Students should not guess the output; they should follow each step carefully.

Dry Run and Edge Cases

Dry run should not be done only for normal inputs. Students should also dry run edge cases to check whether the program works in special situations.

Common Beginner Mistakes

Prerequisites Before Learning Dry Run

To perform dry runs properly, students should understand some basic programming concepts.

Practice Activity: Dry Run a Program

This activity helps students practice dry run using a simple loop.

Problem Statement

START
SET total = 0

FOR i = 1 TO 4 DO
    SET total = total + i
END FOR

DISPLAY total
END

Solution Trace Table

Final Output

10

Mini Quiz

Interview Questions on Dry Run

Quick Summary