-
Suggestion
-
Resolution: Fixed
-
None
At the very least, provide an example of the current way to exclude or include a single package from being instrumented.
Ideally, a user could select one or more modules to have clover enabled.
Similarly, the includes/excludes text boxes should be augmented with a File Chooser, or Package Tree Browser to make selecting a package as easy as possible.
Is it possible to put Clover in the Context Menu of the IDEA Package Explorer so that includes/excludes can be set from there as well?
Watching a new user trying to configure includes/excludes using the current UI is very revealing.
[CLOV-604] Make selecting excludes/includes a lot simpler
The solution is still ant-glob-pattern - oriented.
Changing (optionally) to more project-tree oriented needs a separate JIRA
Following stuff needs to be added:
- mark just-excluded files as dirty instead of scheduling immediate rebuild
- right-click action for module exclusion
- add exclude action to Coverage Explorer View
Created CIJ-301 for excluding 100% covered classes from the view only
I should have deleted my last comment above, instead of just UPDATING it.
What is the purpose of excluding 100% covered classes?
To remove them from the Coverage Explorer, so a testing session can focus on just a few dedicated classes or packages. On clarification with Kate however, she doesn't actually want to exclude them from Clover. So ignore that. Also, she can sort the files in the CoverageExplorer to achieve mostly what she wants.
Maybe this should be done automatically?
Nope. Don't worry about it.
The includes/excludes in the Package Explorer is awesome! Kate == very excited!
There is still value in having the context menus, BTW.
I mean, if it can be done in the normal Project Explorer it's probably good to do it in the Coverage Explorer too even if it's not how Kate does it.
Requirements gathering FAIL (not directed at anyone in particular). This issue seems to have started out as "exclude from instrumentation" and is now including "exclude in Coverage Explorer if condition X is met". Better we caught this now than later, of course.
I think I misunderstood. Are you saying that there's still value in the context menus but just not in the Coverage Explorer?
Exclusion for instrumentation shouldn't be necessary just for certain classes of, er, classes being excluded / included in the Coverage Explorer. Clover-for-Eclipse will filter out classes with 100% coverage via a toggle button in the toolbar. I suggest you do it that way.
Can I suggest that the grey Clover icon might be less laden with meaning than the red icon?
What is the purpose of excluding 100% covered classes?
Maybe this should be done automatically?
UPDATE Kate has just mentioned that this is not how she would use it. So don't bother adding the menu to the Coverage Explorer just yet.
Another valid use-case however, (one which Kate in fact would use), is to toggle includes/excludes in the Coverage Explorer panel as well:
During a testing session, Kate likes to exclude classes based on how much coverage they have. e.g. she likes to exclude classes which have coverage of 100% already.
The decision to exclude a class is most often made when viewing the coverage explorer.
Also - this may be a known bug, basically, if you select "Add includes" on a directory which is already marked as included, the icon changes to red.
The includes/excludes patterns are still correct though.
I know this issue is resolved already, but I couldn't help commenting anyway.
I love the new includes/excludes. I used it today and checked out the Ant patternset it created - there is no way I would have figured out the right value to set, plus it was just so easy to right click and exclude a boatload of autogenerated classes rather than having to think about what syntax to (try and) use.
Thanks so much guys