Re: Verification of bug fixes
Emilian Bold <[email protected]> Sun, 6 Oct 2013 21:08:27 +0300
| Newsgroups | gmane.comp.java.netbeans.general |
|---|---|
| Message-ID | <[email protected]> |
--Apple-Mail-1--951218049 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Also see the work of Marcelo Serrano Zanetti which also did an analysis = of the issues last year: = http://www.sg.ethz.ch/media/publication_files/seipicse2013.pdf He might = even help you with some of the questions from an outsider's pow. We also had some similar analysis done a few years before but I don't = have links saved. Please provide a link to your paper when you are finished. --emi On Oct 1, 2013, at 12:28 PM, Rodrigo Rocha Gomes e Souza wrote: > Hi, >=20 > I'm a PhD student at the Federal University of Bahia, Brazil. As part = of my research, I'm analyzing NetBeans Platform bug reports to try to = understand how software verification/testing can be made more effective. >=20 > However, it's hard to reach meaningful conclusions only looking at bug = reports; I need some feedback from the community to understand what = happens behind the scenes. For example: >=20 > * when someone marks a bug as VERIFIED, does it mean that the bug fix = was manually tested? Or that the source code was reviewed? Or it = depends? > * do you use automated tests? If so, when are they run? >=20 > I really appreciate any information you can provide to help me = understand the verification process in NetBeans Platform. >=20 > Best regards, > Rodrigo --Apple-Mail-1--951218049 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii <html><head></head><body style=3D"word-wrap: break-word; = -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Also = see the work of Marcelo Serrano Zanetti which also did an analysis = of the issues last year: <a = href=3D"http://www.sg.ethz.ch/media/publication_files/seipicse2013.pdf">ht= tp://www.sg.ethz.ch/media/publication_files/seipicse2013.pdf</a> He = might even help you with some of the questions from an outsider's = pow.<div><br></div><div>We also had some similar analysis done a = few years before but I don't have links = saved.</div><div><br></div><div>Please provide a link to your paper when = you are = finished.</div><div><div><br></div><div>--emi</div><div><br><div><div>On = Oct 1, 2013, at 12:28 PM, Rodrigo Rocha Gomes e Souza wrote:</div><br = class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div = dir=3D"ltr">Hi,<div><br></div><div>I'm a PhD student at the Federal = University of Bahia, Brazil. As part of my research, I'm analyzing = NetBeans Platform bug reports to try to understand how software = verification/testing can be made more effective.</div> <div><br></div><div>However, it's hard to reach meaningful conclusions = only looking at bug reports; I need some feedback from the community to = understand what happens behind the scenes. For = example:</div><div><br></div> <div>* when someone marks a bug as VERIFIED, does it mean that the bug = fix was manually tested? Or that the source code was reviewed? Or it = depends?</div><div>* do you use automated tests? If so, when are they = run?</div> <div> <br></div><div>I really appreciate any information you can provide to = help me understand the verification process in NetBeans = Platform.</div><div><br></div><div>Best = regards,</div><div>Rodrigo</div></div> </blockquote></div><br></div></div></body></html>= --Apple-Mail-1--951218049--