-
Notifications
You must be signed in to change notification settings - Fork 134
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
Measuring test vector coverage #314
Comments
so basically speaking:
for step 1,
is that right? |
hi @Stebalien |
completed a simple demo, and captured a coverage report for executing |
Yes and yes.
Also yes. We'll have to have some way to compile actors with tracing enabled. |
That's awesome! Note: We probably don't need the human readable side of things. As long as the format is compatible with codecov. @raulk is currently in the process of factoring out the actors into a separate repo (with a single wasm build script so this should be a bit simpler). Once that lands, are you up for making a PR? |
sure, the reults could be the compatible format, or at least they should be easily converted to, since all the things are generated by
of course :) |
It would be really nice to measure what parts of actors are covered by our current test vectors.
The text was updated successfully, but these errors were encountered: