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.
 
 
 
 
 
 
Pieter Wuille 1657ed2ab4 Fix minor unit test memory leaks 9 years ago
..
data included-tests: generate binary data from test files for inclusion into test binaries 9 years ago
Checkpoints_tests.cpp
DoS_tests.cpp
Makefile.am included-tests: generate binary data from test files for inclusion into test binaries 9 years ago
README
accounting_tests.cpp
alert_tests.cpp included-tests: generate binary data from test files for inclusion into test binaries 9 years ago
allocator_tests.cpp
base32_tests.cpp
base58_tests.cpp included-tests: generate binary data from test files for inclusion into test binaries 9 years ago
base64_tests.cpp
bignum_tests.cpp
bip32_tests.cpp
bloom_tests.cpp
canonical_tests.cpp included-tests: generate binary data from test files for inclusion into test binaries 9 years ago
checkblock_tests.cpp Bugfix: Since test_bitcoin is being built and run inside src/test/, try using relative directories from that point 9 years ago
compress_tests.cpp
getarg_tests.cpp
hash_tests.cpp Add MurmurHash3() unit test 9 years ago
hmac_tests.cpp
key_tests.cpp
miner_tests.cpp Fix minor unit test memory leaks 9 years ago
mruset_tests.cpp
multisig_tests.cpp
netbase_tests.cpp
pmt_tests.cpp
rpc_tests.cpp
script_P2SH_tests.cpp
script_tests.cpp included-tests: generate binary data from test files for inclusion into test binaries 9 years ago
serialize_tests.cpp
sigopcount_tests.cpp
test_bitcoin.cpp
transaction_tests.cpp included-tests: generate binary data from test files for inclusion into test binaries 9 years ago
uint160_tests.cpp
uint256_tests.cpp
util_tests.cpp Make RPC password resistant to timing attacks 9 years ago
wallet_tests.cpp Fix minor unit test memory leaks 9 years ago

README

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, which simply includes other files that contain the
actual unit tests (outside of a couple required preprocessor
directives). 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
examples of this pattern, examine uint160_tests.cpp and
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/