af6edac*: alias -h for --help (Daniel Cousens)131d7f9Change URLs to https in debian/control (Matt Corallo)7ce2c91Update debian/changelog and slight tweak to debian/control (Matt Corallo)4fbfebeCorrect spelling mistakes in doc folder (Mitchell Cash)e42bf16Clarification of unit test build instructions. (Eric Lombrozo)54f9deeUpdate bluematt-key, the old one is long-since revoked (Matt Corallo)bfc6154[Trivial] Fixed typo when referring to a previous section in depends/README.md [skip ci] (Chris Kleeschulte)9e45157build: disable -Wself-assign (Wladimir J. van der Laan)33d6825Bugfix: Allow mining on top of old tip blocks for testnet (fixes testnet-in-a-box use case) (Luke Dashjr)87a797abuild: Remove dependency of bitcoin-cli on secp256k1 (Wladimir J. van der Laan)a33cd5b[trivial] Fix rpc message "help generate" (MarcoFalke)6fd0019Drop "with minimal dependencies" from description (Zak Wilcox)2394f4dSplit bitcoin-tx into its own package (Zak Wilcox)1e672aeInclude bitcoin-tx binary on Debian/Ubuntu (Zak Wilcox)b3eaa30[Qt] Raise debug window when requested (MarcoFalke)01878c9Fix locking in GetTransaction. (Alex Morcos)9b9acc2Fix spelling of Qt (Diego Viola)
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.
Add the source files to /src/Makefile.test.include to add them to the build.
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/.