-
Notifications
You must be signed in to change notification settings - Fork 274
Test behaviour of --cover in the presence of unreachable functions and assumes #255
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
Comments
@kroening, what is the "problem with location coverage"? |
@kroening: in addition to Peter's question, which coverage criterion should we further test together --cover (location, branch, decision, condition, path, mcdc, assertion)? |
@peterschrammel and @kroening: I have created about 15 test cases to check the behaviour of the location coverage. I was unable to find any issue related to this feature. I have just made a pull request in the repository so that you can evaluate the test cases. |
@kroening and @peterschrammel: Is there something else to be done in this issue? otherwise, may I ask you to close it? |
This is done in #290 which is merged. |
Added a test and fixed some minor things in C++ code
Avoid breaking fixpoint when merging data_dependency_context
for C programs
The text was updated successfully, but these errors were encountered: