|
|
@ -5,42 +5,42 @@ and tests weren't explicitly disabled. |
|
|
|
|
|
|
|
|
|
|
|
After configuring, they can be run with `make check`. |
|
|
|
After configuring, they can be run with `make check`. |
|
|
|
|
|
|
|
|
|
|
|
To run the litecoind tests manually, launch `src/test/test_litecoin`. To recompile |
|
|
|
To run the kevacoind tests manually, launch `src/test/test_kevacoin`. To recompile |
|
|
|
after a test file was modified, run `make` and then run the test again. If you |
|
|
|
after a test file was modified, run `make` and then run the test again. If you |
|
|
|
modify a non-test file, use `make -C src/test` to recompile only what's needed |
|
|
|
modify a non-test file, use `make -C src/test` to recompile only what's needed |
|
|
|
to run the litecoind tests. |
|
|
|
to run the kevacoind tests. |
|
|
|
|
|
|
|
|
|
|
|
To add more litecoind tests, add `BOOST_AUTO_TEST_CASE` functions to the existing |
|
|
|
To add more kevacoind tests, add `BOOST_AUTO_TEST_CASE` functions to the existing |
|
|
|
.cpp files in the `test/` directory or add new .cpp files that |
|
|
|
.cpp files in the `test/` directory or add new .cpp files that |
|
|
|
implement new BOOST_AUTO_TEST_SUITE sections. |
|
|
|
implement new BOOST_AUTO_TEST_SUITE sections. |
|
|
|
|
|
|
|
|
|
|
|
To run the litecoin-qt tests manually, launch `src/qt/test/test_litecoin-qt` |
|
|
|
To run the kevacoin-qt tests manually, launch `src/qt/test/test_kevacoin-qt` |
|
|
|
|
|
|
|
|
|
|
|
To add more litecoin-qt tests, add them to the `src/qt/test/` directory and |
|
|
|
To add more kevacoin-qt tests, add them to the `src/qt/test/` directory and |
|
|
|
the `src/qt/test/test_main.cpp` file. |
|
|
|
the `src/qt/test/test_main.cpp` file. |
|
|
|
|
|
|
|
|
|
|
|
### Running individual tests |
|
|
|
### Running individual tests |
|
|
|
|
|
|
|
|
|
|
|
test_litecoin has some built-in command-line arguments; for |
|
|
|
test_kevacoin has some built-in command-line arguments; for |
|
|
|
example, to run just the getarg_tests verbosely: |
|
|
|
example, to run just the getarg_tests verbosely: |
|
|
|
|
|
|
|
|
|
|
|
test_litecoin --log_level=all --run_test=getarg_tests |
|
|
|
test_kevacoin --log_level=all --run_test=getarg_tests |
|
|
|
|
|
|
|
|
|
|
|
... or to run just the doubledash test: |
|
|
|
... or to run just the doubledash test: |
|
|
|
|
|
|
|
|
|
|
|
test_litecoin --run_test=getarg_tests/doubledash |
|
|
|
test_kevacoin --run_test=getarg_tests/doubledash |
|
|
|
|
|
|
|
|
|
|
|
Run `test_litecoin --help` for the full list. |
|
|
|
Run `test_kevacoin --help` for the full list. |
|
|
|
|
|
|
|
|
|
|
|
### Note on adding test cases |
|
|
|
### Note on adding test cases |
|
|
|
|
|
|
|
|
|
|
|
The sources in this directory are unit test cases. Boost includes a |
|
|
|
The sources in this directory are unit test cases. Boost includes a |
|
|
|
unit testing framework, and since litecoin already uses boost, it makes |
|
|
|
unit testing framework, and since kevacoin already uses boost, it makes |
|
|
|
sense to simply use this framework rather than require developers to |
|
|
|
sense to simply use this framework rather than require developers to |
|
|
|
configure some other framework (we want as few impediments to creating |
|
|
|
configure some other framework (we want as few impediments to creating |
|
|
|
unit tests as possible). |
|
|
|
unit tests as possible). |
|
|
|
|
|
|
|
|
|
|
|
The build system is setup to compile an executable called "test_litecoin" |
|
|
|
The build system is setup to compile an executable called "test_kevacoin" |
|
|
|
that runs all of the unit tests. The main source file is called |
|
|
|
that runs all of the unit tests. The main source file is called |
|
|
|
test_bitcoin.cpp, which simply includes other files that contain the |
|
|
|
test_bitcoin.cpp, which simply includes other files that contain the |
|
|
|
actual unit tests (outside of a couple required preprocessor |
|
|
|
actual unit tests (outside of a couple required preprocessor |
|
|
|