summaryrefslogtreecommitdiff
path: root/3f/d7f1b5bcff2de7ca2b1f7a63d4acb8c4ea39fb
blob: 72c7cdb847ef8cdf1256288c733a04d9c4073e2c (plain)
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
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <gavinandresen@gmail.com>) id 1QbNjc-0000au-1q
	for bitcoin-development@lists.sourceforge.net;
	Tue, 28 Jun 2011 02:09:04 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.210.47 as permitted sender)
	client-ip=209.85.210.47; envelope-from=gavinandresen@gmail.com;
	helo=mail-pz0-f47.google.com; 
Received: from mail-pz0-f47.google.com ([209.85.210.47])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128)
	(Exim 4.76) id 1QbNjb-00080C-8r
	for bitcoin-development@lists.sourceforge.net;
	Tue, 28 Jun 2011 02:09:03 +0000
Received: by pzk36 with SMTP id 36so4256376pzk.34
	for <bitcoin-development@lists.sourceforge.net>;
	Mon, 27 Jun 2011 19:08:57 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.142.237.21 with SMTP id k21mr483672wfh.271.1309226937340; Mon,
	27 Jun 2011 19:08:57 -0700 (PDT)
Received: by 10.142.153.7 with HTTP; Mon, 27 Jun 2011 19:08:57 -0700 (PDT)
Date: Mon, 27 Jun 2011 22:08:57 -0400
Message-ID: <BANLkTi=ELrQjh=ocB53mpdfPcK601qFHgQ@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: text/plain; charset=ISO-8859-1
X-Spam-Score: -1.5 (-)
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
	-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
	0.1 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1QbNjb-00080C-8r
Subject: [Bitcoin-development] Test away
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: Tue, 28 Jun 2011 02:09:04 -0000

I got Steve-from-the-Forum's boost unit test skeleton code compiling
and running, so there's now a src/test directory and you can 'make -f
makefile.unix test_bitcoin'

More tests are very welcome. I'd welcome higher-level tests (not just
code unit tests), too.

And speaking of testing:  if you know a good QA test manager type
person interested in bitcoin, I think we can wrangle up funding for
somebody to put together a team to help test bitcoin (and hopefully
pull requests). I think lack of testing resources for core bitocin is
a big weakness right now.

-- 
--
Gavin Andresen