Skip to content

[DO NOT MERGE] Vitest blockchain test runner for coverage reports, BLS coverage attempt by including implementation code as well #3997

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 10 commits into
base: master
Choose a base branch
from

Conversation

jochem-brouwer
Copy link
Member

This PR attempts to create a coverage report for BLS, by also including the implementation code (Noble) in the report. I have tried to add things to vitest such that it also adds node_modules/@noble/curves to the report output, but to no avail. The new WIP strategy is now instead to list noble as an inner package and let vitest generate a coverage report.

This PR showscases (but is NOT intended to get merged) also a very dirty way to generate coverage from the blockchain tests. So we can directly run fixtures from EEST and generate a coverage report. If you want to change which tests are ran change this in vm/test/tester/testRunnerVitest.spec.ts:

dir: '../fixtures/blockchain_tests/prague/eip2537_bls_12_381_precompiles/bls12_g1add', (to some dir you want to test)

To run coverage, cd ./packages/vm and then bash coverage.sh

@jochem-brouwer jochem-brouwer changed the title [DO NOT MERGE] [DO NOT MERGE] Vitest blockchain test runner for coverage reports, BLS coverage attempt by including implementation code as well Apr 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant