Cypher_Stack/wownero
2
0
Fork 0
mirror of https://git.wownero.com/wownero/wownero.git synced 2025-01-04 23:18:53 +00:00
Code Issues Packages Projects Releases Wiki Activity

fixed tests/README.md

Browse Source
This commit is contained in:
notmike 2019-02-21 08:34:37 -07:00
parent 466140f55e
commit 05e0624b81
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
tests/README.md
View File

@ -3,7 +3,7 @@
To run all tests, run:
```
cd /path/to/monero
cd /path/to/wownero
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 Wownero 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 Wownero'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 Wownero'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
wownerod --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.
@ -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 Wownero'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 Wownero'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 Wownero's unit tests (after building):
```
cd build/debug/tests/unit_tests