Skip to content
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.

Commit

Permalink
Update readme with correct instructions to run tests
Browse files Browse the repository at this point in the history
  • Loading branch information
nazarhussain committed Jun 28, 2018
1 parent bb6ae35 commit bae0e80
Showing 1 changed file with 3 additions and 9 deletions.
12 changes: 3 additions & 9 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -194,7 +194,7 @@ To test Lisk is built and configured correctly, issue the following command:
node app.js
```
Once the process is verified as running correctly, `CTRL+C` and start the process with `pm2`. This will fork the process into the background and automatically recover the process if it fails.
This will start the lisk instance with `devnet` configuration. Once the process is verified as running correctly, `CTRL+C` and start the process with `pm2`. This will fork the process into the background and automatically recover the process if it fails.
```
pm2 start --name lisk app.js
Expand All @@ -218,7 +218,7 @@ pm2 stop lisk
pm2 start --name lisk app.js -- -p [port] -a [address] -c [config-path] -n [network]
```
You can pass any of `devnet`, `testnet`, `betanet` or `mainnet` for the network option.
You can pass any of `devnet`, `alphanet`, `betanet`, `testnet` or `mainnet` for the network option.
## Tests
Expand All @@ -231,13 +231,7 @@ dropdb lisk_test
createdb lisk_test
```
2. Ensure Lisk is configured to run on the same local network used by the tests. Replace the files **config.json** and **genesis_block.json** with those located under the **test/data** directory:
```
cp test/data/config.json test/data/genesis_block.json .
```
3. Launch Lisk (runs on port 4000):
2. Launch Lisk (runs on port 4000):
```
NODE_ENV=test node app.js
Expand Down

0 comments on commit bae0e80

Please sign in to comment.