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.
 
 
 
 
 
 
Gavin Andresen 142e604184 DoS fix for mapOrphanTransactions 11 years ago
..
Checkpoints_tests.cpp
DoS_tests.cpp DoS fix for mapOrphanTransactions 11 years ago
README
base58_tests.cpp
base64_tests.cpp
getarg_tests.cpp
key_tests.cpp
miner_tests.cpp
mruset_tests.cpp Add mruset and use it for setInventoryKnown 11 years ago
multisig_tests.cpp Fix tests after 38067c18 11 years ago
rpc_tests.cpp
script_P2SH_tests.cpp Fix tests after 38067c18 11 years ago
script_tests.cpp Fix tests after 38067c18 11 years ago
sigopcount_tests.cpp Fix tests after 38067c18 11 years ago
test_bitcoin.cpp
transaction_tests.cpp Fix tests after 38067c18 11 years ago
uint160_tests.cpp
uint256_tests.cpp
util_tests.cpp

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/