<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Brian Stansberry wrote:
<blockquote cite="mid:4B7A9ED7.5060006@redhat.com" type="cite">
<pre wrap="">Yes and no.
Yes, I definitely agree that the AS testsuite could use beefing up in
terms of integration testing of some of the stuff the AS brings in.
</pre>
</blockquote>
+1<br>
<blockquote cite="mid:4B7A9ED7.5060006@redhat.com" type="cite">
<pre wrap="">
High level
integration tests can catch that by luck, but IMHO much better is closer
unit testing of the deployer class where the problem was. In general, my
impression is the AS testsuite is overly reliant on integration testing
and doesn't have enough low level unit testing.
</pre>
</blockquote>
-1<br>
<br>
The testsuite is there for regression testing. An effective regression
test is one that uncovers a bug. A good regression test is one that
fails. In this case, the integration test did that and it wasn't just
dumb luck. I would submit that as regression tests go, integration
tests find bugs far more often then their low-level unit-testing
counterparts.<br>
<br>
Unit tests are written to pass. The person writing the test also wrote
the code. And good programmers tend to write code that works.<br>
<br>
If done right, unit tests do help a programmer figure out what his API
needs to look like (TDD). They also serve as a sanity check for that
programmer to make sure his small change didn't mess anything up. But
because they are so fine-grained and isolated, they are unlikely to
fail when later run in the testsuite for regression purposes.<br>
<br>
The good test (one more likely to fail), is the one that combines the
work of two or more programmers. That is what integration tests do.
We need more emphasis on integration tests, not less.<br>
<br>
Furthermore, an integration test goes through real use cases. It makes
sure that at the end of the day, the system can actually do something
useful. And that's the best test of all.<br>
<blockquote cite="mid:4B7A9ED7.5060006@redhat.com" type="cite">
<pre wrap="">
On 02/16/2010 06:26 AM, Dimitris Andreadis wrote:
</pre>
<blockquote type="cite">
<pre wrap="">For future releases, shouldn't we enhance the scope of our standard testsuite runs to
uncover issues earlier? Better testing of components like seam/weld/jopr/rest-easy/etc.
Brian Stansberry wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Just an FYI on the status of the 6.0.0.M2 release. Rajesh Rajasekaran,
Martin Gencur and the QE folks are doing a great job (thanks!) and found
a couple critical issues not exposed by the testsuite. They proved easy
to fix, and are fixed, but it's delayed things by a day.
</pre>
</blockquote>
<pre wrap="">_______________________________________________
jboss-development mailing list
<a class="moz-txt-link-abbreviated" href="mailto:jboss-development@lists.jboss.org">jboss-development@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/jboss-development">https://lists.jboss.org/mailman/listinfo/jboss-development</a>
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
</blockquote>
<br>
</body>
</html>