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.
 
 
 
 
 
 
Crypto City d8d45c8fba unit_tests: fix build after set_default_palette change 2 months ago
..
block_weight coins can now have a custom graphic design 8 months ago
core_proxy Merge remote-tracking branch 'origin/master' into cc 1 year ago
core_tests v16 with recent consensus changes - with hacks for now 2 months ago
crypto Merge remote-tracking branch 'origin/master' into cc 1 year ago
daemon_tests Add RELINK_TARGETS, monero_add_target_no_relink and use monero_add_executable/monero_add_library where possible (mj-xmr) 1 year ago
data tests: add a decode_blocks fuzz test 2 months ago
db_tests add whispers - player messages on arbitrary locations 2 months ago
difficulty Merge remote-tracking branch 'origin/master' into cc 1 year ago
functional_tests v16 with recent consensus changes - with hacks for now 2 months ago
fuzz tests: add a decode_blocks fuzz test 2 months ago
gtest cmake: set 3.5 as minimum version 9 months ago
hash Merge remote-tracking branch 'origin/master' into cc 1 year ago
libwallet_api_tests Add RELINK_TARGETS, monero_add_target_no_relink and use monero_add_executable/monero_add_library where possible (mj-xmr) 1 year ago
net_load_tests Merge remote-tracking branch 'origin/master' into cc 9 months ago
performance_tests game: load schematic models 4 months ago
trezor Add RELINK_TARGETS, monero_add_target_no_relink and use monero_add_executable/monero_add_library where possible (mj-xmr) 1 year ago
unit_tests unit_tests: fix build after set_default_palette change 2 months ago
CMakeLists.txt Merge remote-tracking branch 'origin/master' into cc 1 year ago
README.md Doc: funtional_tests add new mining env vars and how to use them 9 months ago
benchmark.cpp Support for supercop ASM in wallet, and benchmark for supercop 2 years ago
benchmark.h.in Support for supercop ASM in wallet, and benchmark for supercop 2 years ago
cryptolib.pl Update copyright year to 2020 2 years ago
cryptotest.pl Update copyright year to 2020 2 years ago
hash-target.cpp Update copyright year to 2020 2 years ago
io.h Update copyright year to 2020 2 years ago

README.md

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_tests 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

Parameters

Configuration of individual tests.

Mining test

The following environment variables may be set to control the mining test:

  • MINING_NO_MEASUREMENT - set to anything to use large enough and fixed mining timeouts (use case: very slow PCs and no intention to change the mining code)
  • MINING_SILENT - set to anything to disable mining logging

For example, to customize the run of the functional tests, you may run the following commands from the build directory:

export MINING_NO_MEASUREMENT=1
ctest -V -R functional_tests_rpc
unset MINING_NO_MEASUREMENT

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]