From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Y2RyJ-0007S4-CC for bitcoin-development@lists.sourceforge.net; Sat, 20 Dec 2014 21:53:59 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of bitpay.com designates 209.85.214.178 as permitted sender) client-ip=209.85.214.178; envelope-from=jgarzik@bitpay.com; helo=mail-ob0-f178.google.com; Received: from mail-ob0-f178.google.com ([209.85.214.178]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Y2RyG-000683-M5 for bitcoin-development@lists.sourceforge.net; Sat, 20 Dec 2014 21:53:57 +0000 Received: by mail-ob0-f178.google.com with SMTP id gq1so16976730obb.9 for ; Sat, 20 Dec 2014 13:53:51 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=i6Rsbf0InlQ+T6fSQe47+swageun9Kr8RSMijhtdofk=; b=Gxhxu26JUYcjb1xmeEct1FBInyoQ7zKdobFrhvHkFEj2Q7udFmI9/C0vZGJbAojcjM yNatDml+H09tYoOIGOTx7kq13Y9PmXGeCHXPcXmNbQSKdet1kAuYHcVlF7JmcBfJegq/ 9oTjRi1sBrT9QZd8QF+5x9jOHQAEjHyK3GRdqS+E4bzCd3/zu9KHuc+BiyJdYMwle/+n EeiLcis8Dvx4qOb09VW4gdr8dUr41RGEZPzKrmKOX0x4MjP8oZ2m2BjrrcdfY4kPUEDK gK5+UQ7g4eRj2fFKycjZ/wQBCeKOqI6lDF0od+8OPSoHLhYskcXniADIFiJ+uts8S6vd WRug== X-Gm-Message-State: ALoCoQl7UG6mN4C9wvTyMJX7dTyqeXwab6RQTuXkgjs6xF1P9x2BdjPWj9WdUNg4tKKhCuqrQFbt X-Received: by 10.202.94.66 with SMTP id s63mr8122449oib.41.1419110801270; Sat, 20 Dec 2014 13:26:41 -0800 (PST) MIME-Version: 1.0 Received: by 10.202.193.137 with HTTP; Sat, 20 Dec 2014 13:26:20 -0800 (PST) In-Reply-To: References: From: Jeff Garzik Date: Sat, 20 Dec 2014 16:26:20 -0500 Message-ID: To: Will Bickford Content-Type: multipart/alternative; boundary=001a113d395835072c050aac7b54 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 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: 1Y2RyG-000683-M5 Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Area of Focus X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Dec 2014 21:53:59 -0000 --001a113d395835072c050aac7b54 Content-Type: text/plain; charset=UTF-8 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 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/ --001a113d395835072c050aac7b54 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
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.=C2=A0 There are several surfaces= to test, RPC, REST, P2P, internal unit tests, and more.=C2=A0 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 in= teresting.=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 is (a= ) knowing bitcoin and (b) knowing the current test regimes.

Jo= in #bitcoin-dev IRC and ask questions.=C2=A0 Read the bitcoin wiki.

=


--001a113d395835072c050aac7b54--