LBRYCommunity/lbrycrd
1
0
Fork 0
Code Issues 29 Pull requests 1 Projects Releases 32 Packages Wiki Activity

Merge pull request #6998

Browse source 
01afa80 doc: Remove mention of pulltester from README.md (Wladimir J. van der Laan)
This commit is contained in:
Wladimir J. van der Laan 2015-11-13 10:11:20 +01:00
commit 24c4841d16
No known key found for this signature in database
GPG key ID: 74810B012346C9A6
1 changed files with 6 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
README.md
View file

@ -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. in Python, that are run automatically on the build server.
These tests can be run with: `qa/pull-tester/rpc-tests.py` 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, The Travis CI system makes sure that every pull request is built for Windows
and unit and sanity tests are automatically run. The binaries produced may be and Linux, OSX, and that unit and sanity tests are automatically run.
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.
### Manual Quality Assurance (QA) Testing ### Manual Quality Assurance (QA) Testing
Large changes should have a test plan, and should be tested by somebody other Changes should be tested by somebody other than the developer who wrote the
than the developer who wrote the code. code. This is especially important for large or high-risk changes. It is useful
See https://github.com/bitcoin/QA/ for how to create a test plan. to add a test plan to the pull request description if testing the changes is
not straightforward.
Translations Translations
------------ ------------