twister-core/src/test
2012-05-25 11:37:34 -04:00
..
data Unit tests for transaction size limits 2012-05-25 11:37:34 -04:00
base58_tests.cpp Clean up warnings 2012-05-09 03:48:30 +02:00
base64_tests.cpp Clean up warnings 2012-05-09 03:48:30 +02:00
Checkpoints_tests.cpp
DoS_tests.cpp DoS_tests: fix signed/unsigned comparison warnings 2012-05-24 12:18:50 -04:00
getarg_tests.cpp
key_tests.cpp
miner_tests.cpp Fix tests after recent refactors 2012-04-17 20:37:47 +02:00
mruset_tests.cpp
multisig_tests.cpp
README
rpc_tests.cpp Expose CRPCTable via bitcoinrpc.h for testing 2012-04-21 01:37:34 +02:00
script_P2SH_tests.cpp
script_tests.cpp Lots more Script unit test cases. 2012-05-24 17:32:09 -04:00
sigopcount_tests.cpp
test_bitcoin.cpp Make testcases build, prevent windows symbol collision 2012-05-20 10:44:50 +02:00
transaction_tests.cpp Fix tests after recent refactors 2012-04-17 20:37:47 +02:00
uint160_tests.cpp
uint256_tests.cpp
util_tests.cpp change strings to Bitcoin (uppercase), where it is used as a noun and update strings to use "Qt" (and not qt or QT) / update initialisation of notificator to use qApp->applicationName() instead of a static string 2012-05-18 23:13:58 +02: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/