sikkienl/dash
1
0
Fork 0
mirror of https://github.com/dashpay/dash.git synced 2024-12-25 20:12:57 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

s/bitcoin/dash

Browse Source 
Signed-off-by: Pasta <pasta@dashboost.org>
This commit is contained in:
Pasta 2019-07-24 12:03:39 -05:00
parent 83af2d8d50
commit c34ec30b61
No known key found for this signature in database
GPG Key ID: D362C9F7142766AE
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
test/README.md
View File

@ -155,7 +155,7 @@ import pdb; pdb.set_trace()
anywhere in the test. You will then be able to inspect variables, as well as anywhere in the test. You will then be able to inspect variables, as well as
call methods that interact with the dashd nodes-under-test. call methods that interact with the dashd nodes-under-test.
If further introspection of the bitcoind instances themselves becomes If further introspection of the dashd instances themselves becomes
necessary, this can be accomplished by first setting a pdb breakpoint necessary, this can be accomplished by first setting a pdb breakpoint
at an appropriate location, running the test to that point, then using at an appropriate location, running the test to that point, then using
`gdb` to attach to the process and debug. `gdb` to attach to the process and debug.
@ -169,15 +169,15 @@ For instance, to attach to `self.node[1]` during a run:
use the directory path to get the pid from the pid file: use the directory path to get the pid from the pid file:
```bash ```bash
cat /tmp/user/1000/testo9vsdjo3/node1/regtest/bitcoind.pid cat /tmp/user/1000/testo9vsdjo3/node1/regtest/dashd.pid
gdb /home/example/bitcoind <pid> gdb /home/example/dashd <pid>
``` ```
Note: gdb attach step may require `sudo` Note: gdb attach step may require `sudo`
### Util tests ### Util tests
Util tests can be run locally by running `test/util/bitcoin-util-test.py`. Util tests can be run locally by running `test/util/dash-util-test.py`.
Use the `-v` option for verbose output. Use the `-v` option for verbose output.
# Writing functional tests # Writing functional tests