summaryrefslogtreecommitdiff
path: root/tests
AgeCommit message (Collapse)Author
2017-08-30[tests] apply dns workaround for functional testsKali Kaneko
2017-08-30[tests] apply dns workaroundKali Kaneko
2017-08-30[tests] increase timeout on vpn onKali Kaneko
2017-08-30[tests] reuse tox virtualenv for e2e/functionalKali Kaneko
2017-08-30[tests] add another demo gatewayKali Kaneko
2017-08-30[bug] assert vpn management folder existsKali Kaneko
2017-08-30[tests] use another geoip api to avoid json decode problemsKali Kaneko
2017-08-30[tests] add root-switch as dns workaround for tests on CIKali Kaneko
2017-08-30[tests] do not fail if helper installed in debian pathKali Kaneko
2017-08-30[tests] fix check-ip scriptKali Kaneko
2017-08-30[tests] workaround some errors while running testsKali Kaneko
2017-08-30[tests] prepare to run behave against bundleKali Kaneko
2017-08-30[tests] increase timeoutKali Kaneko
2017-08-30[tests] Check egress IP for VPN stepsVarac
2017-08-30[tests] fix test case typoKali Kaneko
2017-08-30[tests] fix path for data filesKali Kaneko
2017-08-30[refactor] re-add retries for connecting to managementKali Kaneko
2017-08-30[refactor] integrate new management protocolKali Kaneko
2017-08-30[feature] add twisted protocol for handling openvpn managementKali Kaneko
2017-08-25[bug] replace content-type after removing the signatureRuben Pollan
- Resolves: #9003
2017-08-14[tests] pep8 test_gateways.pyazul
tests were failing because of pep8 issues
2017-08-11[feature] allow manual gateway selection for vpnKali Kaneko
For now, the way to select a gateway is to add a section in bitmaskd.cfg: [vpn_prefs] locations = ["frankfurt", "seattle__wa"] countries = ["DE", "US"] Note that the location indication has priority over country code. This will be exposed by the UI in release 0.11 - Resolves: #8855
2017-08-11[feature] automatic vpn gateway selection, based on timezoneKali Kaneko
This is a first approach to automatic gateways selection. More things are missing: - allow manual selection, by location or country code. - take the hemisphere into account. - expose the selected gw to the api/cli but overall seems this is a good approach to make 0.10 release usable in terms of vpn. - Resolves: #8804
2017-07-21[tests] Succeed VPN test if helper files existsVarac
2017-07-20[test] keep artifacts inside the project dirAzul
2017-07-20[test] enable and check vpnAzul
2017-07-20[test] minor: only set env["HOME"] onceAzul
2017-07-20[tests] clearer message if test user not definedKali Kaneko
2017-07-20[doc] Tests inside docker with gitlab-runnerVarac
2017-07-20[test] keep config files from failing testsAzul
2017-07-20[test] Add basic functional login testVarac
* 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
2017-07-18[test] ca_cert_path can not be an empty stringRuben Pollan
2017-06-12[feat] push private key updates into nicknymRuben Pollan
Deal as well with sending key if key is outdated in the providers nicknym. - Resolves: #8819, #8832
2017-06-07[tests] enable mail e2e againKali Kaneko (leap communications)
- skip ssl verification for this test - use mail.bitmask as e2e provider for now (ci.leap.se seems broken; cannot download smtp cert)
2017-06-07[feature] run vpn directly if user is rootKali Kaneko (leap communications)
- Improve tests too: add entry in resolv.conf, not done without resolvconf
2017-06-07[tests] improve vpn e2e testKali Kaneko (leap communications)
- add invite code
2017-06-07[tests] simple e2e vpn testKali Kaneko (leap communications)
- Resolves: #8874
2017-06-05[test] validate the CA cert fingerprint checkRuben Pollan
2017-06-05[bug] fail bonafide bootstrap for self sign certsRuben Pollan
- Resolves: #8881
2017-05-24[tests] fix testsKali Kaneko (leap communications)
2017-05-22[tests] add lxpolkit to the test-docker depsKali Kaneko (leap communications)
this is an attempt to debug the failure of the vpn e2e test on the works. if this commit makes the test pass, it means that we need to capture the "no polkit authentication agent running" in a more meaningful way.
2017-05-22[tests] add openvpn and mocha to docker test containerKali Kaneko (leap communications)
2017-05-19[tests] get invite code from env variableKali Kaneko (leap communications)
the BITMASK_INVITE_CODE variable must be set from within the CI settings.
2017-05-18[pkg] need wget for bundlesKali Kaneko (leap communications)
2017-05-18[tests] touch the dockerfile to force it being rebuiltKali Kaneko (leap communications)
2017-05-17[bug] add policykit-1 to docker image for e2e testsKali Kaneko (leap communications)
2017-05-16[tests] remove listener testKali Kaneko (leap communications)
I've removed the add_listener method because it's not used anywhere.
2017-05-16[bug] fix notification for incoming mail with several listeners registeredKali Kaneko (leap communications)
When setting the listeners in the IMAP Folder, we avoid setting more than one listener for the same imap mailbox (because in some situations we were registering way too many listeners). this was making the pixelated inbox registering the notification and therefore the imap mailbox not being registered. this MR also refactors the way pixelated is initialized, so that it avoid creating a second Account instance. In this way, we make sure that the pixelated mua and the imap server share the same collections for a given mailbox, and therefore any of the two is able to get a notification whenever the other adds a message to the mailbox. - Resolves: #8846, #8798
2017-05-09Run e2e tests againts ci.leap.sevarac
Resolves: #8882
2017-05-04[feat] Create and publish docker image (see #8755).Micah Anderson
When the tests/docker directory is changed, this CI job is triggered to build the docker image and push it to the bitmask-dev container registry. This allows us to change the existing CI jobs to pull the image from our registry, instead of from dockerhub.