Re: Verification of bug fixes

--047d7bae47383e53fd04e7c19dd6
Content-Type: text/plain; charset=ISO-8859-1

Thanks for the links, Glenn!

On Tue, Oct 1, 2013 at 10:43 AM, Glenn Holmer <[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/

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.
* the code in hg repo is built (nightly?)
* automated tests are run against the build (since NetBeans 4.0? 3.5?)
* 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.
* no code review takes place.

Is that right?

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

[]s
Rodrigo

--047d7bae47383e53fd04e7c19dd6
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thanks for the links, Glenn!<div class=3D"gmail_extra"><br=
><div class=3D"gmail_quote">On Tue, Oct 1, 2013 at 10:43 AM, Glenn Holmer <=
span dir=3D"ltr">&lt;<a href=3D"mailto:[email protected]" target=3D"_b=
lank">[email protected]</a>&gt;</span> wrote:<br>


<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><div><a href=3D"http://wiki.netbeans.org/IssueLifeCycle" t=
arget=3D"_blank">http://wiki.netbeans.org/<u></u>IssueLifeCycle</a><br>

</div></blockquote><blockquote class=3D"gmail_quote" style=3D"margin:0px 0p=
x 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border=
-left-style:solid;padding-left:1ex"><a href=3D"https://blogs.oracle.com/gee=
rtjan/entry/15_lessons_learned_from_15" target=3D"_blank">https://blogs.ora=
cle.com/<u></u>geertjan/entry/15_lessons_<u></u>learned_from_15</a></blockq=
uote>

<div><br></div><div>Wow, that&#39;s a very interesting presentation! Also, =
I&#39;m impressed with the dashboard at <a href=3D"http://services.netbeans=
.org/dashboard/web/" target=3D"_blank">http://services.netbeans.org/dashboa=
rd/web/</a></div>


<div><br></div><div style>So, let me see if I got the typical scenario righ=
t:</div><div style><br></div><div style>* a developer marks a bug as FIXED =
after commiting a patch to the hg repo.</div><div style>* the code in hg re=
po is built (nightly?)=A0</div>

<div style>* automated tests are run against the build (since NetBeans 4.0?=
 3.5?)</div><div style>* a tester (or the reporter) tries to reproduce the =
bug using the build=A0and marks the bug as VERIFIED or REOPENED, according =
to the outcome.</div>

<div style>* no code review takes place.</div><div style><br></div><div sty=
le>Is that right?=A0</div><div style><br></div><div style>Also, do you reca=
ll any bug that was reopened because an automated test case turned into red=
?</div>

<div style><br></div><div style>[]s<br></div><div style>Rodrigo</div></div>=
</div></div>

--047d7bae47383e53fd04e7c19dd6--