trailofbits/manticore

Increase EVM instruction test coverage

Open

#1,040 创建于 2018年8月10日

在 GitHub 查看
 (0 评论) (0 反应) (1 负责人)Python (3,469 star) (481 fork)batch import
ethereumhelp wantedtesting

描述

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

...

贡献者指南

技术栈
python
领域
testingblockchain
议题类型
test
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-2 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
PythonEVM opcodesManticore testing conventions
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
45
研究方向
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.