51bad9195e
019c492 qa: Fix lcov for out-of-tree builds (MarcoFalke) e169349 qa: Restore bitcoin-util-test py2 compatibility (MarcoFalke) 806c78f add functional test for mempoolreplacement command line arg (Gregory Sanders) a825d4a Fix bip68-sequence rpc test (Johnson Lau) a36f332 Verify DBWrapper iterators are taking snapshots (Matt Corallo) 8d2e51d qa: Fix bug introduced in p2p-segwit.py (Suhas Daftuar) 2f0b30a qa: Treat mininode p2p exceptions as fatal (Suhas Daftuar) e4605d9 Tests for zmqpubrawtx and zmqpubrawblock (Andrew Chow) 2c4ff35 [script] Unit tests for IsMine (Jim Posen) 794a80e [script] Unit tests for script/standard functions (Jim Posen) f9cf7b5 [tests] Check connectivity before sending in assumevalid.py (John Newbery) f1ced0d [tests] Make p2p-leaktests.py more robust (John Newbery) 2e1ac70 [qa] zapwallettxes: Wait up to 3s for mempool reload (MarcoFalke) b6468d3 Add listwallets RPC test to multiwallet.py (Cristian Mircea Messel) d8dd8e7 [tests] fixup dbcrash interaction with add_nodes() (John Newbery) 2b97b36 [test] Replace check_output with low level version (João Barbosa) e38211f [test] Add assert_raises_process_error to assert process errors (João Barbosa) e0bfd28 [test] Add support for custom arguments to TestNodeCLI (João Barbosa) 812c870 [test] Improve assert_raises_jsonrpc docstring (João Barbosa) eeb24a3 [qa] TestNode: Add wait_until_stopped helper method (MarcoFalke) f3f7891 Stop test_bitcoin-qt touching ~/.bitcoin (MeshCollider) f0b6795 Remove redundant testutil files (MeshCollider) 4424176 Improve signmessages functional test (Cristian Mircea Messel) cef0319 [tests] fixups from set_test_params() (John Newbery) 82bf6fc [tests] Functional tests must explicitly set num_nodes (John Newbery) 801d2ae [tests] don't override __init__() in individual tests (John Newbery) bb5e7cb [tests] Avoid passing around member variables in test_framework (John Newbery) 4d3ba18 [tests] TestNode: separate add_node from start_node (John Newbery) 11a5992 [tests] fix - use rpc_timeout as rpc timeout (John Newbery) 847c75e Add getmininginfo functional test (Cristian Mircea Messel) 2a5d099 RPC: gettxout: Slightly improve doc and tests (Jorge Timón) 716066d [tests] Add bitcoin_cli.py test script (John Newbery) 016b9ad [tests] add TestNodeCLI class for calling bitcoin-cli for a node (John Newbery) 5398f20 qa: Move wait_until to util (MarcoFalke) 1d80d1e [tests] fix timeout issues from TestNode (John Newbery) c276c1e test: Increase initial RPC timeout to 60 seconds (Wladimir J. van der Laan) fc2aa09 [tests] Introduce TestNode (John Newbery) Pull request description: This includes test related backports for 0.15.1. The motivation is twofold: * Make backporting new tests written for current master easier * Fix the most common test issues that happen(ed) frequently on travis Even though this includes the new TestNode class, which comes with a lot of refactoring, I believe that the issues caused by refactoring are found and fixed by now. Tree-SHA512: 6a0c4e5246da83ff0b3f7d2cb8df358d105ed548fb3857e5d882f26cc336553aa07b39e38c281879bf82f95078298b775334f9a60c0b23140f77c50174bd8347
Bitcoin Core integration/staging tree
What is Bitcoin?
Bitcoin is an experimental digital currency that enables instant payments to anyone, anywhere in the world. Bitcoin uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Bitcoin Core is the name of open source software which enables the use of this currency.
For more information, as well as an immediately useable, binary version of the Bitcoin Core software, see https://bitcoin.org/en/download, or read the original whitepaper.
License
Bitcoin Core is released under the terms of the MIT license. See COPYING for more information or see https://opensource.org/licenses/MIT.
Development Process
The master branch is regularly built and tested, but is not guaranteed to be
completely stable. Tags are created
regularly to indicate new official, stable release versions of Bitcoin Core.
The contribution workflow is described in CONTRIBUTING.md.
The developer mailing list should be used to discuss complicated or controversial changes before working on a patch set.
Developer IRC can be found on Freenode at #bitcoin-core-dev.
Testing
Testing and code review is the bottleneck for development; we get more pull requests than we can review and test on short notice. Please be patient and help out by testing other people's pull requests, and remember this is a security-critical project where any mistake might cost people lots of money.
Automated Testing
Developers are strongly encouraged to write unit tests for new code, and to
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.
There are also regression and integration tests, written
in Python, that are run automatically on the build server.
These tests can be run (if the test dependencies are installed) with: test/functional/test_runner.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.
Manual Quality Assurance (QA) Testing
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
Changes to translations as well as new translations can be submitted to Bitcoin Core's Transifex page.
Translations are periodically pulled from Transifex and merged into the git repository. See the translation process for details on how this works.
Important: We do not accept translation changes as GitHub pull requests because the next pull from Transifex would automatically overwrite them again.
Translators should also subscribe to the mailing list.