Browse Source
Refer to the right file in the top-level README.md. Having only one file with test documentation saves some confusion about where things are documented.0.14
Wladimir J. van der Laan
8 years ago
4 changed files with 37 additions and 34 deletions
@ -1,18 +0,0 @@ |
|||||||
Compiling/running unit tests |
|
||||||
------------------------------------ |
|
||||||
|
|
||||||
Unit tests will be automatically compiled if dependencies were met in `./configure` |
|
||||||
and tests weren't explicitly disabled. |
|
||||||
|
|
||||||
After configuring, they can be run with `make check`. |
|
||||||
|
|
||||||
To run the bitcoind tests manually, launch `src/test/test_bitcoin`. |
|
||||||
|
|
||||||
To add more bitcoind tests, add `BOOST_AUTO_TEST_CASE` functions to the existing |
|
||||||
.cpp files in the `test/` directory or add new .cpp files that |
|
||||||
implement new BOOST_AUTO_TEST_SUITE sections. |
|
||||||
|
|
||||||
To run the bitcoin-qt tests manually, launch `src/qt/test/test_bitcoin-qt` |
|
||||||
|
|
||||||
To add more bitcoin-qt tests, add them to the `src/qt/test/` directory and |
|
||||||
the `src/qt/test/test_main.cpp` file. |
|
Loading…
Reference in new issue