1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gavinandresen@gmail.com>) id 1TGwAA-0002Ad-48
for bitcoin-development@lists.sourceforge.net;
Wed, 26 Sep 2012 18:16:46 +0000
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;
Received: from mail-wi0-f181.google.com ([209.85.212.181])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1TGwA4-0002jn-LY
for bitcoin-development@lists.sourceforge.net;
Wed, 26 Sep 2012 18:16:46 +0000
Received: by wibhq12 with SMTP id hq12so832559wib.10
for <bitcoin-development@lists.sourceforge.net>;
Wed, 26 Sep 2012 11:16:34 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.216.82.16 with SMTP id n16mr92293wee.44.1348682995858; Wed, 26
Sep 2012 11:09:55 -0700 (PDT)
Received: by 10.194.17.138 with HTTP; Wed, 26 Sep 2012 11:09:55 -0700 (PDT)
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
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(gavinandresen[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1TGwA4-0002jn-LY
Cc: Bitcoin Development List <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin Testing Project
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Wed, 26 Sep 2012 18:16:46 -0000
--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'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 "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)."</div>
<div><br></div><div>Thanks to Matt, we're doing great with automated fu=
nctional test cases (can always do better, of course).</div><div><br></div>=
<div>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. Th=
at is where I think a QA team can add a lot of value.</div>
<div><br></div><div>Steve: I'm worried you'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--
|
