trailofbits/manticore

Increase EVM instruction test coverage

Open

#1040 opened on Aug 10, 2018

View on GitHub
 (0 comments) (0 reactions) (1 assignee)Python (3,469 stars) (481 forks)batch import
ethereumhelp wantedtesting

Description

This is just from a quick look over unit test coverage report results. What actually needs coverage may be another story.

The following have no coverage in tests/ETH/*;

  • STOP
  • CALLDATACOPY
  • CODECOPY
  • EXTCODECOPY
  • RETURNDATACOPY
  • RETURNDATASIZE
  • BLOCKHASH
  • MLOAD
  • MSTORE
  • MSTORE8 (tainted pc)
  • SSTORE (tainted pc)
  • JUMPI
  • SWAP
  • LOG
  • CREATE
  • CALL
  • CALLCODE
  • RETURN
  • DELEGATECALL
  • STATICCALL
  • THROW

...

Contributor guide

Tech stack
python
Domain
testingblockchain
Issue type
test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
PythonEVM opcodesManticore testing conventions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
Examine the existing tests in tests/ETH/ directory to understand the testing patterns used. For each EVM instruction listed (e.g., STOP, CALLDATACOPY), create a test case that exercises the instruction and verifies correct symbolic execution. Refer to Manticore's documentation and EVM opcode specifications for expected behavior. Since the issue is old and unassigned, it's best to check if any related work has been done in the repository.