You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
SHI 5d86a68c53 main - > Starwels MAI 2 years ago
..
data Starwels Ai - > Start 2 years ago
DoS_tests.cpp Rename all 2 years ago
Makefile Rename all 2 years ago
README.md Rename all 2 years ago
addrman_tests.cpp main - > Starwels MAI 2 years ago
allocator_tests.cpp Rename all 2 years ago
amount_tests.cpp Rename all 2 years ago
arith_uint256_tests.cpp Rename all 2 years ago
base32_tests.cpp Rename all 2 years ago
base58_tests.cpp Starwels Ai - > Start 2 years ago
base64_tests.cpp Rename all 2 years ago
bip32_tests.cpp Rename all 2 years ago
blockencodings_tests.cpp Rename all 2 years ago
bloom_tests.cpp Rename all 2 years ago
bswap_tests.cpp Rename all 2 years ago
checkqueue_tests.cpp Rename all 2 years ago
coins_tests.cpp Rename all 2 years ago
compress_tests.cpp Rename all 2 years ago
crypto_tests.cpp Rename all 2 years ago
cuckoocache_tests.cpp Rename all 2 years ago
dbwrapper_tests.cpp Rename all 2 years ago
getarg_tests.cpp Rename all 2 years ago
hash_tests.cpp Rename all 2 years ago
key_tests.cpp Rename all 2 years ago
limitedmap_tests.cpp Rename all 2 years ago
main_tests.cpp Rename all 2 years ago
mempool_tests.cpp Rename all 2 years ago
merkle_tests.cpp Rename all 2 years ago
miner_tests.cpp Starwels start 2 years ago
multisig_tests.cpp Rename all 2 years ago
net_tests.cpp main - > Starwels MAI 2 years ago
netbase_tests.cpp main - > Starwels MAI 2 years ago
pmt_tests.cpp Rename all 2 years ago
policyestimator_tests.cpp Rename all 2 years ago
pow_tests.cpp Starwels start 2 years ago
prevector_tests.cpp Rename all 2 years ago
raii_event_tests.cpp Rename all 2 years ago
random_tests.cpp Rename all 2 years ago
reverselock_tests.cpp Rename all 2 years ago
rpc_tests.cpp Rename all 2 years ago
sanity_tests.cpp Rename all 2 years ago
scheduler_tests.cpp Rename all 2 years ago
script_P2SH_tests.cpp Rename all 2 years ago
script_standard_tests.cpp Rename all 2 years ago
script_tests.cpp Rename all 2 years ago
scriptnum10.h Rename all 2 years ago
scriptnum_tests.cpp Rename all 2 years ago
serialize_tests.cpp Rename all 2 years ago
sighash_tests.cpp Rename all 2 years ago
sigopcount_tests.cpp Rename all 2 years ago
skiplist_tests.cpp Rename all 2 years ago
streams_tests.cpp Rename all 2 years ago
test_starwels.cpp Rename all 2 years ago
test_starwels.h Rename all 2 years ago
test_starwels_fuzzy.cpp Rename all 2 years ago
test_starwels_main.cpp Rename all 2 years ago
timedata_tests.cpp Rename all 2 years ago
torcontrol_tests.cpp Rename all 2 years ago
transaction_tests.cpp Rename all 2 years ago
txvalidationcache_tests.cpp Rename all 2 years ago
uint256_tests.cpp Rename all 2 years ago
univalue_tests.cpp Rename all 2 years ago
util_tests.cpp Starwels start 2 years ago
versionbits_tests.cpp Rename all 2 years ago

README.md

Compiling/running unit tests

Unit tests will be automatically compiled if dependencies were met in ./configure and tests weren’t explicitly disabled.

After configuring, they can be run with make check.

To run the starwelsd tests manually, launch src/test/test_starwels.

To add more starwelsd tests, add BOOST_AUTO_TEST_CASE functions to the existing .cpp files in the test/ directory or add new .cpp files that implement new BOOST_AUTO_TEST_SUITE sections.

To run the starwels-qt tests manually, launch src/qt/test/test_starwels-qt

To add more starwels-qt tests, add them to the src/qt/test/ directory and the src/qt/test/test_main.cpp file.

Running individual tests

test_starwels has some built-in command-line arguments; for example, to run just the getarg_tests verbosely:

test_starwels --log_level=all --run_test=getarg_tests

… or to run just the doubledash test:

test_starwels --run_test=getarg_tests/doubledash

Run test_starwels --help for the full list.

Note on adding test cases

The sources in this directory are unit test cases. Boost includes a unit testing framework, and since starwels 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_starwels that runs all of the unit tests. The main source file is called test_starwels.cpp. To add a new unit test file to our test suite you need to add the file to src/Makefile.test.include. 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 example of this pattern, examine 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/.