With increasing number of tests, their execution time increases as well.
Currently, various tools provide metrics of test code coverage. These
metrics however do not help identify duplicate test coverage, that leads
only to unnecessary increase of test execution time without any benefit to
effective code coverage. Information about duplicate coverage and execution
time of duplicate tests would be a valuable help for subsequent refactoring
of test code base.
JaCoCo is very useful tool and with this new functionality we can provide
more helpful information about the test coverage.
*Possible solution:*
1.
Extend the data file format to include data about
-
Caller (test invoking the piece of code e.g.: line, branch, method,
class,…)
-
Time spent in the piece of code
2.
Enhance the code coverage tool to store information described in point 1
3.
Enhance the tool’s reporting capabilities to present information about
-
Duplicate code coverage
-
Time spent in running tests
I have no problem to discuss about better solutions.
*What I want to do:*
I want to implement solution and write a bachelor thesis at my university
(Faculty of Informatics, Masaryk University, Brno, Czech Republic) about
this.
*Expected result:*
Functional solution and report capability to present information.
How do you like this idea? Best regard,
Jakub Schwan
--
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/cdd5ecf2-a2b8-4488-8e13-4b3928fb0a6f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
