d0s3t3ch
/
wownero
mirror of https://git.wownero.com/wownero/wownero.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
wownero/tests
History
Lee Clagett 973403bc9f Adding initial support for broadcasting transactions over Tor 
- Support for ".onion" in --add-exclusive-node and --add-peer
  - Add --anonymizing-proxy for outbound Tor connections
  - Add --anonymous-inbounds for inbound Tor connections
  - Support for sharing ".onion" addresses over Tor connections
  - Support for broadcasting transactions received over RPC exclusively
    over Tor (else broadcast over public IP when Tor not enabled).
 		2019-01-28 23:56:33 +00:00
..
core_proxy Pruning 2019-01-22 20:30:51 +00:00
core_tests ringct: encode 8 byte amount, saving 24 bytes per output 2019-01-22 23:17:31 +00:00
crypto Merge pull request #4489 2018-10-15 13:37:18 +02:00
daemon_tests Update 2018 copyright 2018-01-26 10:03:20 -05:00
data wallet2: only export necessary outputs and key images 2018-11-04 22:27:01 +00:00
difficulty Fix missing std::runtime_error def in difficulty.cpp 2018-09-16 19:35:07 +00:00
functional_tests Remove boost::lexical_cast for uuid and unused uuid function 2018-12-23 11:11:30 +00:00
fuzz epee: better network buffer data structure 2018-12-23 16:46:07 +00:00
gtest gtest: use -fPIC with CLANG too 2018-06-28 16:42:52 +01:00
hash cryptonote tweak v2.2 2018-09-22 03:47:50 +00:00
libwallet_api_tests libwallet_api_tests: add missing dependency on Boost Locale and ICU 2018-11-15 00:19:41 +09:00
net_load_tests Merge pull request #5001 2019-01-16 19:27:13 +02:00
performance_tests add a bulletproof version, new bulletproof type, and rct config 2019-01-22 23:17:24 +00:00
unit_tests Adding initial support for broadcasting transactions over Tor 2019-01-28 23:56:33 +00:00
CMakeLists.txt Update 2018 copyright 2018-01-26 10:03:20 -05:00
README.md remove trailing whitespace in README.md 2019-01-02 12:25:18 +11:00
cryptolib.pl Update 2018 copyright 2018-01-26 10:03:20 -05:00
cryptotest.pl Update 2018 copyright 2018-01-26 10:03:20 -05:00
hash-target.cpp Update 2018 copyright 2018-01-26 10:03:20 -05:00
io.h Update 2018 copyright 2018-01-26 10:03:20 -05:00

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] Functional tests are located under the tests/functional directory.

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

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]