lbrycrd/src/test
2012-02-27 21:04:32 +01:00
..
base58_tests.cpp Revert "Use standard C99 (and Qt) types for 64-bit integers" 2011-12-21 22:33:19 +01:00
base64_tests.cpp Rework unit tests so test_bitcoin.cpp does not #include them all 2011-12-19 12:39:47 -05:00
Checkpoints_tests.cpp Moved checkpoints out of main, to prep for using them to help prevent DoS attacks 2011-12-01 12:18:50 -05:00
DoS_tests.cpp Network stack refactor 2012-01-06 18:55:37 +01:00
getarg_tests.cpp New GetArg features: allow --, and booleans can be -foo or -nofoo 2012-02-07 09:14:31 -05:00
key_tests.cpp Unit tests for EC key routines 2012-01-09 15:18:19 +01:00
miner_tests.cpp Rework unit tests so test_bitcoin.cpp does not #include them all 2011-12-19 12:39:47 -05:00
mruset_tests.cpp Add mruset and use it for setInventoryKnown 2012-02-27 21:04:32 +01:00
multisig_tests.cpp Fix tests after 38067c18 2012-02-20 18:32:33 +01:00
README Boost unit-testing framework. 2011-06-27 14:12:48 -04:00
rpc_tests.cpp Replace OP_EVAL (BIP 12) with Pay-to-script-hash (BIP 16). 2012-01-13 10:22:23 -05:00
script_P2SH_tests.cpp Fix tests after 38067c18 2012-02-20 18:32:33 +01:00
script_tests.cpp Fix tests after 38067c18 2012-02-20 18:32:33 +01:00
sigopcount_tests.cpp Fix tests after 38067c18 2012-02-20 18:32:33 +01:00
test_bitcoin.cpp Replace OP_EVAL (BIP 12) with Pay-to-script-hash (BIP 16). 2012-01-13 10:22:23 -05:00
transaction_tests.cpp Fix tests after 38067c18 2012-02-20 18:32:33 +01:00
uint160_tests.cpp Revert "Use standard C99 (and Qt) types for 64-bit integers" 2011-12-21 22:33:19 +01:00
uint256_tests.cpp Revert "Use standard C99 (and Qt) types for 64-bit integers" 2011-12-21 22:33:19 +01:00
util_tests.cpp Replace OP_EVAL (BIP 12) with Pay-to-script-hash (BIP 16). 2012-01-13 10:22:23 -05:00

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/