Skip to content

Regression test for remove_virtual_functions [TG-1404] #1805

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

Conversation

romainbrenguier
Copy link
Contributor

This is based on #1731 to check that it fixes coverage issues with virtual functions TG-1404.

This test shows that coverage issue with virtual functions is fixed (TG-1404).
@romainbrenguier romainbrenguier force-pushed the bugfix/all_resolved_calls branch from 1238863 to 94c2ccd Compare February 8, 2018 10:50
@romainbrenguier romainbrenguier changed the base branch from bugfix/all_resolved_calls to develop February 8, 2018 10:51
Copy link
Contributor

@thk123 thk123 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks fine, though I'm not sure what it tests that the test Matthias added doesn't. I think a more useful test would be a unit that explicitly checks the goto program after removing virtual functions to check the appropriate virtual functions are called in the appropriate contexts.

@martin-cs
Copy link
Collaborator

I'm not quite sure why I've got this as a "code owner" but ... yeah, adding regression tests is a good idea.

@romainbrenguier
Copy link
Contributor Author

@martin-cs my PR was originally based on a PR by Matthias, when his PR got merged and I rebased mine on develop several commits appeared here marking you code owner, these commits disappeared when I changed the base branch to develop, but for some reason I still cannot remove the review requests.

Copy link
Collaborator

@martin-cs martin-cs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fine by me.

@romainbrenguier
Copy link
Contributor Author

Unit tests were added with the PR that fixed this issue. And they check the problem is solved in a more reliable way than this test. So I'm going to close this PR.

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.

3 participants