You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Marko Bencun bb81e17355 scripted-diff: stop using the gArgs wrappers 5 years ago
..
data
DoS_tests.cpp scripted-diff: stop using the gArgs wrappers 5 years ago
Makefile
README.md
addrman_tests.cpp Merge #10483: scripted-diff: Use the C++11 keyword nullptr to denote the pointer literal instead of the macro NULL 5 years ago
allocator_tests.cpp
amount_tests.cpp
arith_uint256_tests.cpp
base32_tests.cpp
base58_tests.cpp
base64_tests.cpp
bip32_tests.cpp
blockencodings_tests.cpp
bloom_tests.cpp
bswap_tests.cpp
checkqueue_tests.cpp
coins_tests.cpp
compress_tests.cpp
crypto_tests.cpp
cuckoocache_tests.cpp
dbwrapper_tests.cpp
getarg_tests.cpp scripted-diff: stop using the gArgs wrappers 5 years ago
hash_tests.cpp
key_tests.cpp
limitedmap_tests.cpp
main_tests.cpp
mempool_tests.cpp
merkle_tests.cpp
miner_tests.cpp scripted-diff: Use the C++11 keyword nullptr to denote the pointer literal instead of the macro NULL 5 years ago
multisig_tests.cpp scripted-diff: Use the C++11 keyword nullptr to denote the pointer literal instead of the macro NULL 5 years ago
net_tests.cpp scripted-diff: stop using the gArgs wrappers 5 years ago
netbase_tests.cpp
pmt_tests.cpp
policyestimator_tests.cpp
pow_tests.cpp scripted-diff: Use the C++11 keyword nullptr to denote the pointer literal instead of the macro NULL 5 years ago
prevector_tests.cpp
raii_event_tests.cpp scripted-diff: Use the C++11 keyword nullptr to denote the pointer literal instead of the macro NULL 5 years ago
random_tests.cpp
reverselock_tests.cpp
rpc_tests.cpp rpc: Move ValueFromAmount to core_write 5 years ago
sanity_tests.cpp
scheduler_tests.cpp
script_P2SH_tests.cpp scripted-diff: Use the C++11 keyword nullptr to denote the pointer literal instead of the macro NULL 5 years ago
script_tests.cpp scripted-diff: Use the C++11 keyword nullptr to denote the pointer literal instead of the macro NULL 5 years ago
scriptnum10.h
scriptnum_tests.cpp
serialize_tests.cpp
sighash_tests.cpp
sigopcount_tests.cpp
skiplist_tests.cpp scripted-diff: Use the C++11 keyword nullptr to denote the pointer literal instead of the macro NULL 5 years ago
streams_tests.cpp
test_bitcoin.cpp scripted-diff: stop using the gArgs wrappers 5 years ago
test_bitcoin.h
test_bitcoin_fuzzy.cpp
test_bitcoin_main.cpp
testutil.cpp
testutil.h
timedata_tests.cpp
torcontrol_tests.cpp
transaction_tests.cpp
txvalidationcache_tests.cpp scripted-diff: Use the C++11 keyword nullptr to denote the pointer literal instead of the macro NULL 5 years ago
uint256_tests.cpp
univalue_tests.cpp
util_tests.cpp scripted-diff: Use the C++11 keyword nullptr to denote the pointer literal instead of the macro NULL 5 years ago
versionbits_tests.cpp scripted-diff: Use the C++11 keyword nullptr to denote the pointer literal instead of the macro NULL 5 years ago

README.md

Compiling/running unit tests

Unit tests will be automatically compiled if dependencies were met in ./configure and tests weren't explicitly disabled.

After configuring, they can be run with make check.

To run the bitcoind tests manually, launch src/test/test_bitcoin.

To add more bitcoind tests, add BOOST_AUTO_TEST_CASE functions to the existing .cpp files in the test/ directory or add new .cpp files that implement new BOOST_AUTO_TEST_SUITE sections.

To run the bitcoin-qt tests manually, launch src/qt/test/test_bitcoin-qt

To add more bitcoin-qt tests, add them to the src/qt/test/ directory and the src/qt/test/test_main.cpp file.

Running individual tests

test_bitcoin has some built-in command-line arguments; for example, to run just the getarg_tests verbosely:

test_bitcoin --log_level=all --run_test=getarg_tests

... or to run just the doubledash test:

test_bitcoin --run_test=getarg_tests/doubledash

Run test_bitcoin --help for the full list.

Note on adding test cases

The sources in this directory are unit test cases. Boost includes a unit testing framework, and since bitcoin already uses boost, it makes sense to simply use this framework rather than require developers to configure some other framework (we want as few impediments to creating unit tests as possible).

The build system is setup to compile an executable called test_bitcoin that runs all of the unit tests. The main source file is called test_bitcoin.cpp. To add a new unit test file to our test suite you need to add the file to src/Makefile.test.include. The pattern is to create one test file for each class or source file for which you want to create unit tests. The file naming convention is <source_filename>_tests.cpp and such files should wrap their tests in a test suite called <source_filename>_tests. For an example of this pattern, examine uint256_tests.cpp.

For further reading, I found the following website to be helpful in explaining how the boost unit test framework works: http://www.alittlemadness.com/2009/03/31/c-unit-testing-with-boosttest/.