psy acb75fc76a REGENERATING... 3 years ago
..
data acb75fc76a REGENERATING... 3 years ago
Checkpoints_tests.cpp acb75fc76a REGENERATING... 3 years ago
DoS_tests.cpp acb75fc76a REGENERATING... 3 years ago
README acb75fc76a REGENERATING... 3 years ago
accounting_tests.cpp acb75fc76a REGENERATING... 3 years ago
allocator_tests.cpp acb75fc76a REGENERATING... 3 years ago
base32_tests.cpp acb75fc76a REGENERATING... 3 years ago
base58_tests.cpp acb75fc76a REGENERATING... 3 years ago
base64_tests.cpp acb75fc76a REGENERATING... 3 years ago
bignum_tests.cpp acb75fc76a REGENERATING... 3 years ago
getarg_tests.cpp acb75fc76a REGENERATING... 3 years ago
key_tests.cpp acb75fc76a REGENERATING... 3 years ago
miner_tests.cpp acb75fc76a REGENERATING... 3 years ago
mruset_tests.cpp acb75fc76a REGENERATING... 3 years ago
multisig_tests.cpp acb75fc76a REGENERATING... 3 years ago
netbase_tests.cpp acb75fc76a REGENERATING... 3 years ago
rpc_tests.cpp acb75fc76a REGENERATING... 3 years ago
script_P2SH_tests.cpp acb75fc76a REGENERATING... 3 years ago
script_tests.cpp acb75fc76a REGENERATING... 3 years ago
sigopcount_tests.cpp acb75fc76a REGENERATING... 3 years ago
test_ecoin.cpp acb75fc76a REGENERATING... 3 years ago
transaction_tests.cpp acb75fc76a REGENERATING... 3 years ago
uint160_tests.cpp acb75fc76a REGENERATING... 3 years ago
uint256_tests.cpp acb75fc76a REGENERATING... 3 years ago
util_tests.cpp acb75fc76a REGENERATING... 3 years ago
wallet_tests.cpp acb75fc76a REGENERATING... 3 years ago

README

The sources in this directory are unit test cases. Boost includes a
unit testing framework, and since ecoin 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_ecoin"
that runs all of the unit tests. The main source file is called
test_ecoin.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 "_tests.cpp" and such files should wrap
their tests in a test suite called "_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/