townforge/tests
2021-05-23 18:25:51 +00:00
..
block_weight remove mime_type from custom items, and add gold content 2021-03-25 14:37:56 +00:00
core_proxy Merge remote-tracking branch 'origin/master' into cc 2021-01-18 01:33:53 +00:00
core_tests decrease decay and repair costs, bump land tax a little 2021-04-27 18:39:05 +00:00
crypto Merge remote-tracking branch 'origin/master' into cc 2021-01-18 01:33:53 +00:00
daemon_tests Add RELINK_TARGETS, monero_add_target_no_relink and use monero_add_executable/monero_add_library where possible (mj-xmr) 2020-10-28 20:08:26 +01:00
data fuzz_tests: add a test for utf8canonical 2020-12-14 19:40:24 +00:00
db_tests remove various unused variables 2021-04-27 18:15:29 +00:00
difficulty Merge remote-tracking branch 'origin/master' into cc 2021-01-18 01:33:53 +00:00
functional_tests add logging/quarrying/maintenance discoveries 2021-05-14 17:22:13 +00:00
fuzz port feather monero changes to townforge 2021-05-23 18:25:51 +00:00
gtest Made code block usage consistent across all .md files 2019-05-12 05:16:26 +01:00
hash Merge remote-tracking branch 'origin/master' into cc 2021-01-18 01:33:53 +00:00
libwallet_api_tests Add RELINK_TARGETS, monero_add_target_no_relink and use monero_add_executable/monero_add_library where possible (mj-xmr) 2020-10-28 20:08:26 +01:00
net_load_tests Merge remote-tracking branch 'origin/master' into cc 2021-04-24 13:46:11 +00:00
performance_tests Merge remote-tracking branch 'origin/master' into cc 2021-04-24 13:46:11 +00:00
trezor Add RELINK_TARGETS, monero_add_target_no_relink and use monero_add_executable/monero_add_library where possible (mj-xmr) 2020-10-28 20:08:26 +01:00
unit_tests add logging/quarrying/maintenance discoveries 2021-05-14 17:22:13 +00:00
benchmark.cpp Support for supercop ASM in wallet, and benchmark for supercop 2020-05-16 10:25:17 +00:00
benchmark.h.in Support for supercop ASM in wallet, and benchmark for supercop 2020-05-16 10:25:17 +00:00
CMakeLists.txt Merge remote-tracking branch 'origin/master' into cc 2021-01-18 01:33:53 +00:00
cryptolib.pl Update copyright year to 2020 2020-05-06 22:36:54 -04:00
cryptotest.pl Update copyright year to 2020 2020-05-06 22:36:54 -04:00
hash-target.cpp Update copyright year to 2020 2020-05-06 22:36:54 -04:00
io.h Update copyright year to 2020 2020-05-06 22:36:54 -04:00
README.md [CI] Adaptive mining timeout, depending on available CPU power 2021-03-30 05:48:55 +02:00

Running all tests

To run all tests, run:

cd /path/to/monero
make [-jn] debug-test # where n is number of compiler processes

To test a release build, replace debug-test with release-test in the previous command.

Core tests

Core tests take longer than any other Monero tests, due to the high amount of computational work involved in validating core components.

Tests are located in tests/core_tests/, and follow a straightforward naming convention. Most cases cover core functionality (block_reward.cpp, chaingen.cpp, rct.cpp, etc.), while some cover basic security tests (double_spend.cpp & integer_overflow.cpp).

To run only Monero's core tests (after building):

cd build/debug/tests/core_tests
ctest

To run the same tests on a release build, replace debug with release.

Crypto Tests

Crypto tests are located under the tests/crypto directory.

  • crypto-tests.h contains test harness headers
  • main.cpp implements the driver for the crypto tests

Tests correspond to components under src/crypto/. A quick comparison reveals the pattern, and new tests should continue the naming convention.

To run only Monero's crypto tests (after building):

cd build/debug/tests/crypto
ctest

To run the same tests on a release build, replace debug with release.

Daemon tests

[TODO]

Functional tests

[TODO] Functional tests are located under the tests/functional directory.

Building all the tests requires installing the following dependencies:

pip install requests psutil monotonic

First, run a regtest daemon in the offline mode and with a fixed difficulty:

monerod --regtest --offline --fixed-difficulty 1

Alternatively, you can run multiple daemons and let them connect with each other by using --add-exclusive-node. In this case, make sure that the same fixed difficulty is given to all the daemons.

Next, restore a mainnet wallet with the following seed and restore height 0 (the file path doesn't matter):

velvet lymph giddy number token physics poetry unquoted nibs useful sabotage limits benches lifestyle eden nitrogen anvil fewest avoid batch vials washing fences goat unquoted

Open the wallet file with monero-wallet-rpc with RPC port 18083. Finally, start tests by invoking ./blockchain.py or ./speed.py

Fuzz tests

Fuzz tests are written using American Fuzzy Lop (AFL), and located under the tests/fuzz directory.

An additional helper utility is provided contrib/fuzz_testing/fuzz.sh. AFL must be installed, and some additional setup may be necessary for the script to run properly.

Hash tests

Hash tests exist under tests/hash, and include a set of target hashes in text files.

To run only Monero's hash tests (after building):

cd build/debug/tests/hash
ctest

To run the same tests on a release build, replace debug with release.

Libwallet API tests

[TODO]

Net Load tests

[TODO]

Performance tests

Performance tests are located in tests/performance_tests, and test features for performance metrics on the host machine.

To run only Monero's performance tests (after building):

cd build/debug/tests/performance_tests
./performance_tests

The path may be build/Linux/master/debug (adapt as necessary for your platform).

If the performance_tests binary does not exist, try running make in the build/debug/tests/performance_tests directory.

To run the same tests on a release build, replace debug with release.

Unit tests

Unit tests are defined under the tests/unit_tests directory. Independent components are tested individually to ensure they work properly on their own.

To run only Monero's unit tests (after building):

cd build/debug/tests/unit_tests
ctest

To run the same tests on a release build, replace debug with release.

Writing new tests

Test hygiene

When writing new tests, please implement all functions in .cpp or .c files, and only put function headers in .h files. This will help keep the fairly complex test suites somewhat sane going forward.

Writing fuzz tests

[TODO]