lbrycrd/src/test
Gavin Andresen feaec80cb0 Test alerts high at high PROTOCOL_VERSIONs
I regenerated the alert test data; now alerts are tested
against a protocol version way above the current protocol
version.

So we won't have to regenerate them every time we bump
PROTOCOL_VERSION in the future.
2013-11-11 10:31:08 +10:00
..
data Test alerts high at high PROTOCOL_VERSIONs 2013-11-11 10:31:08 +10: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 Cleanup code using forward declarations. 2013-11-10 09:36:28 -06: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 Merge pull request #2645 from sipa/inlinesighash 2013-10-16 17:53:31 -07:00
miner_tests.cpp Cleanup code using forward declarations. 2013-11-10 09:36:28 -06: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 Cleanup code using forward declarations. 2013-11-10 09:36:28 -06: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 Cleanup code using forward declarations. 2013-11-10 09:36:28 -06: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 Cleanup code using forward declarations. 2013-11-10 09:36:28 -06: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 Cleanup code using forward declarations. 2013-11-10 09:36:28 -06: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/