From aeb25ba1385278e4cbec496582d00306f04c8d81 Mon Sep 17 00:00:00 2001 From: Leny Kholodov Date: Tue, 14 May 2019 00:59:50 +0300 Subject: [PATCH] rename: monero -> graft --- tests/README.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/tests/README.md b/tests/README.md index 0bf097254..6ef48bf75 100644 --- a/tests/README.md +++ b/tests/README.md @@ -3,7 +3,7 @@ To run all tests, run: ``` -cd /path/to/monero +cd /path/to/graft make [-jn] debug-test # where n is number of compiler processes ``` @@ -11,11 +11,11 @@ To test a release build, replace `debug-test` with `release-test` in the previou # Core tests -Core tests take longer than any other Monero tests, due to the high amount of computational work involved in validating core components. +Core tests take longer than any other Graft 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): +To run only Graft's core tests (after building): ``` cd build/debug/tests/core @@ -34,7 +34,7 @@ Crypto tests are located under the `tests/crypto` directory. 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): +To run only Graft's crypto tests (after building): ``` cd build/debug/tests/crypto @@ -54,7 +54,7 @@ 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 +graftnoded --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. @@ -63,7 +63,7 @@ Next, restore a mainnet wallet with the following seed and restore height 0 (the 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 +Open the wallet file with `graft-wallet-rpc` with RPC port 18083. Finally, start tests by invoking ./blockchain.py or ./speed.py # Fuzz tests @@ -75,7 +75,7 @@ An additional helper utility is provided `contrib/fuzz_testing/fuzz.sh`. AFL mus 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): +To run only Graft's hash tests (after building): ``` cd build/debug/tests/hash @@ -96,7 +96,7 @@ To run the same tests on a release build, replace `debug` with `release`. 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): +To run only Graft's performance tests (after building): ``` cd build/debug/tests/performance_tests @@ -111,7 +111,7 @@ To run the same tests on a release build, replace `debug` with `release`. 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): +To run only Graft's unit tests (after building): ``` cd build/debug/tests/unit_tests