feat(github): coverage workflow using evmone script #503
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🗒️ Description
git job to measure coverage of ported tests
if a new line introduced to converted_ethereum_tests, the script will run coverage and make an artifact
demonstration: #504
What does it do:
Evmone docker image
The main script is in this repo: https://github.com/winsvega/evmtest_coverage/tree/main/dockerhub
There are 3 docker dependencies that are used in this git workflow:
Coverage script
With the latest github docker workflow refactor, the script speaks for itself, but I put here some comments:
This command mounts
evmtest_coverage/coverage
github folder into docker /tests folderPATCH_TESTS is a folder inside that already prepared with the .json tests to cover
run: /entrypoint.sh --mode=cover --testpath=/tests/PATCH_TESTS --outputname=PATCH
will create coverage_PATCH.lcov and PATCH folder with html report
same is done for the BASE tests
run: /entrypoint.sh --mode=diff --basefile=coverage_BASE.lcov --patchfile=coverage_PATCH.lcov
will create DIFF folder with html report on coverage. which will later be uploaded as artifact.
🔗 Related Issues
Feauture
✅ Checklist
mkdocs serve
locally and verified the auto-generated docs for new tests in the Test Case Reference are correctly formatted.