ethereum-optimism / ethereum-optimism/optimism
op-node: improve engine package testing
Open
A-op-node
- Dominant language
- Go
- Stars
- 6.5k
- Forks
- 4k
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 145
Description
Once we remove more of the legacy engine-controller, we can cleanly test the op-node engine package, and fix the code coverage.
Contributor guide
Research direction
Start by locating the op-node engine package and the remaining legacy engine-controller code. Inspect the existing package tests and coverage results to identify what is currently untested. Done means the legacy dependency is reduced enough for clean engine-package tests and the code coverage is improved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100