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 d752ba86c1 Add SCRIPT_VERIFY_SIGPUSHONLY (BIP62 rule 2) 8 years ago
..
data Add SCRIPT_VERIFY_SIGPUSHONLY (BIP62 rule 2) 8 years ago
Checkpoints_tests.cpp
DoS_tests.cpp Remove CheckMinWork, as we always know all parent headers 8 years ago
Makefile
README.md
accounting_tests.cpp
alert_tests.cpp
allocator_tests.cpp
base32_tests.cpp
base58_tests.cpp script: add a slew of includes all around and drop includes from script.h 8 years ago
base64_tests.cpp
bctest.py
bignum.h
bip32_tests.cpp
bitcoin-util-test.py
bloom_tests.cpp Fixes for missing boost tuple.hpp header include. 8 years ago
buildenv.py.in
checkblock_tests.cpp CAutoFile: Explicit Get() and remove unused methods 8 years ago
coins_tests.cpp
compress_tests.cpp
crypto_tests.cpp
getarg_tests.cpp
hash_tests.cpp
key_tests.cpp Typo in test 8 years ago
main_tests.cpp
miner_tests.cpp script: move CScriptID to standard.h and add a ctor for creating them from CScripts 8 years ago
mruset_tests.cpp
multisig_tests.cpp script: add ToByteVector() for converting anything with begin/end 8 years ago
netbase_tests.cpp
pmt_tests.cpp
rpc_tests.cpp
rpc_wallet_tests.cpp
script_P2SH_tests.cpp script: add ToByteVector() for converting anything with begin/end 8 years ago
script_tests.cpp Add SCRIPT_VERIFY_SIGPUSHONLY (BIP62 rule 2) 8 years ago
scriptnum_tests.cpp
serialize_tests.cpp
sighash_tests.cpp
sigopcount_tests.cpp script: add ToByteVector() for converting anything with begin/end 8 years ago
skiplist_tests.cpp
test_bitcoin.cpp Rename CWalletInterface to CValidationInterface 8 years ago
timedata_tests.cpp
transaction_tests.cpp Add SCRIPT_VERIFY_SIGPUSHONLY (BIP62 rule 2) 8 years ago
uint256_tests.cpp
univalue_tests.cpp
util_tests.cpp boost: drop boost dependency in version.cpp. 8 years ago
wallet_tests.cpp

README.md

Notes

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/.