On 2009.03.13. 12:08, Frank Schönheit - Sun Microsystems Germany wrote:
Hi Ingrid,
that now bite us, most of them have been found by users or testers
*working* with the program. Adding more CWS test runs and so shortening
the time for real-life testing will not help us but make things worse.
I don't agree. Preventing the integration of bugs earlier in the
production phase especially before the integration into the master trunk
would give us much more freedom. Now we always need to react on show
stoppers and react and react and uh then the release time line is on
risk. All that, because the bugs are already in the product. If you
instead detect the bugs before they are integrated into the product you
can keep cool, refuse the bad CWS and thus not the release is on risk
but only the single bad CWS.
Hmmm ... difficult.
On the one hand, I agree (and this is what you can read in every QA
handbook) that finding bugs earlier reduces the overall costs.
On the other hand, I suppose (! - that's an interesting facet to find
out when analyzing the current show stoppers: found by whom?) that in
fact the majority of problems are found during real-life usage. And
nobody will use a CWS in real life. So, getting the CWS into the MWS
early has its advantages, too.
seeing as my bug made the list, i'll chime in.
i've reported quite some bugs, absolute majority being found in real
life usage. but i'm not the casual user, as i run dev snapshots most of
the time, which increases chances of stumbling upon bugs.
i'd like to think i'm not the only one who does that ;), so i think this
is the group that would find most of the stoppers in real life scenarios
(that slipped past automated testing). important factor would be to get
as many users (and developers !) as possible doing the same.
i think you already have guessed where i'm heading - stability and
usability (as in "fit for purpose") of dev snapshots. if dev snapshot
has a critical problem that prevents me from using it i'll "regress" to
last stable version, and, quite likely, will stay with it for a while.
that means i won't find some other bug that will prevent somebody else
from using a dev build and finding yet another bug and so on ;)
many opensource projects tend to keep trunk relatively stable to
increase the proportion of users why stay on trunk, and use trunk
themselves. thus breakages are discovered sooner.
summary - while release early, release often is very important, stable
dev snapshots are as important.
Ciao
Frank
--
Rich
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
