public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Niels Thijssen <niels.thijssen@improveqs.nl>
To: "bitcoin-dev@lists.linuxfoundation.org"
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] testing bitcoin nodes
Date: Tue, 6 Aug 2019 10:36:18 +0000	[thread overview]
Message-ID: <AM0PR07MB54748379B8B41BA5023F46CAE9D50@AM0PR07MB5474.eurprd07.prod.outlook.com> (raw)

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.

Who would be able to join me or share information that guides me.
Thanks in advance,

Niels.



-------- Disclaimer --------
This email and any files transmitted may contain proprietary and confidential information of Improve Quality Services B.V. (‘Improve QS’) and is intended only for the (use of the) named recipient(s) above. If you have received this message in error or are not the intended or named recipient(s) of this message, please immediately notify the sender by return and delete this email message from your computer. Any views or opinions presented are solely those of its author and do not necessarily represent those of Improve QS. You are hereby notified that unauthorized disclosure, use, dissemination, forwarding, printing or copying of this e-mail and its attachments either whole or partial of its contents is strictly prohibited. Improve QS cannot guarantee that email communications are secured and error-free and does not accept any liability for damages resulting from the use of email. The general terms and conditions of purchase respectively sale and delivery of Improve QS are applicable to all transactions and undertakings resulting therefrom.


             reply	other threads:[~2019-08-06 10:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-06 10:36 Niels Thijssen [this message]
2019-08-21 12:35 ` [bitcoin-dev] testing bitcoin nodes Niels Thijssen
2019-08-21 17:33   ` Alexander Leishman
2019-08-21 18:33 ` Pieter Wuille

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=AM0PR07MB54748379B8B41BA5023F46CAE9D50@AM0PR07MB5474.eurprd07.prod.outlook.com \
    --to=niels.thijssen@improveqs.nl \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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