trailofbits/manticore

Increase EVM instruction test coverage

Open

#1,040 opened on Aug 10, 2018

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

Repository metrics

Stars
 (3,469 stars)
PR merge metrics
 (No merged PRs in 30d)

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

Research direction
Add unit tests for the listed EVM instructions in the tests/ETH directory. Study the existing test patterns and the EVM specification to write correct test cases.
Tech stack
python
Domain
testing
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitPython
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65