Java Negative test cases not adding up to the ECLEmma java code coverage

When I run sonar code coverage for a set of integration test cases then the code coverage gives high value with positive and valid test cases.
After that I add few more negative test cases for same set of java classes and the code coverage drops drastically by 10 to 20%.
I checked the surefire-reports and logs but I am not sure what is going wrong and how is it impacting.

I want to understand mechanism of Sonar reads sure fire reports.
jgdvishnuSoftware ArchitectAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

jgdvishnuSoftware ArchitectAuthor Commented:
why is it neglected. Please help
0
MogalManicCommented:
Need more information.  If could be that there is something in the tests that you  added that changed the state of something.

You could also try commenting out the new rests to determine that was the actual cause. If it was,then reintroduce them one at a time.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jgdvishnuSoftware ArchitectAuthor Commented:
code coverage values are erratic and inconsistent.
I wanted to understand how the sonar reads sure fire reports for any test cases(positive and negative).
0
Cloud Class® Course: Python 3 Fundamentals

This course will teach participants about installing and configuring Python, syntax, importing, statements, types, strings, booleans, files, lists, tuples, comprehensions, functions, and classes.

jgdvishnuSoftware ArchitectAuthor Commented:
how does sure fire report is read by sonar. what is the mechanism.
Perhaps that gives idea about it.
0
jgdvishnuSoftware ArchitectAuthor Commented:
This was due to 3 reasons:-
1) Sure Fire just lists if there was error or not. there was an error happening in the last method that was lowering the coverage count. We need to check target/classes/sure-fire report.

2) step to test the code coverage is.
mvn clean
mvn install without test case
mvn test // look that there is no error.
then when we restart sonar server
then look for issues in
mvn sonar:sonar.
0
jgdvishnuSoftware ArchitectAuthor Commented:
my step gives more detail and i donot take credit for it.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Java EE

From novice to tech pro — start learning today.