Test Coverage Metrics about rdfunit

[jimkont]

TestCoverageEvaluator was created at the very first beginning of the project and not used since. I updated the code a bit to make not throw errors.

It is still not working correctly but now shows some (wrong) output when you pass -c as a CLI parameter

[INFO  TestCoverageEvaluator] Fdom Coverage: 0.0
[INFO  TestCoverageEvaluator] fRang Coverage: 0.0
[INFO  TestCoverageEvaluator] fDep Coverage: 0.0
[INFO  TestCoverageEvaluator] fCard Coverage: 0.0
[INFO  TestCoverageEvaluator] fMem Coverage: 0.0
[INFO  TestCoverageEvaluator] fCDep Coverage: 0.0

if this is updated to provide the correct numbers it could probably handle your use case.
Each metric measures a specific test coverage according to pages 3-4 in http://svn.aksw.org/papers/2014/WWW_Databugger/public.pdf

the lower the metric numbers the fewer cases are actually tested in the input source.

This class was more like a hack to generate table 4 in the paper.
What is does (or what I remember it was doing) is

• relate RDFUnit patterns to each metric
• calculates class & property statistics for the input source
• exploit some rdfunit pattern hacks to get the classes / properties / patters associated with each test case and calculate the metrics

It needs some work to get this in a good shape & usable. Let me know if working in this directions covers your goal

[jimkont]

Note that, ideally, the metrics should be identified by doing pattern identification inside the SPARQL queries.
This would also work on non pattern-based test cases or pattern-based test cases where the pattern is not associated with coverage metrics.
However, this approach handles most cases easily.