Why testing prevents costly bugs in Blockchain / Solidity - Visual Breakdown

Concept Flow - Why testing prevents costly bugs

Write Code

↓

Write Tests

↓

Run Tests

↓

Tests Pass?

No→Fix Bugs

↓

Re-run Tests

↓

Deploy Code

↓

Code Works Safely

This flow shows how writing and running tests before deployment helps catch bugs early, preventing costly errors later.

Execution Sample

Blockchain / Solidity

function transfer(amount) {
  if (balance >= amount) {
    balance -= amount;
    return true;
  } else {
    return false;
  }
}

This simple blockchain transfer function checks if balance is enough before subtracting amount.

Execution Table

Step	balance	amount	Condition (balance >= amount)	Action	Return Value
1	100	50	100 >= 50 is True	balance = 100 - 50 = 50	true
2	50	60	50 >= 60 is False	No subtraction	false
3	50	50	50 >= 50 is True	balance = 50 - 50 = 0	true
4	0	10	0 >= 10 is False	No subtraction	false

💡 All test cases run to check transfer function behavior with different amounts.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4
balance	100	50	50	0	0
amount	-	50	60	50	10

Key Moments - 2 Insights

Why do we check the condition 'balance >= amount' before subtracting?

Because if we subtract without checking, balance could go negative causing errors. See execution_table step 2 where condition is false and no subtraction happens.

What happens if tests are not run before deployment?

Bugs like allowing negative balance could go unnoticed, causing costly failures after deployment. The flow shows tests catch bugs early before deploy.

Visual Quiz - 3 Questions

Look at the execution_table at Step 3, what is the balance after the transfer?

A 0

B 50

C 100

D 60

💡 Hint

Check the 'Action' and 'balance' columns at Step 3 in execution_table.

At which step does the condition 'balance >= amount' become false for the first time?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Look at the 'Condition' column in execution_table to find the first false.

If the condition check was removed, what would happen to balance at Step 2?

A transfer returns false

B balance would become negative

C balance stays the same

D transfer returns true

💡 Hint

Without condition, subtraction happens regardless, see variable_tracker for balance changes.

Concept Snapshot

Testing in blockchain code means writing checks before deployment.
Run tests to catch bugs early.
Prevents costly errors like negative balances.
Always verify conditions before state changes.
Fix bugs before deploying to keep code safe.

Full Transcript

This visual shows why testing blockchain code prevents costly bugs. We start by writing code and tests, then run tests. If tests fail, we fix bugs and re-run tests until all pass. Only then do we deploy code safely. The example transfer function checks if balance is enough before subtracting. The execution table traces four test cases showing when transfers succeed or fail. The variable tracker shows how balance changes step by step. Key moments explain why condition checks matter and why testing before deployment is critical. The quiz asks about balance values and condition results to reinforce learning. Testing helps catch errors early, avoiding expensive problems after deployment.