wownero/tests
Riccardo Spagni 74b699beda
Merge pull request #2812
9ac52127 unit_tests: fix build after wallet2 list/vector change (moneromooo-monero)
2017-11-14 21:33:38 +02:00
..
core_proxy Merge pull request #2736 2017-11-14 21:31:51 +02:00
core_tests remove "using namespace std" from headers 2017-11-14 16:56:10 +00:00
crypto Subaddresses 2017-10-07 13:06:21 +09:00
daemon_tests changed crypto to cncrypto so it generated libcncrypto 2017-05-23 07:45:40 -04:00
data Add fuzz testing using american fuzzy lop 2017-06-24 16:46:18 +01:00
difficulty update copyright year, fix occasional lack of newline at line end 2017-02-21 19:38:18 +02:00
functional_tests Initialize openssl on startup 2017-10-21 10:17:18 +01:00
fuzz move cryptonote command line options to cryptonote_core 2017-11-14 17:06:19 +00:00
gtest updated gtest (added missing files) 2016-01-25 21:19:57 +02:00
hash changed crypto to cncrypto so it generated libcncrypto 2017-05-23 07:45:40 -04:00
libwallet_api_tests Merge pull request #2696 2017-11-14 15:13:44 +02:00
net_load_tests Merge pull request #2696 2017-11-14 15:13:44 +02:00
performance_tests make this build on SunOS/Solaris 2017-11-14 17:03:48 +00:00
unit_tests Merge pull request #2812 2017-11-14 21:33:38 +02:00
CMakeLists.txt always use core_tests for consistency, not coretests 2017-10-19 23:11:29 +01:00
cryptolib.pl update copyright year, fix occasional lack of newline at line end 2017-02-21 19:38:18 +02:00
cryptotest.pl update copyright year, fix occasional lack of newline at line end 2017-02-21 19:38:18 +02:00
hash-target.cpp update copyright year, fix occasional lack of newline at line end 2017-02-21 19:38:18 +02:00
io.h update copyright year, fix occasional lack of newline at line end 2017-02-21 19:38:18 +02:00
README.md Edited test readme for accuracy and depth 2017-10-01 12:11:59 -06: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
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]