diff options
author | Varac <varac@leap.se> | 2017-06-09 09:40:55 +0200 |
---|---|---|
committer | Azul <azul@riseup.net> | 2017-07-20 12:34:33 +0200 |
commit | d6abd906cb64ae68eed3348eba521bc44ebed7b2 (patch) | |
tree | fadf7d8270106a628c31b1f7017f343a94f311f0 /tests/functional/README.md | |
parent | c81b98df15e3d2006c991c9ca9d86500e3599e9b (diff) |
[test] Add basic functional login test
* Move todo list to https://0xacab.org/leap/bitmask-dev/issues/8929
* use bundled pysqlcipher - debian package has not been fixed yet.
* reset bitmaskd for each scenario so they are isolated
* run functional tests on CI
* moved e2e tests before the bundle
* add test_functional_graphical Make target
* Install chromedriver in docker image
* add screenshots as artifacts on failure
* run chrome without sandbox for docker
Tests were failing on CI with chrome sandbox:
https://0xacab.org/leap/bitmask-dev/-/jobs/15196
Used this workaround:
https://stackoverflow.com/questions/28364012/webdriver-exception-chrome-not-reachable/28949227#28949227
- Resolves: #8929
Diffstat (limited to 'tests/functional/README.md')
-rw-r--r-- | tests/functional/README.md | 41 |
1 files changed, 41 insertions, 0 deletions
diff --git a/tests/functional/README.md b/tests/functional/README.md new file mode 100644 index 00000000..9405d8e0 --- /dev/null +++ b/tests/functional/README.md @@ -0,0 +1,41 @@ +# Bitmask functional UI tests + +## Todo + +Moved to https://0xacab.org/leap/bitmask-dev/issues/8929#note_111673 + +## Setup + +Ubuntu: + + sudo apt install xvfb chromium-chromedriver + ln -s /usr/lib/chromium-browser/chromedriver venv-all/bin/chromedriver + +Debian: + + sudo apt install xvfb chromedriver + + +Setup your virtualenv and python packages: + + virtualenv venv-all + source ./venv-all/bin/activate + make dev-all + make test_functional_setup + +## Run tests + + source ./venv-all/bin/activate + export TEST_USERNAME='user@provider.tld' TEST_PASSWORD='...' + make test_functional + +# Develop tests + +When tests are run using `make test_functional` no window shows you what the browser sees. +In order to see tests running in the browser run: + + make test_functional_graphical + +You can also run behave by itself and have a browser window to watch, i.e. to run all tests tagged as `@wip`: + + behave --wip -k -D host=localhost tests/functional/features |