Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.212.181 as permitted sender)
	client-ip=209.85.212.181; envelope-from=gavinandresen@gmail.com;
	helo=mail-wi0-f181.google.com; 
MIME-Version: 1.0
In-Reply-To: <50633F02.6030807@mistfpga.net>
References: <5061F8CC.9070906@mistfpga.net>
	<1348605677.2284.2.camel@localhost.localdomain>
	<5062F4F8.6040504@mistfpga.net>
	<CA+s+GJBM4DwDoqT8RC0+SyrLYrLGZuGZSuoj7zbHunQa3kFoRA@mail.gmail.com>
	<506301AC.90101@mistfpga.net>
	<CACh7GpHFY_KUhhtk09H_oCzBtRh66artDCqz8pXNTh_ZzkAABg@mail.gmail.com>
	<50633F02.6030807@mistfpga.net>
Date: Wed, 26 Sep 2012 14:09:55 -0400
Message-ID: <CABsx9T119rT1NssV6YO8KPse3sEGHZJ-vzFFD3o=aAQ161g6-A@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: steve <steve@mistfpga.net>
Content-Type: multipart/alternative; boundary=0016e6de008be1fbca04ca9ebaa0
Cc: Bitcoin Development List <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin Testing Project
Precedence: list

--0016e6de008be1fbca04ca9ebaa0
Content-Type: text/plain; charset=ISO-8859-1

There are test cases that can be automated. That's Jenkins, and those will
be run automagically.

Then there are tests that cannot be automated; things like "Does the GUI
look OK on all of the platforms that we support (Windows XP/2000/Vista/7/8,
Ubuntu/Debian blah with window managers foo and bar, OSX 10.5/6/7/8)."

Thanks to Matt, we're doing great with automated functional test cases (can
always do better, of course).

We're failing on simple, boring stuff like making sure we actually run on
all of the platforms that we say we run on BEFORE final release. That is
where I think a QA team can add a lot of value.

Steve: I'm worried you're over-designing The Process. A release acceptance
test plan could be nothing more than a step-by-step checklist on a wiki
page, Google Doc, or Drobox shared folder...

-- 
--
Gavin Andresen

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

<div>There are test cases that can be automated. That&#39;s Jenkins, and th=
ose will be run automagically.</div><div><br></div><div>Then there are test=
s that cannot be automated; things like &quot;Does the GUI look OK on all o=
f the platforms that we support (Windows XP/2000/Vista/7/8, Ubuntu/Debian b=
lah with window managers foo and bar, OSX 10.5/6/7/8).&quot;</div>
<div><br></div><div>Thanks to Matt, we&#39;re doing great with automated fu=
nctional test cases (can always do better, of course).</div><div><br></div>=
<div>We&#39;re failing on simple, boring stuff like making sure we actually=
 run on all of the platforms that we say we run on BEFORE final release. Th=
at is where I think a QA team can add a lot of value.</div>
<div><br></div><div>Steve: I&#39;m worried you&#39;re over-designing The Pr=
ocess. A release acceptance test plan could be nothing more than a step-by-=
step checklist on a wiki page, Google Doc, or Drobox shared folder...</div>
<div><br></div>-- <br>--<br>Gavin Andresen<br><br>

--0016e6de008be1fbca04ca9ebaa0--