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.