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

Flow Coverage: Too many test cases. #13

Open
vvhof opened this issue Mar 9, 2015 · 1 comment
Open

Flow Coverage: Too many test cases. #13

vvhof opened this issue Mar 9, 2015 · 1 comment
Labels

Comments

@vvhof
Copy link
Member

vvhof commented Mar 9, 2015

If eliminating via Flow Coverage, we get a multitude of test cases, where actually one test case would be sufficient (and correct).

This should be adapted to actually eliminate test cases based upon coverage.

@vvhof vvhof added the bug label Mar 9, 2015
@timmaj
Copy link

timmaj commented Mar 9, 2015

Hm...this might or not might be a bug.

In principle, there either could be a but in detecting the flow or in detecting the coverage. However, it might aswell be the case that the flow cannot be fully covered. Moreover, the greedy algorithm used sometimes yiels a too great number of test cases. It should be at most a few, though. There are some debugging options in the code for test case elimination that should help with this, though.

@vvhof vvhof added question and removed bug labels Mar 9, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants