Skip to content
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

measure Cryptol model coverage #86

Open
kiniry opened this issue Feb 18, 2022 · 0 comments
Open

measure Cryptol model coverage #86

kiniry opened this issue Feb 18, 2022 · 0 comments
Labels
assurance Issues that relate to the assurance of the system, whether via models, code, informal, or formal. cryptol Issues related to our Cryptol specifications, or use thereof. ENHANCEMENT New feature or request Someday Issues that are not required by our current contract, but we'd like to attend to someday.
Milestone

Comments

@kiniry
Copy link
Member

kiniry commented Feb 18, 2022

How can we instrument our Cryptol model, use the Cryptol interpreter, or modify the Cryptol interpreter (particularly for :check and :prove) in order to measure how well a set of Cryptol properties covers a Cryptol specification, from a classic code and specification coverage point of view?

Note that doing this is not part of our SoW, but is mentioned in the assurance write-up and having a good answer for it, and possibly actually doing it later, is important.

Your thoughts, @abakst?

@kiniry kiniry added ENHANCEMENT New feature or request To Do assurance Issues that relate to the assurance of the system, whether via models, code, informal, or formal. cryptol Issues related to our Cryptol specifications, or use thereof. labels Feb 18, 2022
@kiniry kiniry added Someday Issues that are not required by our current contract, but we'd like to attend to someday. and removed To Do labels Apr 18, 2022
@kiniry kiniry added this to the Assurance milestone May 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
assurance Issues that relate to the assurance of the system, whether via models, code, informal, or formal. cryptol Issues related to our Cryptol specifications, or use thereof. ENHANCEMENT New feature or request Someday Issues that are not required by our current contract, but we'd like to attend to someday.
Projects
None yet
Development

No branches or pull requests

1 participant