runtimeverification / runtimeverification/evm-semantics
Update legacy-tests across test-suites
Nobody has claimed this yet.
- Dominant language
- KCL
- Stars
- 591
- Forks
- 156
- Avg merge
- 2h 19m
- Merged PRs (30d)
- 1
Description
Are tehre any legacy tests that are not covered by the new test-suite already anyway? Maybe we can drop running the legacy tests. Is it just the Nix harness that runs them? We could update th eNix harness to run one of the new formats of tests instead perhaps?
That can be done in follow-up PR if you want, which can then simplify this.
Originally posted by @ehildenb in https://github.com/runtimeverification/evm-semantics/pull/2821#discussion_r2611543699
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the legacy and new test-suite formats, then inspect the Nix harness that runs them. Confirm which legacy tests are already covered and define done as removing redundant legacy execution or updating the harness to use the new format, with any follow-up work separated.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, testing-qa
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100