/docs/standalone/building-on-electrumsv/functional-tests.rst

https://github.com/electrumsv/electrumsv · ReStructuredText · 78 lines · 57 code · 21 blank · 0 comment · 0 complexity · 3edd51a750febeef7ea9b5146a399229 MD5 · raw file 

    

  1. Functional tests
    2. 

  2. ===================
    3. 

  3. The functional tests are a set of tests that use the REST API to manipulate the state of a
    4. 

  4. 'live' RegTest wallet and check that the state changes are matching what is expected.
    5. 

  5. Eventually, the REST API should mature to cover all functionality available through the GUI,
    6. 

  6. allowing automation of any wallet tasks as well as full end-to-end integration testing
    7. 

  7. coverage.
    8. 

  8. 

  9. The functional tests are run as part of the Azure pipeline for any commits to any new
    10. 

  10. feature branch or pull requests but can also be run locally (and offline) provided a few
    11. 

  11. dependencies are installed.
    12. 

  12. 

  13. A few examples of functional tests are:
    14. 

  14. 

  15. - A simulated reorg test (via the RegTest SDK) in which wallet transactions are affected and move to a new block height with a new merkle branch. The database and general wallet state is checked for consistency before and after the reorg.
    16. 

  16. - Loading the wallet on the daemon.
    17. 

  17. - Getting the account details.
    18. 

  18. - Getting utxos before and after topping up the wallet with new coins.
    19. 

  19. - Getting utxos before and after splitting a coin into smaller outputs.
    20. 

  20. - Concurrent transaction broadcasting to check the broadcast pathway and as a basic check for data races.
    21. 

  21. 

  22. These tests give a broad-brush coverage of many different code paths and as the
    23. 

  23. REST API grows to cover all GUI interactions will give assurances about:
    24. 

  24. 

  25. - Correctness of wallet state.
    26. 

  26. - Regressions at the wallet server level that could in turn affect the user experience.
    27. 

  27. 

  28. Installation of dependencies
    29. 

  29. -------------------------------
    30. 

  30. 

  31. 1. Install pytest pre-requisites::
    32. 

  32. 

  33.     python3 -m pip install pytest pytest-cov pytest-asyncio pytest-timeout electrumsv_node openpyxl
    34. 

  34. 

  35. 

  36. 2. Install the ElectrumSV-SDK (follow instructions here: https://electrumsv-sdk.readthedocs.io/ ) and then do::
    37. 

  37. 

  38.     electrumsv-sdk install node
    39. 

  39.     electrumsv-sdk install electrumx
    40. 

  40.     electrumsv-sdk install --repo=$PWD electrumsv
    41. 

  41. 

  42. This will install the repositories and dependencies for these components.
    43. 

  43. 

  44. Run the functional tests
    45. 

  45. --------------------------
    46. 

  46. **The SDK components should be stopped before running the tests as the tests automate
    47. 

  47. resetting and starting these services - it will fail if they are already running**.
    48. 

  48. 

  49. Run the functional tests with pytest like this::
    50. 

  50. 

  51.     python3 -m pytest -v -v -v contrib/functional_tests/functional
    52. 

  52. 

  53. Which should output something like (but with verbose logging output)::
    54. 

  54. 

  55.     contrib\functional_tests\functional\test_reorg.py::TestReorg::test_reorg PASSED
    56. 

  56.     contrib\functional_tests\functional\test_restapi.py::TestRestAPI::test_get_all_wallets PASSED                                                              [ 25%]
    57. 

  57.     contrib\functional_tests\functional\test_restapi.py::TestRestAPI::test_load_wallet PASSED                                                                  [ 33%]
    58. 

  58.     contrib\functional_tests\functional\test_restapi.py::TestRestAPI::test_websocket_wait_for_mempool PASSED                                                   [ 41%]
    59. 

  59.     contrib\functional_tests\functional\test_restapi.py::TestRestAPI::test_websocket_wait_for_confirmation PASSED                                              [ 50%]
    60. 

  60.     contrib\functional_tests\functional\test_restapi.py::TestRestAPI::test_get_parent_wallet PASSED                                                            [ 58%]
    61. 

  61.     contrib\functional_tests\functional\test_restapi.py::TestRestAPI::test_get_account PASSED                                                                  [ 66%]
    62. 

  62.     contrib\functional_tests\functional\test_restapi.py::TestRestAPI::test_get_utxos_and_top_up PASSED                                                         [ 75%]
    63. 

  63.     contrib\functional_tests\functional\test_restapi.py::TestRestAPI::test_get_balance PASSED                                                                  [ 83%]
    64. 

  64.     contrib\functional_tests\functional\test_restapi.py::TestRestAPI::test_concurrent_tx_creation_and_broadcast PASSED                                         [ 91%]
    65. 

  65.     contrib\functional_tests\functional\test_restapi.py::TestRestAPI::test_create_and_broadcast_exception_handling PASSED
    66. 

  66. 

  67.     ============================================================= 11 passed, 1 skipped, 0 failed in 49.53s ==========================================================
    68. 

  68. 

  69. Logging
    70. 

  70. ---------------
    71. 

  71. There is a ``pytest.ini`` file in ``contrib/functional_tests/pytest.ini`` with these settings::
    72. 

  72. 

  73.     [pytest]
    74. 

  74.     log_cli=true
    75. 

  75.     log_level=INFO
    76. 

  76. 

  77. If you are finding the logging details distracting or you want more verbose logging you can refer
    78. 

  78. to the pytest documentation and change the ``pytest.ini`` settings as needed.
    79.