d528025Revert "rpc-tests: re-enable rpc-tests for Windows" (Wladimir J. van der Laan)1e700c9doc: update deps in build-unix.md after libevent (Wladimir J. van der Laan)26c9b83Move windows socket init to utility function (Wladimir J. van der Laan)4be0b08libevent: Windows reuseaddr workaround in depends (Cory Fields)3a174cdFix race condition between starting HTTP server thread and setting EventBase() (Wladimir J. van der Laan)6d2bc22Document options for new HTTP/RPC server in --help (Wladimir J. van der Laan)be33f3fImplement RPCTimerHandler for Qt RPC console (Wladimir J. van der Laan)57d85d9doc: mention SSL support dropped for RPC in release notes (Wladimir J. van der Laan)40b556devhttpd implementation (Wladimir J. van der Laan)ee2a42btests: GET requests cannot have request body, use POST in rest.py (Wladimir J. van der Laan)6e996d3tests: fix qt payment test (Cory Fields)3140ef9build: build-system changes for libevent (Wladimir J. van der Laan)a9af234libevent: add depends (Cory Fields)6a21dd5Remove rpc_boostasiotocnetaddr test (Wladimir J. van der Laan)8f9301cqa: Remove -rpckeepalive tests from httpbasics (Wladimir J. van der Laan)51fcfc0doc: remove documentation for rpcssl (Wladimir J. van der Laan)
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/.
test_bitcoin has some built-in command-line arguments; for example, to run just the getarg_tests verbosely:
test_bitcoin --log_level=all --run_test=getarg_tests
... or to run just the doubledash test:
test_bitcoin --run_test=getarg_tests/doubledash
Run test_bitcoin --help for the full list.