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.
wownero/tests
Howard Chu 177148468a
Fix missing std::runtime_error def in difficulty.cpp
6 years ago
..
core_proxy Only log an error if fork version is higher AND is not known. 6 years ago
core_tests keypair::generate: always require hw::device to avoid possible mistake 6 years ago
crypto crypto: revert odd namespace changes made in #3303 6 years ago
daemon_tests Update 2018 copyright 6 years ago
data tests: add levin fuzz test 6 years ago
difficulty Fix missing std::runtime_error def in difficulty.cpp 6 years ago
functional_tests Stagenet 6 years ago
fuzz epee: adaptive connection timeout system 6 years ago
gtest gtest: use -fPIC with CLANG too 6 years ago
hash cryptonote tweak v2.2 6 years ago
libwallet_api_tests Fix typos in various files 6 years ago
net_load_tests Fix typos in various files 6 years ago
performance_tests add and use constant time 32 byte equality function 6 years ago
unit_tests add and use constant time 32 byte equality function 6 years ago
CMakeLists.txt Update 2018 copyright 6 years ago
README.md Edited test readme for accuracy and depth 7 years ago
cryptolib.pl Update 2018 copyright 6 years ago
cryptotest.pl Update 2018 copyright 6 years ago
hash-target.cpp Update 2018 copyright 6 years ago
io.h Update 2018 copyright 6 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
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]

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

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]