psy
acb75fc76a
REGENERATING...
|
3 年之前 | |
|---|---|---|
| .. | ||
| data | 3 年之前 | |
| Checkpoints_tests.cpp | 3 年之前 | |
| DoS_tests.cpp | 3 年之前 | |
| README | 3 年之前 | |
| accounting_tests.cpp | 3 年之前 | |
| allocator_tests.cpp | 3 年之前 | |
| base32_tests.cpp | 3 年之前 | |
| base58_tests.cpp | 3 年之前 | |
| base64_tests.cpp | 3 年之前 | |
| bignum_tests.cpp | 3 年之前 | |
| getarg_tests.cpp | 3 年之前 | |
| key_tests.cpp | 3 年之前 | |
| miner_tests.cpp | 3 年之前 | |
| mruset_tests.cpp | 3 年之前 | |
| multisig_tests.cpp | 3 年之前 | |
| netbase_tests.cpp | 3 年之前 | |
| rpc_tests.cpp | 3 年之前 | |
| script_P2SH_tests.cpp | 3 年之前 | |
| script_tests.cpp | 3 年之前 | |
| sigopcount_tests.cpp | 3 年之前 | |
| test_ecoin.cpp | 3 年之前 | |
| transaction_tests.cpp | 3 年之前 | |
| uint160_tests.cpp | 3 年之前 | |
| uint256_tests.cpp | 3 年之前 | |
| util_tests.cpp | 3 年之前 | |
| wallet_tests.cpp | 3 年之前 | |
README
The sources in this directory are unit test cases. Boost includes a
unit testing framework, and since ecoin 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_ecoin"
that runs all of the unit tests. The main source file is called
test_ecoin.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 "_tests.cpp" and such files should wrap
their tests in a test suite called "_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/
unit testing framework, and since ecoin 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_ecoin"
that runs all of the unit tests. The main source file is called
test_ecoin.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 "_tests.cpp" and such files should wrap
their tests in a test suite called "_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/