kevacoin

Kevacoin source tree

Gavin Andresen f04017f702 More CScript unit tests.		13 years ago
..
data	More CScript unit tests.	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	DoS_tests: fix signed/unsigned comparison warnings	13 years ago
README	Boost unit-testing framework.	13 years ago
base58_tests.cpp	Clean up warnings	13 years ago
base64_tests.cpp	Clean up warnings	13 years ago
getarg_tests.cpp	New GetArg features: allow --, and booleans can be -foo or -nofoo	13 years ago
key_tests.cpp	CBitcoinSecret::SetString() now calls IsValid() to make sure it was passed something with the correct version.	13 years ago
miner_tests.cpp	Fix tests after recent refactors	13 years ago
mruset_tests.cpp	Add mruset and use it for setInventoryKnown	13 years ago
multisig_tests.cpp	Fix tests after `38067c18`	13 years ago
rpc_tests.cpp	Expose CRPCTable via bitcoinrpc.h for testing	13 years ago
script_P2SH_tests.cpp	Fix tests after `38067c18`	13 years ago
script_tests.cpp	More CScript unit tests.	13 years ago
sigopcount_tests.cpp	Fix tests after `38067c18`	13 years ago
test_bitcoin.cpp	Make testcases build, prevent windows symbol collision	13 years ago
transaction_tests.cpp	Fix tests after recent refactors	13 years ago
uint160_tests.cpp	Revert "Use standard C99 (and Qt) types for 64-bit integers"	13 years ago
uint256_tests.cpp	Revert "Use standard C99 (and Qt) types for 64-bit integers"	13 years ago
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	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/