@ -54,9 +54,9 @@ submit new unit tests for old code. Unit tests can be compiled and run
@@ -54,9 +54,9 @@ submit new unit tests for old code. Unit tests can be compiled and run
(assuming they weren't disabled in configure) with: `make check`. Further details on running
and extending unit tests can be found in [/src/test/README.md](/src/test/README.md).
There are also [regression and integration tests](/qa) of the RPC interface, written
There are also [regression and integration tests](/test) of the RPC interface, written
in Python, that are run automatically on the build server.
These tests can be run (if the [test dependencies](/qa) are installed) with: `qa/pull-tester/rpc-tests.py`
These tests can be run (if the [test dependencies](/test) are installed) with: `test/pull-tester/rpc-tests.py`
The Travis CI system makes sure that every pull request is built for Windows, Linux, and OS X, and that unit/sanity tests are run automatically.
@ -132,7 +132,7 @@ Run with the -testnet option to run with "play bitcoins" on the test network, if
@@ -132,7 +132,7 @@ Run with the -testnet option to run with "play bitcoins" on the test network, if
are testing multi-machine code that needs to operate across the internet.
If you are testing something that can run on one machine, run with the -regtest option.
In regression test mode, blocks can be created on-demand; see qa/rpc-tests/ for tests
In regression test mode, blocks can be created on-demand; see test/rpc-tests/ for tests
By default, tests will be run in parallel. To specify how many jobs to run,
append `--jobs=n` (default n=4).
@ -61,7 +61,7 @@ Possible options, which apply to each individual test run:
@@ -61,7 +61,7 @@ Possible options, which apply to each individual test run:
```
If you set the environment variable `PYTHON_DEBUG=1` you will get some debug
@ -11,7 +11,7 @@ forward all unrecognized arguments onto the individual test scripts.
@@ -11,7 +11,7 @@ forward all unrecognized arguments onto the individual test scripts.