You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+6-8Lines changed: 6 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,17 +55,15 @@ There are also regression and integration tests of the RPC interface, written
55
55
in Python, that are run automatically on the build server.
56
56
These tests can be run with: `qa/pull-tester/rpc-tests.py`
57
57
58
-
Every pull request is built for both Windows and Linux on a dedicated server,
59
-
and unit and sanity tests are automatically run. The binaries produced may be
60
-
used for manual QA testing — a link to them will appear in a comment on the
61
-
pull request posted by [BitcoinPullTester](https://github.com/BitcoinPullTester). See https://github.com/TheBlueMatt/test-scripts
62
-
for the build/test scripts.
58
+
The Travis CI system makes sure that every pull request is built for Windows
59
+
and Linux, OSX, and that unit and sanity tests are automatically run.
63
60
64
61
### Manual Quality Assurance (QA) Testing
65
62
66
-
Large changes should have a test plan, and should be tested by somebody other
67
-
than the developer who wrote the code.
68
-
See https://github.com/bitcoin/QA/ for how to create a test plan.
63
+
Changes should be tested by somebody other than the developer who wrote the
64
+
code. This is especially important for large or high-risk changes. It is useful
65
+
to add a test plan to the pull request description if testing the changes is
0 commit comments