Hi Frank,
don't have something (in this very mail) about the "what to do with the
bug pile" topic, but a few other items cried for my response ...
To improve this we need people who write Testtool testscripts.
I disagree. The problem is not finding the bugs.
Using the Testtool is very useful to find regressions by comparing
result files of eg. a CWS build with result files of the corresponding
master workspace.
Not sure. Looking at the amount of stoppers which came in in 3.1's
release phase, and the amount of stoppers already raised for 3.1.1 (and
most often for good reasons), I think that *finding* bugs *is* a problem.
Of course, or at least in my opinion: Automatically finding bugs is just
*one* line of defense. There are others, and personally, I think another
line of defense must be with the Devs, by not *introducing* the bugs.
IMO, we take way too little measures to prevent bugs, we always
concentrate on finding and fixing them.
You're describing the perfect world where developers don't introduce new
bugs ;-)
<snip>
</snip>
- verifying issues of just integrated child workspaces within the current
master build (to verify there are no integration related issues regarding
this CWS)
Jup, nice janitorial task that takes off some workload of the other
QA/Devs that can focus on other tasks
+1
From your experience: Is this worth it? I mean, we probably all agree
that in the current modus operandi, there's more work for both QA and
Dev than they can accomplish (that's why changing this modus is one of
the topics of this thread, as I understand it.). An no, that's not an
excuse, that's a matter of fact which we need to deal with.
So, in how many cases did checking a VERIFIED FIXED issue in the MWS
really detect a problem? And in how many cases was it just moving the
issue to CLOSED?
I'm asking because my gut feeling is that the latter takes too much
time. And seeing that all issues have already been VERIFIED in the CWS,
and assuming that *breaking* a fix by merely integrating the CWS is
unlikely (though surely possible), I wonder whether auto-CLOSING issues
would free previous QA resources.
I have a different experience regarding this topic. In the past I
remember cases where the integration of child workspaces integrated new
regressions because the integration failed or dependencies between child
workspaces were not solved correctly during integration work. OK this
case is rare but it's better to check a proper integration than to find
the regressions weeks after integration.
Kind regards, Joost
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
