Re: Verification of bug fixes

On 2.10.2013 14:57, Rodrigo Rocha Gomes e Souza wrote:

> Thanks for the links, Glenn!
>
> On Tue, Oct 1, 2013 at 10:43 AM, Glenn Holmer <[email protected]
> <mailto:[email protected]>> wrote:
>
>     http://wiki.netbeans.org/__IssueLifeCycle
>     <http://wiki.netbeans.org/IssueLifeCycle>
>
>     https://blogs.oracle.com/__geertjan/entry/15_lessons___learned_from_15
>     <https://blogs.oracle.com/geertjan/entry/15_lessons_learned_from_15>
>
>
> Wow, that's a very interesting presentation! Also, I'm impressed with
> the dashboard at http://services.netbeans.org/dashboard/web/

Thank you Rodrigo!

> So, let me see if I got the typical scenario right:
>
> * a developer marks a bug as FIXED after commiting a patch to the hg repo.

Yes

> * the code in hg repo is built (nightly?)

Yes

> * automated tests are run against the build (since NetBeans 4.0? 3.5?)

4.0

> * a tester (or the reporter) tries to reproduce the bug using the
> build and marks the bug as VERIFIED or REOPENED, according to the outcome.

Yes

> * no code review takes place.

No. For API changes and fixes in High Resistance mode code review is 
done. See for example here: 
https://netbeans.org/bugzilla/show_bug.cgi?id=234353

> Is that right?
>
> Also, do you recall any bug that was reopened because an automated test
> case turned into red?

For example:
https://netbeans.org/bugzilla/show_bug.cgi?id=236010
https://netbeans.org/bugzilla/show_bug.cgi?id=235589

Hope this helps,
-Jirka

> []s
> Rodrigo