Hello, I do not think there are real standards. 100% branch coverage is almost unreachable given that simple looking stuff like try-with-resources already results in 8 branches using Oracle JDK 8.
I would strive to cover your own responsibilities as good as you can with unit tests and strive for here for the 100. This is only possible if you facade external systems, these facades are mostly boring, so I sometimes exclude them completely from the unit test coverage but always test the happy paths integratively. Regards Mirko -- Sent from my mobile Am 16.02.2017 07:25 schrieb <[email protected]>: > Hello Everyone, > I am new to JaCoCo using maven and Jenkins. > I have made integration of JaCoCo,Maven and Jenkins. > However i am not getting what rules and standards needs to be set to > improve code quality. > Is there any Good Industry Standard for > Instruction % Branch % Complexity % Line % Method % > Class > > -- > 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/9da87832-37c4-45d6-92fb-989a34d82444%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- 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/CAK8jvqweB4zco77srgQoHRhcnFWn-mnO8AmSp_AT6N%2BGDdcy1A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
