RE: [JBoss-dev] Integration issues

[Scott M S. <sco...@jb...>]

So the jems integration testsuite brute force tests can be run against
the current snapshot as well as well as targeted released versions. The
portal testsuite is supposed to be updated to be doing this.=20

-----Original Message-----
From: jbo...@li...
[mailto:jbo...@li...] On Behalf Of Tom
Elrod
Sent: Tuesday, November 01, 2005 10:14 PM
To: jbo...@li...
Subject: Re: [JBoss-dev] Integration issues

There are two issues:

1. Project B has proper test coverage (within its own project)
2. Project A detecting there is a hole in project B's test coverage

For issue 1, I agree with all that everyone is saying.  The only=20
exception would be that a developer from A should write test cases for=20
project B to ensure complete coverage.  Although that would be great, it

just simply isn't going to happen (for various reason, which I can=20
enumerate if need be).  The best we can hope for is that they open a=20
jira issue for it.

Issue 2, and what I was originally talking about, is about early=20
visibility to project B's test coverage holes.  If A is only testing=20
against released versions of B, will not know about the hole till too=20
late (after the next release of B).  If A is testing against a=20
development snapshot of B, would be able to detect and plug a hole=20
earlier in the development cycle of B (probably via a opening a jira
issue).