Assertion patterns in Blockchain / Solidity - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is an assertion in software testing?

An assertion is a statement that checks if a condition is true during a test. If the condition is false, the test fails. It helps verify that the code works as expected.

intermediate

Why are assertion patterns important in blockchain testing?

Assertion patterns help ensure blockchain code behaves correctly, such as verifying transactions, smart contract states, and security rules. They catch errors early and improve trust in the system.

beginner

Name a common assertion pattern used in blockchain smart contract tests.

One common pattern is asserting that a transaction emits the expected event. This confirms that the contract executed the correct action.

intermediate

How does the 'assert revert' pattern work in blockchain testing?

It checks that a transaction fails and reverts when given bad input or unauthorized access. This ensures the contract protects against invalid actions.

advanced

What is the benefit of using multiple assertion patterns in one blockchain test?

Using multiple assertions checks different parts of the code and outcomes. This gives a fuller picture of correctness and helps find bugs faster.

What does an assertion do in a blockchain test?

A Generates blockchain addresses

B Runs the blockchain node

C Deploys the smart contract

D Checks if a condition is true and fails the test if not

Assertions verify conditions during tests and cause failures if conditions are false.

Which assertion pattern verifies that a smart contract emitted an event?

A Assert revert

B Assert balance change

C Assert event emission

D Assert transaction hash

Assert event emission checks that the contract emitted the expected event during execution.

What does the 'assert revert' pattern test for?

A Transaction failure and rollback

B Block confirmation time

C Correct gas usage

D Successful transaction completion

'Assert revert' ensures that invalid transactions fail and the blockchain state does not change.

Why use multiple assertions in one blockchain test?

A To check different outcomes and improve test coverage

B To slow down the test

C To confuse developers

D To reduce gas fees

Multiple assertions verify various aspects of the code, catching more bugs and improving confidence.

Which of these is NOT a typical assertion in blockchain testing?

A Assert event emitted

B Assert UI color scheme

C Assert transaction success

D Assert revert on error

UI color scheme is unrelated to blockchain logic testing and assertions.

Explain how assertion patterns help improve blockchain smart contract testing.

Think about how assertions check conditions and outcomes in tests.

Describe the 'assert revert' pattern and why it is important in blockchain testing.

Consider what happens when a smart contract should reject a bad input.