-
Notifications
You must be signed in to change notification settings - Fork 21
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
Clean coverage after tests applying #349
Clean coverage after tests applying #349
Conversation
Why do we need to clean coverage and remove all tests after application? What if the user wants to apply a set of tests and then work on other tests, and then apply them again? |
…le-buttons-during-tests-excecution Disable buttons during tests running
FYI: My approval is for the existing changes, in case that cleaning the coverage is suitable
For your use case showing coverage seems to be useful, but there are a couple of ideological problems:
All this led me to the conclusion that we have to either clear coverage and make it just a useful visualization of currently generated tests(as it is now) or refactor how we treat coverage, in general, to make it useful for understanding the not-covered part of the project. I am voting for the first option, at least for now. @Vladislav0Art @pderakhshanfar @arksap2002 your opinion on it? |
My problem is about removing test cases. |
Oh, I didn't notice such behaviour, it obviously has to be fixed. I was thinking about the concept of deleting coverage in general |
This issue fixed here: #333 |
@pderakhshanfar fixed, could you, please, check it again |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It works for me now
Description of changes made
After applying tests to the project the coverage have to be removed.
Other notes
Closes #347