Why testing prevents costly bugs in Blockchain / Solidity

Introduction

Testing helps find mistakes early so they don't cause big problems later. It saves time and money by fixing bugs before they become costly.

Before launching a new blockchain smart contract to ensure it works correctly.

When updating blockchain code to check that new changes don't break existing features.

While developing decentralized apps to catch errors early in the process.

When integrating with other blockchain services to verify compatibility.

Before deploying code to the blockchain mainnet where mistakes can cost real money.

Syntax

Blockchain / Solidity

function testExample() {
  // Arrange: set up conditions
  // Act: run the code to test
  // Assert: check the results
}

Tests usually follow the Arrange-Act-Assert pattern to keep them clear.

Automated tests run code and check results without manual work.

Examples

This test checks if adding 2 and 3 gives 5.

Blockchain / Solidity

function testAddition() {
  let result = add(2, 3);
  console.assert(result === 5);
}

This test verifies that transferring 10 tokens reduces the user's balance by 10.

Blockchain / Solidity

function testTransfer() {
  let balanceBefore = getBalance(user);
  transfer(user, 10);
  let balanceAfter = getBalance(user);
  console.assert(balanceAfter === balanceBefore - 10);
}

Sample Program

This simple program tests the add function to make sure it returns the correct sum.

Blockchain / Solidity

function add(a, b) {
  return a + b;
}

function testAdd() {
  let result = add(5, 7);
  if (result === 12) {
    console.log('Test passed');
  } else {
    console.log('Test failed');
  }
}

testAdd();

Important Notes

Testing early helps catch bugs before they cause damage.

Automated tests save time by running many checks quickly.

In blockchain, bugs can cause loss of money, so testing is very important.

Summary

Testing finds bugs early to avoid costly mistakes.

Automated tests make checking code easier and faster.

In blockchain, testing protects real assets and trust.

Practice

1. Why is testing especially important in blockchain development?

easy

A. Because it helps find bugs early to avoid costly mistakes

B. Because blockchain code never changes once written

C. Because testing slows down the development process

D. Because blockchain does not handle real assets

Solution

1. Step 1: Understand blockchain risks

   Blockchain handles real assets and trust, so bugs can cause big losses.

2. Step 2: Role of testing

   Testing finds bugs early, preventing costly mistakes before deployment.

3. Final Answer:

   Because it helps find bugs early to avoid costly mistakes -> Option A

4. Quick Check:

   Testing prevents costly bugs = C [OK]

Hint: Testing finds bugs early to save money and trust [OK]

Common Mistakes:

• Thinking blockchain code never changes
• Believing testing slows development
• Ignoring real asset risks

2. Which of the following is the correct syntax to define a simple test function in Solidity?

easy

A. test function balance() { /* code */ }

B. function testBalance() public { /* test code */ }

C. def testBalance(): pass

D. function testBalance() private { /* test code */ }

Solution

1. Step 1: Recall Solidity function syntax

   Functions start with 'function', name, visibility, and body in braces.

2. Step 2: Check options

   function testBalance() public { /* test code */ } matches Solidity syntax with 'public' visibility for test functions.

3. Final Answer:

   function testBalance() public { /* test code */ } -> Option B

4. Quick Check:

   Solidity test function syntax = B [OK]

Hint: Solidity functions start with 'function' and visibility [OK]

Common Mistakes:

• Using Python syntax in Solidity
• Missing 'function' keyword
• Using wrong visibility for test functions

3. Consider this Solidity test snippet:

uint balance = 100;
function testWithdraw() public {
    uint amount = 50;
    balance -= amount;
    assert(balance == 50);
}

What will happen when testWithdraw() runs?

medium

A. The test passes because balance equals 50 after withdrawal

B. The test fails because balance is not updated

C. The code causes a compilation error

D. The test throws a runtime exception

Solution

1. Step 1: Analyze balance update

   Initial balance is 100, subtract 50, new balance is 50.

2. Step 2: Check assertion

   Assert checks balance == 50, which is true, so test passes.

3. Final Answer:

   The test passes because balance equals 50 after withdrawal -> Option A

4. Quick Check:

   balance after subtract 50 = 50 [OK]

Hint: Check variable updates before assertions [OK]

Common Mistakes:

• Assuming balance is unchanged
• Confusing compile errors with runtime logic
• Ignoring assert condition

4. This Solidity test function is meant to check if a user can withdraw funds:

function testWithdraw() public {
    uint balance = 100;
    uint amount = 150;
    balance -= amount;
    assert(balance >= 0);
}

What is the main problem with this test?

medium

A. The test function is missing visibility

B. The assert condition is always true

C. It allows balance to go negative, which is invalid in Solidity

D. The amount is less than balance, so test is useless

Solution

1. Step 1: Check balance subtraction

   Subtracting 150 from 100 causes underflow (negative balance).

2. Step 2: Understand Solidity behavior

   Solidity unsigned integers cannot be negative; underflow causes error or wrap.

3. Final Answer:

   It allows balance to go negative, which is invalid in Solidity -> Option C

4. Quick Check:

   Unsigned int underflow = error [OK]

Hint: Check for underflow or overflow in tests [OK]

Common Mistakes:

• Ignoring unsigned integer limits
• Assuming assert always passes
• Missing visibility keyword

5. You want to write automated tests for a smart contract that manages token transfers. Which approach best prevents costly bugs?

hard

A. Write tests that check only successful transfers

B. Write tests only after deployment

C. Skip tests and rely on manual code review

D. Write tests that check both successful and failed transfers

Solution

1. Step 1: Understand test coverage needs

   Testing only successes misses bugs in failure cases.

2. Step 2: Importance of failure tests

   Tests for failed transfers catch edge cases and prevent costly errors.

3. Final Answer:

   Write tests that check both successful and failed transfers -> Option D

4. Quick Check:

   Test successes and failures = D [OK]

Hint: Test both success and failure cases to catch all bugs [OK]

Common Mistakes:

• Testing only success cases
• Skipping automated tests
• Testing after deployment too late