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.
 
 
 
 
 
 
Wladimir J. van der Laan dba2e9141a Add tests for new uint256 8 years ago
..
data Remove redundant copyright notices from README files 8 years ago
Checkpoints_tests.cpp String conversions uint256 -> uint256S 8 years ago
DoS_tests.cpp
Makefile
README.md
accounting_tests.cpp
alert_tests.cpp
allocator_tests.cpp
arith_uint256_tests.cpp uint256->arith_uint256 blob256->uint256 8 years ago
base32_tests.cpp
base58_tests.cpp
base64_tests.cpp
bctest.py
bignum.h
bip32_tests.cpp
bitcoin-util-test.py
bloom_tests.cpp String conversions uint256 -> uint256S 8 years ago
buildenv.py.in
checkblock_tests.cpp
coins_tests.cpp
compress_tests.cpp
crypto_tests.cpp
getarg_tests.cpp
hash_tests.cpp
key_tests.cpp
main_tests.cpp
miner_tests.cpp
mruset_tests.cpp
multisig_tests.cpp
netbase_tests.cpp
pmt_tests.cpp Use arith_uint256 where necessary 8 years ago
rpc_tests.cpp
rpc_wallet_tests.cpp
script_P2SH_tests.cpp Replace direct use of 0 with SetNull and IsNull 8 years ago
script_tests.cpp
scriptnum_tests.cpp
serialize_tests.cpp
sighash_tests.cpp String conversions uint256 -> uint256S 8 years ago
sigopcount_tests.cpp Replace direct use of 0 with SetNull and IsNull 8 years ago
skiplist_tests.cpp Use arith_uint256 where necessary 8 years ago
test_bitcoin.cpp
timedata_tests.cpp
transaction_tests.cpp String conversions uint256 -> uint256S 8 years ago
uint256_tests.cpp Add tests for new uint256 8 years ago
univalue_tests.cpp
util_tests.cpp
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/.