bitcoin/src/test
Pieter Wuille 6865127551 Merge pull request #3015 from theuni/win32-version-info
Win32 version info
2013-09-29 06:49:23 -07:00
..
data included-tests: generate binary data from test files for inclusion into test binaries 2013-09-16 12:53:11 -04:00
Checkpoints_tests.cpp
DoS_tests.cpp
Makefile.am autotools: fix the Makefile.include to be safely included anywhere. 2013-09-18 17:12:39 -04:00
README
accounting_tests.cpp
alert_tests.cpp included-tests: generate binary data from test files for inclusion into test binaries 2013-09-16 12:53:11 -04:00
allocator_tests.cpp
base32_tests.cpp
base58_tests.cpp included-tests: generate binary data from test files for inclusion into test binaries 2013-09-16 12:53:11 -04:00
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 2013-09-16 12:53:11 -04:00
checkblock_tests.cpp Bugfix: Since test_bitcoin is being built and run inside src/test/, try using relative directories from that point 2013-09-10 23:04:56 +00:00
compress_tests.cpp
getarg_tests.cpp
hash_tests.cpp
hmac_tests.cpp
key_tests.cpp
miner_tests.cpp Fix minor unit test memory leaks 2013-09-19 00:01:46 +02:00
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 2013-09-16 12:53:11 -04:00
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 2013-09-16 12:53:11 -04:00
uint160_tests.cpp
uint256_tests.cpp
util_tests.cpp
wallet_tests.cpp Fix minor unit test memory leaks 2013-09-19 00:01:46 +02:00

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/