Kevacoin source tree
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Luke Dashjr 21d9f36781 Use standard C99 (and Qt) types for 64-bit integers 13 years ago
..
Checkpoints_tests.cpp Moved checkpoints out of main, to prep for using them to help prevent DoS attacks 13 years ago
DoS_tests.cpp Use standard C99 (and Qt) types for 64-bit integers 13 years ago
README Boost unit-testing framework. 13 years ago
base58_tests.cpp Use standard C99 (and Qt) types for 64-bit integers 13 years ago
base64_tests.cpp Rework unit tests so test_bitcoin.cpp does not #include them all 13 years ago
miner_tests.cpp Rework unit tests so test_bitcoin.cpp does not #include them all 13 years ago
multisig_tests.cpp Use block times for 'hard' OP_EVAL switchover, and refactored EvalScript 13 years ago
script_op_eval_tests.cpp Use standard C99 (and Qt) types for 64-bit integers 13 years ago
script_tests.cpp Use block times for 'hard' OP_EVAL switchover, and refactored EvalScript 13 years ago
test_bitcoin.cpp Global fixture to send output to console instead of debug.log 13 years ago
transaction_tests.cpp Rework unit tests so test_bitcoin.cpp does not #include them all 13 years ago
uint160_tests.cpp Use standard C99 (and Qt) types for 64-bit integers 13 years ago
uint256_tests.cpp Use standard C99 (and Qt) types for 64-bit integers 13 years ago
util_tests.cpp Use standard C99 (and Qt) types for 64-bit integers 13 years ago

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/