lbrycrd/src/test
Jeff Garzik af93273799 Merge pull request #2657 from gmaxwell/its_after_may15_forever
It's after 2013-05-15 forever now, so remove the code for the May 15 fork
2013-05-30 07:35:44 -07:00
..
data Add a few data-driven tests for SIGHASH_ANYONECANPAY 2013-05-21 18:16:43 +02:00
accounting_tests.cpp Bugfix: Initialize CWallet::nOrderPosNext on an empty wallet, and save it in db 2012-09-08 04:55:36 +00:00
alert_tests.cpp -alertnotify=<cmd> 2013-03-19 15:16:30 -04:00
allocator_tests.cpp Handle locked pages more robustly (Fixes issue #1462) 2012-08-23 06:55:35 +02:00
base32_tests.cpp Node support for Tor hidden services 2012-06-23 01:11:32 +02:00
base58_tests.cpp data-driven base58 CBitcoinAddress/CBitcoinSecret tests 2012-10-01 04:57:26 +02:00
base64_tests.cpp Clean up warnings 2012-05-09 03:48:30 +02:00
bignum_tests.cpp Fix signed/unsigned comparison warnings 2013-04-03 14:04:21 -04:00
bloom_tests.cpp Add nFlags to CBloomFilter to make filter updating optional. 2013-01-16 14:34:06 -05:00
canonical_tests.cpp Check for canonical public keys and signatures 2012-09-21 01:24:25 +02:00
checkblock_tests.cpp It's after 2013-05-15 forever now, so remove the code for the May 15 fork. 2013-05-16 13:34:01 -07:00
Checkpoints_tests.cpp Checkpoint at block 185333 (and remove a couple of intermediate checkpoints) 2012-06-25 09:26:14 -04:00
compress_tests.cpp Compact serialization for amounts 2012-10-20 23:08:56 +02:00
DoS_tests.cpp Introduce script verification flags 2012-11-15 23:00:16 +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 Refactor: split CKeyID/CScriptID/CTxDestination from CBitcoinAddress 2012-05-24 20:26:19 +02:00
miner_tests.cpp CValidationState framework 2013-01-30 03:56:44 +01:00
mruset_tests.cpp Fix a couple more typos 2012-06-30 17:05:28 +08:00
multisig_tests.cpp Fix signed/unsigned comparison warnings 2013-04-03 14:04:21 -04:00
netbase_tests.cpp Node support for Tor hidden services 2012-06-23 01:11:32 +02:00
pmt_tests.cpp Add CPartialMerkleTree 2013-01-16 14:34:06 -05:00
README Boost unit-testing framework. 2011-06-27 14:12:48 -04:00
rpc_tests.cpp Add redeemScript to listunspent output and signrawtransaction input 2012-10-29 13:34:35 -04:00
script_P2SH_tests.cpp Define dust transaction outputs, and make them non-standard 2013-05-03 10:52:09 -04:00
script_tests.cpp Introduce script verification flags 2012-11-15 23:00:16 +01:00
serialize_tests.cpp Fix signed/unsigned comparison warnings 2013-04-03 14:04:21 -04:00
sigopcount_tests.cpp Fix signed/unsigned comparison warnings 2013-04-03 14:04:21 -04:00
test_bitcoin.cpp Port Thread* methods to boost::thread_group 2013-04-03 19:57:13 -04:00
transaction_tests.cpp Define dust transaction outputs, and make them non-standard 2013-05-03 10:52:09 -04: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 Remove flaky util thread unit tests 2013-05-03 10:45:00 -04:00
wallet_tests.cpp Define dust transaction outputs, and make them non-standard 2013-05-03 10:52:09 -04: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/