b867e40CreateNewBlock: Stick height in coinbase so we pass template sanity check (Luke Dashjr)60755dbsubmitblock: Check for duplicate submissions explicitly (Luke Dashjr)bc6cb41QA RPC tests: Add tests block block proposals (Luke Dashjr)9765a50Implement BIP 23 Block Proposal (Luke Dashjr)3dcbb9bAbstract DecodeHexBlk and BIP22ValidationResult functions out of submitblock (Luke Dashjr)132ea9bminer_tests: Disable checkpoints so they don't fail the subsidy-change test (Luke Dashjr)df08a62TestBlockValidity function for CBlock proposals (used by CreateNewBlock) (Luke Dashjr)4ea1be7CreateNewBlock and miner_tests: Also check generated template is valid by CheckBlockHeader, ContextualCheckBlockHeader, CheckBlock, and ContextualCheckBlock (Luke Dashjr)a48f2d6Abstract context-dependent block checking from acceptance (Luke Dashjr)
Notes
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/.