3

You are confusing the two kinds of tests. Unit tests are compiled into a separate binary and run by make check. Functional tests are testing the RPC commands and have to be run explicitly using the test_runner.py script. test_framework.log is only created by the functional tests. The documentation for the unit tests can be found here. To print messages in ...


3

This is the output for all platforms at the moment, not just MacOS. To paraphrase from sipa on IRC: The first summary is bitcoin's own summary: because of some hackery to run unit tests in parallel, it currently shows no tests (even though they are executed). The second and third summary are the output from make check for the built-in dependencies, ...


2

Marco Falke has a site that analyzes the current line, function and branch coverage for unit tests, functional tests and fuzz tests. Alternatively, vasild runs clang's tools and then a script to highlight which lines in the coverage report have been modified by a particular patch (PR).


2

If you watched Fabian's presentation (or read the transcript) you'll have seen that he said you can use Valgrind for memory leak checks and that it can be used similarly to lldb. valgrind --leak-check=yes src/bitcoind -regtest There is a section in Fabian's doc on debugging Bitcoin with instructions on how to install Valgrind on MacOS and run it. Install ...


2

You opened a 1 million Satoshi channel and send 500 sats to the other side. The protocol requires a 1%channel reserve kept on both sides for the penalty mechanism to always have enough collateral. This one percent is ignored initially if you never had that much balance (e. G. On new channels) but is the reason why you can't send sats unless you met the 1% ...


1

Here is my work around. I still have a hard time believing that the test code needs revision, but this is what I did and the tests now pass. From the above, I changed the call of RunCommandParseJSON() to provide for the explicit call of the command window. Apparently, this is needed for Windows. The line became: 57 const UniValue result = ...


1

What backward compatibility testing is done to ensure the latest release passes previous releases' versions of the functional tests? There is a feature_backwards_compatibility.py functional test which spins up functional test nodes from each of the previous releases to do testing between them at the same time. Once you have built the latest version of ...


1

PR #8836 was one of John Newbery's earlier contributions to Bitcoin Core. He introduced this code so that bitcoin-util-test.py would fail when the output_cmp file is empty. if not outputData: print("Output data missing for " + outputFn) sys.exit(1) PR #16445 was Fabian Jahr's first contribution to Bitcoin Core. One ...


1

If you are learning C++ from scratch you may struggle to start writing unit tests to begin with even if you identify a particular unit test that is missing. So that is one challenge. In terms of discovering a missing unit test to write there are various ways to do this. It is worth monitoring the good first issues on the GitHub repo though I think that would ...


1

Jumping straight to writing unit test can be hard, I suggest You check the official github page for how to contribute to the bitcoin core: https://github.com/bitcoin/bitcoin/blob/master/CONTRIBUTING.md If I wanted to contribute I would personally start by trying to solve some of the problems on their issues page because it is fresh, there is a lot of work, ...


Only top voted, non community-wiki answers of a minimum length are eligible