soledad.git/testing, branch 0.9.5 [soledad] [refactor] Improve python3 compatibility 2017-03-17T16:52:57+00:00 efkin efkin@riseup.net 2017-03-13T20:17:18+00:00 7562655cf4bf28a1ebd6c458334da0c166f34e61 With this commit all tests on py34 tox environment are collected. 
With this commit all tests on py34 tox environment
are collected.
[test] Prepare tests for python3 compatibility 2017-03-17T16:52:56+00:00 efkin efkin@riseup.net 2017-03-13T19:20:19+00:00 ba3fcb08eafd389bdbf0ab9c59577a25c8d8126d 






[test] Prepare new tox environment
2017-03-17T16:52:55+00:00

efkin
efkin@riseup.net

2017-03-13T18:28:11+00:00

1034d3107b57f03d7ed2257aef39cede2f6686ef

At this point tests are not yet collectable
in the new environment. But no regressions observed.





At this point tests are not yet collectable
in the new environment. But no regressions observed.







[docs] Define in details the testing environment
2017-03-17T16:52:54+00:00

efkin
efkin@riseup.net

2017-03-13T18:23:08+00:00

5cf77ccd4df00a59c8cb8d4670f2964f021ae862

On debian stable the `python3-tox` and `python-tox` packages
come with a really old version of `pip` and `setup_tools`.
This makes unusable PEP496 that comes handy when dependencies
are "py-version-related".
As a workaround we can "inject" an upgraded version of `pip` just
before running `tox`.





On debian stable the `python3-tox` and `python-tox` packages
come with a really old version of `pip` and `setup_tools`.
This makes unusable PEP496 that comes handy when dependencies
are "py-version-related".
As a workaround we can "inject" an upgraded version of `pip` just
before running `tox`.







[bug] secrets version defaults to v1
2017-03-09T22:25:37+00:00

Tulio Casagrande
tcasagra@thoughtworks.com

2017-03-09T22:25:37+00:00

e779ecd3be6bfe45f2bd082e890e1c600785e676












[bug] add default version when decrypting secrets
2017-03-09T20:28:22+00:00

Tulio Casagrande
tcasagra@thoughtworks.com

2017-03-09T20:28:22+00:00

c1966cd7cfa27445f2a09501709dc66a18d79058

Resolves: https://0xacab.org/leap/soledad/issues/8788





Resolves: https://0xacab.org/leap/soledad/issues/8788







[test] add comments explaining behaviour of upload/download benchmark
2017-03-02T21:54:32+00:00

drebs
drebs@leap.se

2017-03-02T18:47:04+00:00

32c6d2eae998ceec302995e52c70a0636ca1e463












[test] improve twistd startup and termination
2017-03-02T21:54:32+00:00

drebs
drebs@leap.se

2017-03-02T00:02:41+00:00

32c950d16e7bea55bb7af3f4650af857be9027e0

- use subprocess.check_call() to ensure any errors during twistd startup
  will properly show up on test reports.

- use SIGTERM instead of SIGKILL to gracefully terminate twistd.





- use subprocess.check_call() to ensure any errors during twistd startup
  will properly show up on test reports.

- use SIGTERM instead of SIGKILL to gracefully terminate twistd.







[test] mark benchmark tests using their group names
2017-03-02T21:54:32+00:00

drebs
drebs@leap.se

2017-03-01T16:39:04+00:00

6deadf8adeb8c6b4a98e2d69e2bf3b1447a6b4ca












[test] bugfix: actually use an empty local db in download benchmarks
2017-03-02T21:54:32+00:00

drebs
drebs@leap.se

2017-02-28T13:22:06+00:00

5af57250f2b1cd174fa75c559bac6ea179c43d09

We were previously not using an empty local db for download benchmark
tests, so there was actually nothing to sync. This commit fixes that by
adding a way to force an empty local db on soledad client instantiation.





We were previously not using an empty local db for download benchmark
tests, so there was actually nothing to sync. This commit fixes that by
adding a way to force an empty local db on soledad client instantiation.