On 2009.03.13. 12:37, Frank Schönheit - Sun Microsystems Germany wrote:
Hi Rich,
summary - while release early, release often is very important, stable
dev snapshots are as important.
Yes, but how to reach that? In theory, trunk is always stable, since
every CWS has undergone tests (before integration) which ensure that it
doesn't break anything. Okay, enough laughing.
haha. almost got me there :)
Finally, that's exactly the problem here: Too many serious bugs slip
Dev/QA's attention in the CWS, and are found on trunk only. If we fix
that, trunk will automatically be much more stable. Easy to say, hard to do.
when i wrote serious problems i meant something similar to a recent
issue in a dev build where simply accessing tools->options crashed oo.org.
i believe that reducing the amount of such simple to find problems would
be a notable step forward, and what's important - these tests should be
relatively easy to automate.
i'll admit ignorance on current automated testing processes, but stuff
that would walk through all menu options (with some advanced custom
paths), a repository of testdocs in various formats etcetc.
this, of course, correlates with testing process discussions on this
thread, which means more work creating tests - but i'm trying to hilight
simple problems that somehow slip past this process. i mean, if crash on
opening options slipped past it, there aren't enough of these simple
checks which, i hope, would take less developer (or even qa) time to
develop.
if test creation is too complex and there are ways to simplify it, that
could be made a priority. such a change would improve long term quality
and reduce workload, so it seems to be worth concentrating on.
obviously, that's just a small improvement, seen through my "lens",
which should be viewed in context with other things already mentioned.
Ciao
Frank
--
Rich
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
