lbrycrd/src/test
Kangmo 0205abd83d Improve unit test code not to compare with explanatory messages for each platform.
Instead, use have an exception object to check if the string returned by what() on the raised exception matches the string returned by what() on the expected exception instance.
This way, we do not need to list all different possible explanatory strings for different platforms in the test code, and make it simple. (The idea is by Cory Fields.)
2013-12-16 09:26:04 +09:00
..
data Add tests for correct and incorrect order of signatures for a multisig 2013-12-11 00:03:50 +01:00
accounting_tests.cpp Cleanup code using forward declarations. 2013-11-10 09:36:28 -06:00
alert_tests.cpp Test alerts high at high PROTOCOL_VERSIONs 2013-11-11 10:31:08 +10:00
allocator_tests.cpp Cleanup code using forward declarations. 2013-11-10 09:36:28 -06:00
base32_tests.cpp Cleanup code using forward declarations. 2013-11-10 09:36:28 -06:00
base58_tests.cpp Cleanup code using forward declarations. 2013-11-10 09:36:28 -06:00
base64_tests.cpp Cleanup code using forward declarations. 2013-11-10 09:36:28 -06:00
bignum_tests.cpp Cleanup code using forward declarations. 2013-11-10 09:36:28 -06:00
bip32_tests.cpp Cleanup code using forward declarations. 2013-11-10 09:36:28 -06:00
bloom_tests.cpp Cleanup code using forward declarations. 2013-11-10 09:36:28 -06:00
canonical_tests.cpp Cleanup code using forward declarations. 2013-11-10 09:36:28 -06:00
checkblock_tests.cpp Cleanup code using forward declarations. 2013-11-10 09:36:28 -06:00
Checkpoints_tests.cpp Cleanup code using forward declarations. 2013-11-10 09:36:28 -06:00
compress_tests.cpp Cleanup code using forward declarations. 2013-11-10 09:36:28 -06:00
DoS_tests.cpp Add main-specific node state 2013-12-08 14:51:37 +01:00
getarg_tests.cpp Cleanup code using forward declarations. 2013-11-10 09:36:28 -06:00
hash_tests.cpp Cleanup code using forward declarations. 2013-11-10 09:36:28 -06:00
hmac_tests.cpp Cleanup code using forward declarations. 2013-11-10 09:36:28 -06:00
key_tests.cpp Cleanup code using forward declarations. 2013-11-10 09:36:28 -06:00
Makefile.am Re-enable miner tests in --disable-wallet mode 2013-12-09 09:25:10 +01:00
miner_tests.cpp Re-enable miner tests in --disable-wallet mode 2013-12-09 09:25:10 +01:00
mruset_tests.cpp Cleanup code using forward declarations. 2013-11-10 09:36:28 -06:00
multisig_tests.cpp Cleanup code using forward declarations. 2013-11-10 09:36:28 -06:00
netbase_tests.cpp Cleanup code using forward declarations. 2013-11-10 09:36:28 -06:00
pmt_tests.cpp Cleanup code using forward declarations. 2013-11-10 09:36:28 -06:00
README Boost unit-testing framework. 2011-06-27 14:12:48 -04:00
rpc_tests.cpp Split off rpc_wallet_tests 2013-12-04 12:46:14 +01:00
rpc_wallet_tests.cpp Split off rpc_wallet_tests 2013-12-04 12:46:14 +01:00
script_P2SH_tests.cpp Cleanup code using forward declarations. 2013-11-10 09:36:28 -06:00
script_tests.cpp Cleanup code using forward declarations. 2013-11-10 09:36:28 -06:00
serialize_tests.cpp Improve unit test code not to compare with explanatory messages for each platform. 2013-12-16 09:26:04 +09:00
sighash_tests.cpp Inline signature serializer 2013-09-28 18:37:00 +02:00
sigopcount_tests.cpp Cleanup code using forward declarations. 2013-11-10 09:36:28 -06:00
test_bitcoin.cpp Add main-specific node state 2013-12-08 14:51:37 +01:00
transaction_tests.cpp Cleanup code using forward declarations. 2013-11-10 09:36:28 -06:00
uint160_tests.cpp Cleanup code using forward declarations. 2013-11-10 09:36:28 -06:00
uint256_tests.cpp Cleanup code using forward declarations. 2013-11-10 09:36:28 -06:00
util_tests.cpp tests: add testcases for strprintf 2013-11-13 17:02:27 +01:00
wallet_tests.cpp Cleanup code using forward declarations. 2013-11-10 09:36:28 -06: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/