From: Pieter Wuille <pieter.wuille@gmail•com>
To: Niels Thijssen <niels.thijssen@improveqs•nl>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] testing bitcoin nodes
Date: Wed, 21 Aug 2019 11:33:03 -0700 [thread overview]
Message-ID: <CAPg+sBi2Wvh-x0fDVNvAR8ET4OGbbgoegEydaKOaeF4FOWffXQ@mail.gmail.com> (raw)
In-Reply-To: <AM0PR07MB54748379B8B41BA5023F46CAE9D50@AM0PR07MB5474.eurprd07.prod.outlook.com>
On Tue, 6 Aug 2019 at 09:57, Niels Thijssen via bitcoin-dev
<bitcoin-dev@lists•linuxfoundation.org> wrote:
>
> Hi,
>
> I'm working as (software) test specialist and run private a full bitcoin node (based upon Raspberry Pi 4).
> I've been trying to figure out the tests performed during installation/upgrade/compilation of the software for the node.
> Is there any overview on what's the (common) test approach, or other stuff. Because the tests on GitHub don't help me that much.
> I'd like to figure out what/how is tested, maybe refine test cases, and try some manual test also, as part of learning.
Hi Niels,
You're probably not getting many answers because this isn't the right
place to ask. The mailinglist is about development of the Bitcoin
protocol and conventions about its usage across multiple applications.
If you want to learn about the Bitcoin Core software and its testing
infrastructure, see https://bitcoincore.org/en/contribute/
Cheers,
--
Pieter
prev parent reply other threads:[~2019-08-21 18:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 10:36 Niels Thijssen
2019-08-21 12:35 ` Niels Thijssen
2019-08-21 17:33 ` Alexander Leishman
2019-08-21 18:33 ` Pieter Wuille [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=CAPg+sBi2Wvh-x0fDVNvAR8ET4OGbbgoegEydaKOaeF4FOWffXQ@mail.gmail.com \
--to=pieter.wuille@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=niels.thijssen@improveqs$(echo .)nl \
/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