Inside Bitcoin
Opening the selected file…
Inside Bitcoin
Opening the selected file…
The code behind the network, with room to understand it.
Release published 2026-10-28 · Snapshot fetched 2026-11-01. Latest stable release at fetch time; development branches and Git history are excluded. Only the selected code window and visible folders load here.
1# Unit tests3The sources in this directory are unit test cases. Boost includes a4unit testing framework, and since Bitcoin Core already uses Boost, it makes5sense to simply use this framework rather than require developers to6configure some other framework (we want as few impediments to creating7unit tests as possible).9The build system is set up to compile an executable called `test_bitcoin`10that runs all of the unit tests. The main source file for the test library is found in11`util/setup_common.cpp`.13The examples in this document assume the build directory is named14`build`. You'll need to adapt them if you named it differently.16### Compiling/running unit tests18Unit tests will be automatically compiled if dependencies were met19during the generation of the Bitcoin Core build system20and tests weren't explicitly disabled.22The unit tests can be run with `ctest --test-dir build`, which includes unit23tests from subtrees.25Run `build/bin/test_bitcoin --list_content` for the full list of tests.27To run the unit tests manually, launch `build/bin/test_bitcoin`. To recompile28after a test file was modified, run `cmake --build build` and then run the test again. If you29modify a non-test file, use `cmake --build build --target test_bitcoin` to recompile only what's needed30to run the unit tests.32To add more unit tests, add `BOOST_AUTO_TEST_CASE` functions to the existing33.cpp files in the `test/` directory or add new .cpp files that34implement new `BOOST_AUTO_TEST_SUITE` sections.36To run the GUI unit tests manually, launch `build/bin/test_bitcoin-qt`38To add more GUI unit tests, add them to the `src/qt/test/` directory and39the `src/qt/test/test_main.cpp` file.41### Running individual tests43The `test_bitcoin` runner accepts command line arguments from the Boost44framework. To see the list of arguments that may be passed, run:46```47build/bin/test_bitcoin --help48```50For example, to run only the tests in the `getarg_tests` file, with full logging:52```bash53build/bin/test_bitcoin --log_level=all --run_test=getarg_tests54```56or58```bash59build/bin/test_bitcoin -l all -t getarg_tests60```62or to run only the doubledash test in `getarg_tests`64```bash65build/bin/test_bitcoin --run_test=getarg_tests/doubledash66```68The `--log_level=` (or `-l`) argument controls the verbosity of the test output.70The `test_bitcoin` runner also accepts some of the command line arguments accepted by71`bitcoind`. Use `--` to separate these sets of arguments:73```bash74build/bin/test_bitcoin --log_level=all --run_test=getarg_tests -- -printtoconsole=175```77The `-printtoconsole=1` after the two dashes sends debug logging, which78normally goes only to `debug.log` within the data directory, to the79standard terminal output as well.81Running `test_bitcoin` creates a temporary working (data) directory with a randomly82generated pathname within `test_common bitcoin/`, which in turn is within83the system's temporary directory (see84[`temp_directory_path`](https://en.cppreference.com/w/cpp/filesystem/temp_directory_path)).85This data directory looks like a simplified form of the standard `bitcoind` data86directory. Its content will vary depending on the test, but it will always87have a `debug.log` file, for example.89The location of the temporary data directory can be specified with the90`-testdatadir` option. This can make debugging easier. The directory91path used is the argument path appended with92`/test_common bitcoin/<test-name>/datadir`.93The directory path is created if necessary.94Specifying this argument also causes the data directory95not to be removed after the last test. This is useful for looking at96what the test wrote to `debug.log` after it completes, for example.97(The directory is removed at the start of the next test run,98so no leftover state is used.)100```bash101$ build/bin/test_bitcoin --run_test=getarg_tests/doubledash -- -testdatadir=/somewhere/mydatadir102Test directory (will not be deleted): "/somewhere/mydatadir/test_common bitcoin/getarg_tests/doubledash/datadir"103Running 1 test case...105*** No errors detected106$ ls -l '/somewhere/mydatadir/test_common bitcoin/getarg_tests/doubledash/datadir'107total 8108drwxrwxr-x 2 admin admin 4096 Nov 27 22:45 blocks109-rw-rw-r-- 1 admin admin 1003 Nov 27 22:45 debug.log110```112If you run an entire test suite, such as `--run_test=getarg_tests`, or all the test suites113(by not specifying `--run_test`), a separate directory114will be created for each individual test.116### Adding test cases118To add a new unit test file to our test suite, you need119to add the file to either `src/test/CMakeLists.txt` or120`src/wallet/test/CMakeLists.txt` for wallet-related tests. The pattern is to create121one test file for each class or source file for which you want to create122unit tests. The file naming convention is `<source_filename>_tests.cpp`123and such files should wrap their tests in a test suite124called `<source_filename>_tests`. For an example of this pattern,125see `uint256_tests.cpp`.127### Logging and debugging in unit tests129`ctest --test-dir build` will write to the log file `build/Testing/Temporary/LastTest.log`. You can130additionally use the `--output-on-failure` option to display logs of the failed tests automatically131on failure. For running individual tests verbosely, refer to the section132[above](#running-individual-tests).134To write to logs from unit tests you need to use specific message methods135provided by Boost. The simplest is `BOOST_TEST_MESSAGE`.137For debugging you can launch the `test_bitcoin` executable with `gdb` or `lldb` and138start debugging, just like you would with any other program:140```bash141gdb build/bin/test_bitcoin142```144#### Segmentation faults146If you hit a segmentation fault during a test run, you can diagnose where the fault147is happening by running `gdb ./build/bin/test_bitcoin` and then using the `bt` command148within gdb.150Another tool that can be used to resolve segmentation faults is151[valgrind](https://valgrind.org/).153If for whatever reason you want to produce a core dump file for this fault, you can do154that as well. By default, the boost test runner will intercept system errors and not155produce a core file. To bypass this, add `--catch_system_errors=no` to the156`test_bitcoin` arguments and ensure that your ulimits are set properly (e.g. `ulimit -c157unlimited`).159Running the tests and hitting a segmentation fault should now produce a file called `core`160(on Linux platforms, the file name will likely depend on the contents of161`/proc/sys/kernel/core_pattern`).163You can then explore the core dump using164```bash165gdb build/bin/test_bitcoin core167(gdb) bt # produce a backtrace for where a segfault occurred168```
Independent explanations by MyBitcoinExplorer. Not affiliated with or endorsed by Bitcoin Core. Guides are educational and do not replace the source or its tests.
Bitcoin Core source © its contributors, distributed under the MIT license. Original notices and bundled third-party licenses are retained in the source tree.