On Thu, Aug 18, 2011 at 15:28, Jason Porter <span dir="ltr"><<a href="mailto:lightguard.jp@gmail.com">lightguard.jp@gmail.com</a>></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><br><div class="gmail_quote"><div class="im">On Thu, Aug 18, 2011 at 13:09, Dan Allen <span dir="ltr"><<a href="mailto:dan.j.allen@gmail.com" target="_blank">dan.j.allen@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>On Wed, Aug 17, 2011 at 20:56, Jason Porter <span dir="ltr"><<a href="mailto:lightguard.jp@gmail.com" target="_blank">lightguard.jp@gmail.com</a>></span> wrote:</div><div class="gmail_quote"><div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
On Aug 17, 2011, at 18:46, Shane Bryzak <<a href="mailto:sbryzak@redhat.com" target="_blank">sbryzak@redhat.com</a>> wrote:<br>
<br>
> I've done some work to seam-parent already, removing weld-parent from<br>
> the hierarchy, updating all the plugin versions and some general<br>
> cleanup. I have a bunch of questions though, if anyone can answer any<br>
> of these it will save me a lot of time:<br>
><br>
> 1) Do we require both junit and testng?<br>
<br>
</div>I think most are using JUnit. I found ftests that use testng though.<br></blockquote><div><br></div></div><div>That will go away when we switch to Arquillian Drone. The precursor to Drone was bound to (or worked more comfortably) with testng. That's not the case any longer.</div>
<div><br></div><div>JUnit is a much better choice with Arquillian, atm. The intention is to have an equal experience with both, but we are still facing some SPI challenges w/ TestNG.</div><div><br></div><div>Sadly, that knocks out groups. However, we have plans to put a filtering feature at a higher level, in Arquillian itself.</div>
</div></blockquote><div><br></div></div><div>I don't really like how JUnit is doing groups, but they do have a comparable feature now called Categories. I think I can actually say JUnit is moving forward now (maybe not in a direction we agree with) and TestNG is staying rather stagnant.</div>
</div></blockquote><div><br></div><div>The groups in JUnit are incompatible with the Arquillian integration (they both use the same mechanism, which is a strange way to implement groups).</div><div><br></div><div>Both projects are moving forward, but in very different ways.</div>
<div><br></div><div>-Dan</div><div> </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://www.google.com/profiles/dan.j.allen#about" target="_blank">http://www.google.com/profiles/dan.j.allen#about</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><br></div><br>