Why testing prevents costly bugs in Blockchain / Solidity - Quick Recap

Recall & Review

beginner

What is the main reason testing is crucial in blockchain development?

Testing helps find and fix bugs early, preventing costly mistakes in smart contracts that can lead to financial loss or security breaches.

beginner

How can bugs in blockchain smart contracts be more costly than in regular software?

Because blockchain transactions are often irreversible and involve real money, bugs can cause permanent loss of funds or damage trust.

intermediate

What role does automated testing play in preventing costly bugs?

Automated tests run frequently to catch errors quickly, ensuring smart contracts behave as expected before deployment.

intermediate

Why is manual code review important alongside testing in blockchain projects?

Manual reviews help find logical errors and security issues that automated tests might miss, adding an extra layer of protection.

advanced

What is a real-life example of a costly bug in blockchain that testing could have prevented?

The DAO hack in 2016 exploited a bug in a smart contract, causing a loss of millions of dollars; thorough testing and audits could have avoided it.

Why are bugs in blockchain smart contracts especially costly?

A Because blockchain transactions are irreversible and involve real assets

B Because blockchain code is easy to fix after deployment

C Because bugs only affect test environments

D Because blockchain contracts never handle money

Blockchain transactions cannot be undone, so bugs can cause permanent financial loss.

What is one key benefit of automated testing in blockchain development?

A It replaces the need for any manual review

B It runs tests frequently to catch errors early

C It guarantees no bugs will ever exist

D It slows down the development process

Automated tests help find bugs quickly before deployment.

Which of these is a reason manual code review is important?

A It finds logical and security issues automated tests might miss

B It automatically fixes bugs

C It is faster than automated testing

D It is unnecessary if automated tests exist

Manual reviews catch complex issues that tests may not detect.

What happened in the DAO hack that relates to testing?

A The DAO hack was a planned feature

B The smart contract was perfectly tested and secure

C The hack was unrelated to any bugs

D A bug in the smart contract was exploited causing major losses

The DAO hack exploited a bug that better testing could have prevented.

How does testing help save money in blockchain projects?

A By increasing the number of transactions

B By making the code run faster

C By catching bugs early before they cause expensive damage

D By avoiding the need for audits

Early bug detection prevents costly errors and losses.

Explain why testing is especially important in blockchain smart contract development.

Think about what happens if a bug causes loss on the blockchain.

Describe how automated testing and manual code review work together to prevent costly bugs in blockchain projects.

Consider the strengths of each method.

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