From: Arklan Uth Oslin <arklan.uthoslin@gmail•com>
To: Jeff Garzik <jgarzik@exmulti•com>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] On bitcoin testing
Date: Tue, 9 Oct 2012 17:42:31 -0600 [thread overview]
Message-ID: <CAGg41SWAxhGwmMQCnzsBU_0Z=han2JvbTn3CaTFZxqaaTb+AHw@mail.gmail.com> (raw)
In-Reply-To: <CA+8xBpchRLVQW4Rv2RQhsRF716cCTmJLuhZeuvCWtWB4sZX2Sw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3345 bytes --]
thanks for the great reply jeff. i'm going to get a virtual machine set up
on my system later tonight so at the very least, i myself can start testing.
steve - haven't heard from you in almost a week. I'd still really like to
get a look at the test cases and such you set up.
Arklan
----------
As long as there is light, the darkness holds no fear. And yet, even in the
deepest black, there is life. - Arklan Uth Oslin
I want to leave this world the same way I came into it: backwards and on
fire. - Arklan Uth Oslin
On Tue, Oct 9, 2012 at 5:12 PM, Jeff Garzik <jgarzik@exmulti•com> wrote:
> Copying from a response posted to "Bitcoin software testing effort"
> https://bitcointalk.org/index.php?topic=117487.0 as it is relevant to
> a recent thread here...
>
> Any level of testing is useful and appreciated. Various types of
> testing that are helpful:
>
> * "it works" testing: Simply run the latest Release Candidate (or
> latest version, if released). Make sure all the basics work (for
> whatever definition of "basics" you desire). This is the level most
> accessible to casual users.
> * Major features testing: Develop a short checklist of must-work
> features, and organize volunteers to work together and go through that
> checklist, item by item. Test each major feature on each major
> platform.
> * Stress and fuzz testing: Attempt to "stress" the system somehow, or
> randomly corrupt bits of data. See what breaks.
> * Regression testing: Record bugs fixed, and develop automated test
> cases that successfully reproduce the bugs on older versions, and
> verify newer versions remain fixed.
> * Unit function testing: Rigorously exercise each C++ class to ensure
> it behaves as expected at a micro level.
> * Full peer automated testing: Automated testing of RPC and P2P
> functions is non-existent, because of the difficulty in doing so.
> Find a solution to this problem.
> * Data-driven tests: If possible, write software-neutral, data-driven
> tests. This enables clients other than the reference one (Satoshi
> client) to be tested. Embed tests in testnet3 chain, if possible.
>
>
> The community at large can be a big help simply by doing the first
> item: download and run the Release Candidates and the latest version,
> and report any problems. Even reporting success is fine by me, for
> example: "Version 0.7.1 works for me on Windows 7/32-bit" posted on a
> forum thread.
>
> It is always very difficult to organize any sort of testing regime
> with open source volunteers that come and go. Each volunteer chooses
> their level of involvement. Any amount of testing and test-case
> writing, large or small, is helpful to bitcoin.
>
> --
> Jeff Garzik
> exMULTI, Inc.
> jgarzik@exmulti•com
>
>
> ------------------------------------------------------------------------------
> Don't let slow site performance ruin your business. Deploy New Relic APM
> Deploy New Relic app performance management and know exactly
> what is happening inside your Ruby, Python, PHP, Java, and .NET app
> Try New Relic at no cost today and get our sweet Data Nerd shirt too!
> http://p.sf.net/sfu/newrelic-dev2dev
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
[-- Attachment #2: Type: text/html, Size: 4291 bytes --]
next prev parent reply other threads:[~2012-10-09 23:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-09 23:12 Jeff Garzik
2012-10-09 23:42 ` Arklan Uth Oslin [this message]
2012-10-10 0:03 ` Gregory Maxwell
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='CAGg41SWAxhGwmMQCnzsBU_0Z=han2JvbTn3CaTFZxqaaTb+AHw@mail.gmail.com' \
--to=arklan.uthoslin@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=jgarzik@exmulti$(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