[ 
https://issues.apache.org/jira/browse/CAMEL-10345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15556298#comment-15556298
 ] 

ASF GitHub Bot commented on CAMEL-10345:
----------------------------------------

GitHub user tkopczynski opened a pull request:

    https://github.com/apache/camel/pull/1203

    CAMEL-10345: Extended summary for routes coverage in camel-test

    Adds listing uncovered routes and processor coverage to summary in 
CamelTestSupport.
    Related to @davsclaus comment under #1198 

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/tkopczynski/camel camel-10345-followup

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/camel/pull/1203.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1203
    
----
commit 627f0158df256991c9950879919cdb43c9211d90
Author: Tomasz Kopczynski <[email protected]>
Date:   2016-10-07T21:21:30Z

    CAMEL-10345: Extended summary for routes coverage in camel-test

----


> camel-test - Route coverage summary to be logged
> ------------------------------------------------
>
>                 Key: CAMEL-10345
>                 URL: https://issues.apache.org/jira/browse/CAMEL-10345
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-test
>            Reporter: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.19.0
>
>
> The camel-test has a feature to dump route coverages. We should do some 
> summary logging to output 
> https://github.com/apache/camel/blob/master/components/camel-test/src/main/java/org/apache/camel/test/junit4/CamelTestSupport.java#L378
> INFO Route coverage (6 out of 6 routes used)
> WARN Route coverage (5 out of 6 routes used)
> And do a WARN log if one or more route was not in use during testing.
> It may be some percentage instead 100%, 75% etc. eg to count each EIP/node 
> and see how many has 0 in total exchange count.
> We can then later do a drill down, and point out which EIP/node that hasn't 
> been covered in a route.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to