summaryrefslogtreecommitdiff
path: root/tests
AgeCommit message (Collapse)Author
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.
2017-05-04Build docker image and push it to the container registry when tests/docker ↵Micah Anderson
are changed
2017-04-27[tests] fix testsKali Kaneko (leap communications)
mock a renamed method.
2017-04-03[test] remove randomness testerRuben Pollan
There was a test in the Keymanager refresher that was testing the randomness of the refreshing intervals. It was producing a bunch of intervals and checking that all of them where different. This test (rarelly) fails some times, but this is not a sign of bad randomness. - Resolves: #8813
2017-03-31[bug] Log error in case JSON parsing fails for decrypted docSriram Viswanathan
In addition to the UnicodeError exception in _process_decrypted_doc function, we have added ValueError to the exception list so that we can catch any error in JSON parsing, specially a 'NODATA' error that we were getting with some of the emails. This is in reference to issues - https://github.com/pixelated/pixelated-user-agent/issues/908 & https://github.com/pixelated/pixelated-user-agent/issues/981 - to ignore documents that have this problem and not have Soledad try to sync them again and again. with @deniscostadsc
2017-03-31[bug] fix errBack in _decrypt_doc in incoming mail serviceSriram Viswanathan
with @deniscostadsc
2017-03-30[feature] Creates methods for update recovery code.Thais Siqueira
Related with: https://github.com/pixelated/pixelated-user-agent/issues/924 with @aarni Signed-off-by: Ruben Pollan <meskio@sindominio.net>
2017-02-24[feature] require authentication token for apiKali Kaneko (leap communications)
implements a global auth token for the app. this token is written to .config/leap/authtoken, and passed to the anchor part of the landing URI when opening the index resource by the browser. - Resolves: #8765
2017-02-23[feat] eliminate the active user from bonafideRuben Pollan
Active user is now only a concept of the cli. For it we add a ~/.config/leap/bitmaskctl.cfg file. - Resolves: #8769
2017-02-09[feat] add account based keymanagement APIRuben Pollan
- Resolves: #8755
2017-01-26Check validity of key signatureZara Gebru
Check if a new fetched key was signed by a old key with the same address. Please do not merge before: https://github.com/isislovecruft/python-gnupg/pull/150 - Resolves #8112
2016-12-29[bug] avoid unicode conversion bugKali Kaneko (leap communications)
encode to ascii any parameter passed as unicode.
2016-12-29[feature] better param error handling in rest apiKali Kaneko (leap communications)
2016-12-29[refactor] reorganize APIKali Kaneko (leap communications)
so that whitelisting doesn't have to peek into the data. added more documentation and some tests stubs too.
2016-12-29[tests] add some tests for the apiKali Kaneko (leap communications)
2016-12-29[feature] authentication classes and testsKali Kaneko (leap communications)
2016-12-26[test] fix sender and helo for sending e2e test mailvarac
2016-12-26[test] make e2e test more robust, document depsvarac
2016-12-26[test] clean up output of e2e testvarac
2016-12-26[test] first working e2e testvarac
2016-12-26[test] fix path of getmail scriptvarac
2016-12-26[test] look for mail we just sendvarac
2016-12-26[test] add script for checking the mailKali Kaneko (leap communications)
2016-12-26[test] send mail with custom header to tmp_uservarac
2016-12-26[feat] serial script to create and auth userKali Kaneko (leap communications)
2016-11-30[tests] add unit tests for the keymanager token fixKali Kaneko (leap communications)
my goal here is also to start *real* unit tests for the keymanager, that do not need an actual soledad implementation. this should make all the coming tests much faster. I would like to have a common soledad stub that follows the soledad api, but w/o actual disk persistance, and migrate all the bulk of the keymanager tests to these unit tests.
2016-11-22[tests] fix keymanager tests after refactor and mergeZara Gebru
- some pep8 problems - some confusion with old and new code after merging from old keymanager
2016-11-22[tests] fix some refresher tests after the refactorKali Kaneko (leap communications)
disabled some tests that were failing, for some reason the twisted logger doesn't want to be patched? besides, I don't think it's a good idea to rely on log information for tests. what is it really that we were trying to test there?