bitcoin/src/test
Gavin Andresen 0e31ae9818 Merge pull request #2060 from sipa/parallel
Parallel script verification
2013-01-17 16:58:58 -08:00
..
data
Checkpoints_tests.cpp
DoS_tests.cpp Introduce script verification flags 2012-11-15 23:00:16 +01:00
README
accounting_tests.cpp
allocator_tests.cpp
base32_tests.cpp
base58_tests.cpp
base64_tests.cpp
bignum_tests.cpp
bloom_tests.cpp Add nFlags to CBloomFilter to make filter updating optional. 2013-01-16 14:34:06 -05:00
canonical_tests.cpp
compress_tests.cpp
getarg_tests.cpp
key_tests.cpp
miner_tests.cpp changed CreateNewBlock to return a CBlockTemplate object, which includes per-tx fee and sigop count data 2012-12-19 16:12:58 -05:00
mruset_tests.cpp
multisig_tests.cpp Introduce script verification flags 2012-11-15 23:00:16 +01:00
netbase_tests.cpp
pmt_tests.cpp Add CPartialMerkleTree 2013-01-16 14:34:06 -05:00
rpc_tests.cpp Add redeemScript to listunspent output and signrawtransaction input 2012-10-29 13:34:35 -04:00
script_P2SH_tests.cpp Introduce script verification flags 2012-11-15 23:00:16 +01:00
script_tests.cpp Introduce script verification flags 2012-11-15 23:00:16 +01:00
serialize_tests.cpp
sigopcount_tests.cpp
test_bitcoin.cpp Parallelize script verification 2013-01-08 02:00:59 +01:00
transaction_tests.cpp Introduce script verification flags 2012-11-15 23:00:16 +01:00
uint160_tests.cpp
uint256_tests.cpp
util_tests.cpp test/util_tests.cpp: one more DateTimeStrFormat 'T' removal 2013-01-01 19:48:28 -05:00
wallet_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/