status-im
/
status-desktop
mirror of https://github.com/status-im/status-desktop.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
status-desktop/test/e2e
History
Anastasiya Semenkevich 9abc01426f chore: update locators 2024-09-23 17:35:27 +02:00
..
configs chore: use env var for sensitive information 2024-09-05 17:29:39 +03:00
constants chore: use L2 networks for minting community tokens 2024-09-06 20:40:42 +03:00
driver chore: extract methods to helper class 2024-09-10 11:23:14 +03:00
ext test: prepared user data for future tests 2024-06-24 16:24:57 +03:00
fixtures tests: refactor user.py 2024-08-21 17:06:41 +03:00
gui chore: update locators 2024-09-23 17:35:27 +02:00
helpers chore: extract methods to helper class 2024-09-10 11:23:14 +03:00
scripts chore: update random seed generator 2024-09-02 10:01:35 +03:00
tests chore: fix sync devices test and enable it back in PRs 2024-09-23 14:09:19 +03:00
.gitignore ignore envrc and squish.ini 2024-05-31 10:22:29 +02:00
README.md chore: introduce timeout mark and update requirements 2023-12-26 19:14:36 +03:00
conftest.py chore: extract methods to helper class 2024-09-10 11:23:14 +03:00
img.png chore: update readme 2023-12-14 10:45:45 +03:00
img_1.png chore: update readme 2023-12-14 10:45:45 +03:00
pytest.ini chore: introduced local run mark and added skipif mark to skip them on ci 2024-08-09 11:14:54 +03:00
requirements.txt tests: use randomly generated seed where possible 2024-08-26 11:52:39 +02:00

README.md

This repository manages UI tests for desktop application

How to set up your environment

  1. MacOS: https://www.notion.so/Mac-arch-x64-and-Intel-50ea48dae1d4481b882afdbfad38e95a
  2. Linux: https://www.notion.so/Linux-21f7abd2bb684a0fb10057848760a889
  3. Windows: https://www.notion.so/Windows-fbccd2b09b784b32ba4174233d83878d

NOTE: when MacOS and Linux are proven to be working, Windows guide could be outdated (no one yet set up Windows)

Which build to use

  1. you can use your local dev build but sometimes tests hag there. To use it, just place a path to the executable to AUT_PATH in your _local.py config, for example AUT_PATH = "/Users/anastasiya/status-desktop/bin/nim_status_client"

  2. normally, please use CI build. Grab recent one from Jenkins job https://ci.status.im/job/status-desktop/job/nightly/

    2.1 Linux and Windows could be taken from nightly job img.png

    2.2 Mac requires entitlements for Squish which we don't add by default, so please go here https://ci.status.im/job/status-desktop/job/systems/job/macos/ and select architecture you need (arm or intel), click Build with parameters and select Squish entitlements. Select a branch if u like (master is default) img_1.png

Pytest marks used

You can run tests by mark, just use it like this in command line:

python3 -m pytest -m critical

or directly in pycharm terminal:

pytest -m critical

You can obtain the list of all marks we have by running this pytest --markers

  • critical, mark used to select the most important checks we do for PRs in desktop repository (the same for our repo PRs)
  • xfail, used to link tests to existing tickets in desktop, so if test fails it will be marked as expected to fail in report with a reference to the ticket. At the same time, if such test is passing, it will be shown as XPASS (unexpectedly passing) in report, which will indicate the initial bug is gone
  • skip, used to just skip tests for various reasons, normally with a ticket linked
  • flaky, used to mark the tests that are normally passing but sometimes fail. If such test passes, then if will be shown as passed in report normally. If the test fails, then the total run wont be failed, but the corresponding test will be marked as xfail in the report. It is done for a few tests that are not super stable yet, but passes most of the time. This mark should be used with caution and in case of real need only.
  • timeout(timeout=180, method="thread"), to catch excessively long test durations like deadlocked or hanging tests. This is done by pytest-timeout plugin