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. Ciao Frank -- - Frank Schönheit, Software Engineer [email protected] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
