Nice idea. But filtering all methods with complexity 1 seems a bit broad
to me.
Filtering in JaCoCo will require a detailed analysis of the method
bodies anyways, so plain setters and getters should be identifiable,
e.g. if method setFirstName() just assignes a value to field firstname.
If the same method assigns a value to field secondname this is most
likely a bug and the method should not be excluded.
Regards,
-marc
On 17.09.15 12:59, [email protected] wrote:
Hi, I've been using Jacoco for some time now and decided to share this
suggestion, hope it will be considered:
Besides the already existing excludes by name, how about having the option of
excluding methods that have complexity 1?
This would solve the problem with excluding getters/setters and trivial
constructors and seems to be something that Jacoco already knows how to deal
with.
Sorry if this is duplicated but my searches found nothing similar.
What are your thoughts on this?
--
You received this message because you are subscribed to the Google Groups "JaCoCo
and EclEmma Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jacoco/55FB185B.7020501%40mountainminds.com.
For more options, visit https://groups.google.com/d/optout.
