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
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <wbic16@gmail.com>) id 1Y2Sez-0000Mp-8P
for bitcoin-development@lists.sourceforge.net;
Sat, 20 Dec 2014 22:38:05 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.192.171 as permitted sender)
client-ip=209.85.192.171; envelope-from=wbic16@gmail.com;
helo=mail-pd0-f171.google.com;
Received: from mail-pd0-f171.google.com ([209.85.192.171])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Y2Sey-0006q8-0E
for bitcoin-development@lists.sourceforge.net;
Sat, 20 Dec 2014 22:38:05 +0000
Received: by mail-pd0-f171.google.com with SMTP id y13so3450438pdi.16
for <bitcoin-development@lists.sourceforge.net>;
Sat, 20 Dec 2014 14:37:58 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.68.215.100 with SMTP id oh4mr23560655pbc.11.1419115078260;
Sat, 20 Dec 2014 14:37:58 -0800 (PST)
Received: by 10.66.122.231 with HTTP; Sat, 20 Dec 2014 14:37:58 -0800 (PST)
In-Reply-To: <CAJHLa0PBghVhEwWVgH3nXMJAV00OPPPoeZd8qgiCKf07xyEEDg@mail.gmail.com>
References: <CAB2qGxXDtxWxyLUCEZ9XQ4nP0U-Cj5Xiz9ac=vot1H+wzRCHrA@mail.gmail.com>
<CAJHLa0PBghVhEwWVgH3nXMJAV00OPPPoeZd8qgiCKf07xyEEDg@mail.gmail.com>
Date: Sat, 20 Dec 2014 16:37:58 -0600
Message-ID: <CAB2qGxXaxPc3y6HRg4fToPT4SX2bbgsEBYkz5dFQZE7DqGZ4DA@mail.gmail.com>
From: Will Bickford <wbic16@gmail.com>
To: Jeff Garzik <jgarzik@bitpay.com>
Content-Type: multipart/alternative; boundary=001a1134abbc22a022050aad7af8
X-Spam-Score: -0.3 (/)
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
(wbic16[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
0.2 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in
digit (wbic16[at]gmail.com)
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: 1Y2Sey-0006q8-0E
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Area of Focus
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: Sat, 20 Dec 2014 22:38:05 -0000
--001a1134abbc22a022050aad7af8
Content-Type: text/plain; charset=UTF-8
Thanks Jeff. I'll start looking there.
Will Bickford
"In Google We Trust"
On Sat, Dec 20, 2014 at 3:26 PM, Jeff Garzik <jgarzik@bitpay.com> wrote:
> Getting back to the original topic...
>
> I would recommend first taking a look at how the current tests are built
> (via autoconf/automake) in src/test. There are several surfaces to test,
> RPC, REST, P2P, internal unit tests, and more. Then, Travis applies a
> second level of testing via the bitcoinj-based regression tests.
>
> Some automated tests that operate at the Qt level would be interesting.
> In general, the current tests only scratch the surface of what Needs To Be
> Tested... but part of figuring out a good test is (a) knowing bitcoin and
> (b) knowing the current test regimes.
>
> Join #bitcoin-dev IRC and ask questions. Read the bitcoin wiki.
>
>
>
>
> On Sat, Dec 20, 2014 at 2:42 AM, Will Bickford <wbic16@gmail.com> wrote:
>
>> Hi all, I'm looking to help with Bitcoin core development in my spare
>> time (a few hours per week).
>>
>> A little bit about me:
>> * I use C++ and Qt daily
>> * I love to automate and enhance software systems
>> * I enjoy root causing and fixing issues
>>
>> I saw Gavin say we needed help with testing in a Reddit AMA a while ago.
>> I'm curious where I can make the best impact. Any feedback would be
>> appreciated. Thanks!
>>
>> Will Bickford
>> "In Google We Trust"
>>
>>
>> ------------------------------------------------------------------------------
>> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
>> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
>> with Interactivity, Sharing, Native Excel Exports, App Integration & more
>> Get technology previously reserved for billion-dollar corporations, FREE
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Bitcoin-development mailing list
>> Bitcoin-development@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>
>>
>
> --
> Jeff Garzik
> Bitcoin core developer and open source evangelist
> BitPay, Inc. https://bitpay.com/
>
--001a1134abbc22a022050aad7af8
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Thanks Jeff. I'll start looking there.</div><div class=
=3D"gmail_extra"><br clear=3D"all"><div><div class=3D"gmail_signature">Will=
Bickford<br>"In Google We Trust"</div></div>
<br><div class=3D"gmail_quote">On Sat, Dec 20, 2014 at 3:26 PM, Jeff Garzik=
<span dir=3D"ltr"><<a href=3D"mailto:jgarzik@bitpay.com" target=3D"_bla=
nk">jgarzik@bitpay.com</a>></span> wrote:<br><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex"><div dir=3D"ltr"><div><div><div>Getting back to the original topic...<b=
r><br></div>I would recommend first taking a look at how the current tests =
are built (via autoconf/automake) in src/test.=C2=A0 There are several surf=
aces to test, RPC, REST, P2P, internal unit tests, and more.=C2=A0 Then, Tr=
avis applies a second level of testing via the bitcoinj-based regression te=
sts.<br><br></div>Some automated tests that operate at the Qt level would b=
e interesting.=C2=A0 In general, the current tests only scratch the surface=
of what Needs To Be Tested...=C2=A0 but part of figuring out a good test i=
s (a) knowing bitcoin and (b) knowing the current test regimes.<br><br></di=
v>Join #bitcoin-dev IRC and ask questions.=C2=A0 Read the bitcoin wiki.<br>=
<br><div><br><br></div></div><div class=3D"gmail_extra"><br><div class=3D"g=
mail_quote"><div><div class=3D"h5">On Sat, Dec 20, 2014 at 2:42 AM, Will Bi=
ckford <span dir=3D"ltr"><<a href=3D"mailto:wbic16@gmail.com" target=3D"=
_blank">wbic16@gmail.com</a>></span> wrote:</div></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex"><div><div class=3D"h5"><div dir=3D"ltr"><div>Hi all, I'm =
looking to help with Bitcoin core development in my spare time (a few hours=
per week).</div><div><br></div><div>A little bit about me:<br></div><div>*=
I use C++ and Qt daily</div><div>* I love to automate and enhance software=
systems</div><div>* I enjoy root causing and fixing issues</div><div><br><=
/div><div>I saw Gavin say we needed help with testing in a Reddit AMA a whi=
le ago. I'm curious where I can make the best impact. Any feedback woul=
d be appreciated. Thanks!<span><font color=3D"#888888"><br></font></span></=
div><span><font color=3D"#888888"><br clear=3D"all"><div><div>Will Bickford=
<br>"In Google We Trust"</div></div>
</font></span></div>
<br></div></div><span class=3D"">------------------------------------------=
------------------------------------<br>
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server<br>
from Actuate! Instantly Supercharge Your Business Reports and Dashboards<br=
>
with Interactivity, Sharing, Native Excel Exports, App Integration & mo=
re<br>
Get technology previously reserved for billion-dollar corporations, FREE<br=
>
<a href=3D"http://pubads.g.doubleclick.net/gampad/clk?id=3D164703151&iu=
=3D/4140/ostg.clktrk" target=3D"_blank">http://pubads.g.doubleclick.net/gam=
pad/clk?id=3D164703151&iu=3D/4140/ostg.clktrk</a><br>__________________=
_____________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net" target=3D"_bla=
nk">Bitcoin-development@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
<br></span></blockquote></div><span class=3D"HOEnZb"><font color=3D"#888888=
"><br clear=3D"all"><br>-- <br><div>Jeff Garzik<br>Bitcoin core developer a=
nd open source evangelist<br>BitPay, Inc. =C2=A0 =C2=A0 =C2=A0<a href=3D"ht=
tps://bitpay.com/" target=3D"_blank">https://bitpay.com/</a></div>
</font></span></div>
</blockquote></div><br></div>
--001a1134abbc22a022050aad7af8--
|
