aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorWladimir J. van der Laan <laanwj@gmail.com>2015-11-13 10:11:20 +0100
committerWladimir J. van der Laan <laanwj@gmail.com>2015-11-13 10:11:22 +0100
commit24c4841d16862c201bf62218280c2194a85a81ca (patch)
tree1de6981aa85b6007fb44c3de9aa242a172ea652d
parent38ed190eefccf8865d984e08f4dfe4063ed8a55b (diff)
parent01afa809cef688ff7f5af491005ba4abd3cd4098 (diff)
Merge pull request #6998
01afa80 doc: Remove mention of pulltester from README.md (Wladimir J. van der Laan)
-rw-r--r--README.md14
1 files changed, 6 insertions, 8 deletions
diff --git a/README.md b/README.md
index 5aa8c327df..c08b2fb0bc 100644
--- a/README.md
+++ b/README.md
@@ -55,17 +55,15 @@ There are also regression and integration tests of the RPC interface, written
in Python, that are run automatically on the build server.
These tests can be run with: `qa/pull-tester/rpc-tests.py`
-Every pull request is built for both Windows and Linux on a dedicated server,
-and unit and sanity tests are automatically run. The binaries produced may be
-used for manual QA testing — a link to them will appear in a comment on the
-pull request posted by [BitcoinPullTester](https://github.com/BitcoinPullTester). See https://github.com/TheBlueMatt/test-scripts
-for the build/test scripts.
+The Travis CI system makes sure that every pull request is built for Windows
+and Linux, OSX, and that unit and sanity tests are automatically run.
### Manual Quality Assurance (QA) Testing
-Large changes should have a test plan, and should be tested by somebody other
-than the developer who wrote the code.
-See https://github.com/bitcoin/QA/ for how to create a test plan.
+Changes should be tested by somebody other than the developer who wrote the
+code. This is especially important for large or high-risk changes. It is useful
+to add a test plan to the pull request description if testing the changes is
+not straightforward.
Translations
------------