FLO-wallet-core/src/test
Gavin Andresen 8556b0298d Merge pull request #3842 from ditto-b/master
Fix for GetBlockValue() after block 13,440,000
2014-04-02 21:31:17 -04:00
..
data Add sighash tests from data file 2014-03-31 11:19:19 -03:00
accounting_tests.cpp
alert_tests.cpp
allocator_tests.cpp
base32_tests.cpp
base58_tests.cpp
base64_tests.cpp
bignum_tests.cpp
bip32_tests.cpp
bloom_tests.cpp
canonical_tests.cpp
checkblock_tests.cpp
Checkpoints_tests.cpp
compress_tests.cpp
DoS_tests.cpp
getarg_tests.cpp
hash_tests.cpp
hmac_tests.cpp
key_tests.cpp
main_tests.cpp Merge pull request #3842 from ditto-b/master 2014-04-02 21:31:17 -04:00
Makefile.am Add sighash tests from data file 2014-03-31 11:19:19 -03:00
miner_tests.cpp
mruset_tests.cpp
multisig_tests.cpp
netbase_tests.cpp
pmt_tests.cpp
README
rpc_tests.cpp
rpc_wallet_tests.cpp
script_P2SH_tests.cpp
script_tests.cpp
serialize_tests.cpp
sighash_tests.cpp add checks for deserialization errors 2014-03-31 15:07:46 -03:00
sigopcount_tests.cpp
test_bitcoin.cpp
transaction_tests.cpp
uint256_tests.cpp
util_tests.cpp
wallet_tests.cpp

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/