On Tue, Feb 7, 2012 at 01:53, Richard Kennard <span dir="ltr">&lt;<a href="mailto:richard@kennardconsulting.com">richard@kennardconsulting.com</a>&gt;</span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<br>
Just curious: what is the consensus on code coverage tools within JBoss?<br></blockquote><div><br></div><div>I like the way you phrased that question, because it aligns perfectly with the new JBoss Testing SIG (Special Interest Group). [1]</div>

<div><br></div><div>I&#39;m launching an initiative to form SIGs in the JBoss Community. They are designed to answer these sort of &quot;What does JBoss do?&quot; sort of questions. To be honest, such a question really just fell on the floor in the past because JBoss is such a distributed network of project teams. Sometimes, we don&#39;t even know other projects exist. SIGs give us common topic tables to sit at and discuss these very questions. They are also there just to explore what else we could be doing and learning from each others experiences.</div>

<div><br></div><div>So come on by. And feel free to post this question there (you&#39;ll be an early adopter, but it will pick up quickly).</div><div><br></div><div><a href="http://community.jboss.org/groups/testing">http://community.jboss.org/groups/testing</a></div>

<div><br></div><div>We like stories of the past, what isn&#39;t working in the present and what you want to be able to do in the future.</div><div><br></div><div>-Dan</div><div><br></div></div>-- <br><div>Dan Allen</div>
Principal Software Engineer, Red Hat | Author of Seam in Action<br>
Registered Linux User #231597<br><br><div><a href="http://google.com/profiles/dan.j.allen" target="_blank">http://google.com/profiles/dan.j.allen</a><br><a href="http://mojavelinux.com" target="_blank">http://mojavelinux.com</a><br>

<a href="http://mojavelinux.com/seaminaction" target="_blank">http://mojavelinux.com/seaminaction</a></div>