Index of /pub/mirrors/btcbase.org/patches/genesis/hunk/bitcoin/src/test

 Name                    Last modified      Size  Description
 Parent Directory                             -   
 Checkpoints_tests.cp..> 2020-10-16 14:04  7.4K  
 DoS_tests.cpp.html      2020-10-16 14:04   19K  
 base58_tests.cpp.html   2020-10-16 14:05   14K  
 base64_tests.cpp.html   2020-10-16 14:03  5.3K  
 miner_tests.cpp.html    2020-10-16 14:04  7.0K  
 script_tests.cpp.html   2020-10-16 14:04   27K  
 test_bitcoin.cpp.html   2020-10-16 14:04  5.5K  
 transaction_tests.cp..> 2020-10-16 14:03  7.6K  
 uint160_tests.cpp.html  2020-10-16 14:04  4.9K  
 uint256_tests.cpp.html  2020-10-16 14:05  4.9K  
 util_tests.cpp.html     2020-10-16 14:05   35K  

-
+ 8DC10490739FE1FFF46B553121622B8AC1F7B6B90210A56900DDE6B85F44FED7287DCC2F773A8D64ADED5C1B242F587132D3BC1E37CE21C5FFF315AF913B8FC1
bitcoin/src/test/README

(0 . 0)(1 . 21)
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/