From: Will Bickford <wbic16@gmail•com>
To: Jeff Garzik <jgarzik@bitpay•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Area of Focus
Date: Sat, 20 Dec 2014 16:37:58 -0600 [thread overview]
Message-ID: <CAB2qGxXaxPc3y6HRg4fToPT4SX2bbgsEBYkz5dFQZE7DqGZ4DA@mail.gmail.com> (raw)
In-Reply-To: <CAJHLa0PBghVhEwWVgH3nXMJAV00OPPPoeZd8qgiCKf07xyEEDg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2174 bytes --]
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/
>
[-- Attachment #2: Type: text/html, Size: 3635 bytes --]
prev parent reply other threads:[~2014-12-20 22:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-20 7:42 Will Bickford
2014-12-20 8:57 ` Matt Corallo
2014-12-20 10:08 ` Roy Badami
2014-12-20 11:14 ` Jeremy Spilman
2014-12-20 21:20 ` Matt Corallo
2014-12-20 21:30 ` Gregory Maxwell
2014-12-20 18:27 ` Christian Decker
2014-12-20 21:26 ` Jeff Garzik
2014-12-20 22:37 ` Will Bickford [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAB2qGxXaxPc3y6HRg4fToPT4SX2bbgsEBYkz5dFQZE7DqGZ4DA@mail.gmail.com \
--to=wbic16@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=jgarzik@bitpay$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox