I could argue this left and right with my managers ... but in reality when we mention code coverage we mean looking at a report in CI showing lines of code in green or red ... anything short of that is something else<div><br>
</div><div>Thank you very much for the response </div><div>Cheers</div><div>Mike<br><br><div class="gmail_quote">On Mon, Jan 23, 2012 at 10:47 AM, Wolfgang Laun <span dir="ltr"><<a href="mailto:wolfgang.laun@gmail.com">wolfgang.laun@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">It is highly recommended as "best practice" to have RHS code that<br>
doesn't contain any branching instructions. Then, executing means full<br>
coverage.<br>
<br>
In case it is necessary to have more complex code I'd not put it into<br>
a RHS anyway (where it isn't really OO any more) but I'd code it in<br>
Java files and just call from the RHS.<br>
<br>
For the LHS you can also argue that firing proves coverage; although<br>
it won't be full *expression* logic coverage, due to potentially<br>
skipped subexpressions in disjunctions.<br>
<br>
-W<br>
<div class="im"><br>
<br>
On 23/01/2012, mike <<a href="mailto:mikemps@gmail.com">mikemps@gmail.com</a>> wrote:<br>
> Thank you very much Thomas ... yes, what i need is standard code coverage<br>
> ... my company is all over that metric<br>
><br>
> cheers<br>
> Mike<br>
><br>
> 2012/1/23 Swindells, Thomas <<a href="mailto:TSwindells@nds.com">TSwindells@nds.com</a>><br>
><br>
</div>>> It depends what you are asking for,****<br>
<div class="im">>><br>
>> If you just want to know what proportion of rules you have written have<br>
>> actually activated then that can be simply achieved by having a<br>
>> AgendaEventListener and using it to ‘tick’ rules off when they have been<br>
</div>>> triggered – the blog entry should have you achieve this.****<br>
>><br>
>> ** **<br>
<div class="im">>><br>
>> If you actually want to integrate it with standard java code coverage<br>
>> reports then this is a different question and is likely to be much harder,<br>
</div>>> if not impossible, ****<br>
>><br>
>> ** **<br>
>><br>
>> Thomas****<br>
>><br>
>> ** **<br>
>><br>
>> *From:* <a href="mailto:rules-users-bounces@lists.jboss.org">rules-users-bounces@lists.jboss.org</a> [mailto:<br>
>> <a href="mailto:rules-users-bounces@lists.jboss.org">rules-users-bounces@lists.jboss.org</a>] *On Behalf Of *mike<br>
>> *Sent:* 23 January 2012 14:34<br>
>> *To:* Rules Users List<br>
>><br>
>> *Subject:* Re: [rules-users] Code Coverage****<br>
>><br>
>> ** **<br>
<div class="im">>><br>
>> Thank you very much ... as far as i know in order to do code coverage i<br>
>> need to instrument the packages i'm interested in covering ... this<br>
</div>>> recommendation doesn't take me in that direction****<br>
>><br>
>> ** **<br>
>><br>
>> It is very useful however in showing a way to test rules individually.****<br>
>><br>
>> ** **<br>
>><br>
>> Thank you****<br>
>><br>
>> Mike ****<br>
>><br>
>> ** **<br>
>><br>
>> 2012/1/17 Toni Rikkola <<a href="mailto:toni.rikkola@gmail.com">toni.rikkola@gmail.com</a>>****<br>
<div class="im">>><br>
>> You need to write the coverage tests for JUnit yourself. Test Scenarios in<br>
</div>>> Guvnor do this, but you can't use them outside Guvnor. ****<br>
>><br>
>> ** **<br>
<div class="im">>><br>
>> Test Scenarios get all the rule names for the rules in one package and<br>
</div>>> then compares that list to the rules that fired.****<br>
<div class="im">>><br>
>> Edson's blog entry might help you<br>
>> <a href="http://blog.athico.com/2011/10/cookbook-how-to-test-rules-using-xunit.html" target="_blank">http://blog.athico.com/2011/10/cookbook-how-to-test-rules-using-xunit.html</a><br>
</div>>> .****<br>
>><br>
>> ** **<br>
>><br>
>> Toni****<br>
>><br>
>> ** **<br>
>><br>
>> On Jan 16, 2012, at 5:49 PM, mike wrote:****<br>
>><br>
>> ** **<br>
>><br>
>> Hi there,****<br>
>><br>
>> ** **<br>
<div class="im">>><br>
>> I was wondering if its possible to measure code coverage on test running<br>
</div>>> against a set of rules.****<br>
>><br>
>> ** **<br>
>><br>
>> Thank you****<br>
>><br>
>> Mike****<br>
>><br>
>> ****<br>
<div class="im">>><br>
>> _______________________________________________<br>
>> rules-users mailing list<br>
>> <a href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a><br>
</div>>> <a href="https://lists.jboss.org/mailman/listinfo/rules-users****" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-users****</a><br>
>><br>
>> ** **<br>
<div class="im">>><br>
>><br>
>> _______________________________________________<br>
>> rules-users mailing list<br>
>> <a href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a><br>
</div>>> <a href="https://lists.jboss.org/mailman/listinfo/rules-users****" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-users****</a><br>
>><br>
>> ** **<br>
>><br>
>> ------------------------------<br>
<div class="im HOEnZb">>><br>
>><br>
>> **************************************************************************************<br>
>> This message is confidential and intended only for the addressee. If you<br>
>> have received this message in error, please immediately notify the<br>
>> <a href="mailto:postmaster@nds.com">postmaster@nds.com</a> and delete it from your system as well as any copies.<br>
>> The content of e-mails as well as traffic data may be monitored by NDS for<br>
>> employment and security purposes. To protect the environment please do not<br>
>> print this e-mail unless necessary.<br>
>><br>
>> NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18<br>
>> 4EX, United Kingdom. A company registered in England and Wales. Registered<br>
>> no. 3080780. VAT no. GB 603 8808 40-00<br>
>><br>
>> **************************************************************************************<br>
>><br>
>> _______________________________________________<br>
>> rules-users mailing list<br>
>> <a href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a><br>
>> <a href="https://lists.jboss.org/mailman/listinfo/rules-users" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-users</a><br>
>><br>
>><br>
><br>
<br>
</div><div class="HOEnZb"><div class="h5">_______________________________________________<br>
rules-users mailing list<br>
<a href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/rules-users" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-users</a><br>
</div></div></blockquote></div><br></div>