Hi,
Micheal J wrote:
> Juha-P Lindfors wrote:
> > On Fri, 23 Feb 2001, Phan Anh Tran wrote:
> > > 1. Are developers required to pass existing regression test
> > > before committing changes?
> >
> > Yes.
> >
> > > 2. Are developers required to develop a regression test
> > > (if one does not exist) and pass it before committing changes?
> >
> > No.
>
> Aha. A QA loop-hole.
> We can't have that now can we?
That depends.
What matters for the quality of the
product is end-to-end functionality
testing.
For this we have jbosstest.
Some regression tests belong in the
end-to-end functionality testing
category, and such should be added to
jbosstest in case it wasn't there
already. Here we may have a loop-hole,
but I haven't seen any problems
arising from it yet.
Other tests (like unit tests) are not
really done to improve the quality of
the final product, but to improve the
quality of the development process.
But tests do not prove that a product
is bug-free. It only gives you a
certain confidence that whatever is
tested works as tested.
IMHO, what *really* matters for the
quality of JBoss is the large number
of users that are using it in a lot
of different situations, with
different configurations and different
beans. A large part of these users
report when they have problems that
could be bugs in JBoss, and this
enables developers to fix things that
do not work in situations they have
not even thought about.
That does not only help to reduce the
number of bugs in JBoss, but also
makes JBoss more robust. And IMHO
robustness is just as important as
functionality for JBoss.
Best Regards,
Ole Husgaard.
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
