From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 763B4CE5 for ; Wed, 21 Aug 2019 17:33:43 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-qt1-f178.google.com (mail-qt1-f178.google.com [209.85.160.178]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id B781489E for ; Wed, 21 Aug 2019 17:33:40 +0000 (UTC) Received: by mail-qt1-f178.google.com with SMTP id 44so3980165qtg.11 for ; Wed, 21 Aug 2019 10:33:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=2mKGueCl0ZOF4hqiw07lnfW0j+GofJi1wy51ugpLW/8=; b=Z7od1lqmHAvSwyPTMpkk/nVRS37Fts9VgS6VoM2/kp23w/Ac6SyZN/9rN3hJpyZfMs 0elujMmXKhDLMBfJzDLbRbMaLWcLphTP/YTV6DwwTY37l+RWsnWxHzJQObbpEIIAJY0+ eFnJNZX0tGBfG3XLkBjRNPM5uy1RgjvWuyworp6pzL0+HjM+4HfUCRn6ac45U7ZvTNFh q6dKt7kkxCwEBaLoTxW2dAUnnVmNnu92fyL+8ZKx8FbVV60FHffZmmYBdju9Mjc8W5+5 2NMesEBFilOB3QRPrEwFhLh6XTBTUOCL7av4xv4vBKJ01eku8FmMXXnHpWgSlwwfDeKN GTIg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=2mKGueCl0ZOF4hqiw07lnfW0j+GofJi1wy51ugpLW/8=; b=nq7qeWtKk9bk+L3JD/RUMMPxc8NH/LWKcdvdDDcTAC5qd+EAjLq2t1uxNVdkHdxbq2 DWjQfMFb1fvHV1lKSp+j5pqEwfm3Ba6zAn5wuoIvyQnb5I7dMcs/nVhOSKYvNSRzMEA0 4jT4aDWZAb5quAqzrpgLiJ+Fy50UJ7n/OzfwmzC8t79JZdLMdtq3nUSDu1ot1BlWVzqy rp3AIand9b6Y1mC6wyDcR2rAQM9op5SbT9u9BSkUAe6AMdqdbDyghOsEOxw1ojMekpv/ k+RnSl9Jltf+m9B022ymhuK3AbwYL7kOer4h5/97FoU+eBMorajmreWDg2GzhHOfLTms o+7g== X-Gm-Message-State: APjAAAUOOWVwxP96dnoGUDlCyhsMUIWqEbHMXJSdRmHS4hnHGOyDz8/+ QDHQP08DCXfjvkLAs1qKiYOMUX/Z9Vx65zyuB0kd7itTnSI= X-Google-Smtp-Source: APXvYqyYMd0qpqSGu4h23qsl9Jj+nE0hESILeNqfIfG6ELH4teMvlnmYz/FxBqT36cae1XWF5ZJQ+tLcOGvesnFdclY= X-Received: by 2002:ac8:6105:: with SMTP id a5mr31919143qtm.285.1566408819690; Wed, 21 Aug 2019 10:33:39 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Alexander Leishman Date: Wed, 21 Aug 2019 10:33:28 -0700 Message-ID: To: Niels Thijssen , Bitcoin Protocol Discussion Content-Type: multipart/alternative; boundary="00000000000045564f0590a3f906" X-Spam-Status: No, score=-1.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM, HTML_MESSAGE,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org X-Mailman-Approved-At: Wed, 21 Aug 2019 17:37:19 +0000 Subject: Re: [bitcoin-dev] testing bitcoin nodes X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Aug 2019 17:33:43 -0000 --00000000000045564f0590a3f906 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hey Niels, I'm no expert on bitcoind tests, but maybe these bits of information can help you get started: The steps to build bitcoind typically involve running: ./autogen.sh ./configure make make install When you run autogen, the autoreconf tool is invoked which creates the configure script that gets run next. The configure script is generated based on the configure.ac file, which performs a number of compatibility checks for the compiler and other tooling. You can see these checks being performed with the AX_CHECK_COMPILE_FLAG calls. My understanding is that running configure does a lot of system compatibility checks. When you run "make", I do not think any tests get run by default, but I could be wrong about this. If you want to run unit tests you need to run "make check". You can read more about this here There are unit tests for bitcoind written in C++ and a lot of integration and higher level tests written in python. Hopefully this information was useful and accurate. Again, I could be wrong about exactly how the build process works as it's not super obvious. Hopefully someone else more knowledgeable than me can chime in here if I got anything wrong. Best, Alex On Wed, Aug 21, 2019 at 10:06 AM Niels Thijssen via bitcoin-dev < bitcoin-dev@lists.linuxfoundation.org> wrote: > > As no one was able to respond, a gentle reminder : =F0=9F=98=8A > > 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. (=E2=80=98Impro= ve QS=E2=80=99) > and is intended only for the (use of the) named recipient(s) above. If yo= u > 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 communication= s > 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 a= ll > transactions and undertakings resulting therefrom. > > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev > --00000000000045564f0590a3f906 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Hey Niels,


I'm no expert on bitcoind = tests, but maybe these bits of information can help you get started:


The steps to build bitcoind ty= pically involve running:


./autogen.sh

./configure

make

make install


When you run autogen, the=C2= =A0autoreconf=C2=A0tool is invoked which creates = the configure script that gets run next. The configure script is generated = based on the=C2=A0con= figure.ac=C2=A0file, which performs a number of compatibility ch= ecks for the compiler and other tooling. You can see these checks being per= formed with the=C2=A0AX_CHECK_COMPILE_FLAG calls.=C2=A0


My understanding is that runni= ng configure does a lot of system compatibility checks. When you run "= make", I do not think any tests get run by default, but I could be wro= ng about this. If you want to run unit tests you need to run "make che= ck". You can read more about this here



Hope= fully this information was useful and accurate. Again, I could be wrong abo= ut exactly how the build process works as it's not super obvious. Hopef= ully someone else more knowledgeable than me can chime in here if I got any= thing wrong.


Best,

Alex


=


On Wed, Aug 21, 2019 at 10:06 AM Niels Thijssen via bitcoin-dev <bitcoin-dev@lists.lin= uxfoundation.org> wrote:

As no one was able to respond, a gentle reminder : =F0=9F=98=8A

Hi,

I'm working as (software) test specialist and run private a full bitcoi= n 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 st= uff. 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 confidenti= al information of Improve Quality Services B.V. (=E2=80=98Improve QS=E2=80= =99) 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 r= ecipient(s) of this message, please immediately notify the sender by return= and delete this email message from your computer. Any views or opinions pr= esented are solely those of its author and do not necessarily represent tho= se of Improve QS. You are hereby notified that unauthorized disclosure, use= , dissemination, forwarding, printing or copying of this e-mail and its att= achments either whole or partial of its contents is strictly prohibited. Im= prove QS cannot guarantee that email communications are secured and error-f= ree 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.

_______________________________________________
bitcoin-dev mailing list
= bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mail= man/listinfo/bitcoin-dev
--00000000000045564f0590a3f906--