| Thread Previous • Date Previous • Date Next • Thread Next |
Hi Nils, Great to see another active contributor! On 06/05/17 21:54, nils wrote:
Great, Thanks! If you find a minute, I would appreciate if you could throw an eye on lp:~dernils/duplicity/robust-dropbox-backend, specifically the one test that I created under testing/backend-testing. What I’m trying to do here is that I build the tests for the backends in an empty folder by re-using elements from the other tests. This allows me to keep focussed but (more important) to completely oversee the codebase and learn from scratch. Unfortunately, the very simple test case that I created for a ftp backend stucks in execution. I’m currently only trying to take a very simple test and use the ftp server that I set up using docker as a backend. I debugged it so far that the duplicity command seems to get called by the run_duplicity function but there is no output from the execution of the function at all. The tests in the other folders still execute fine.
Did you mean: https://code.launchpad.net/~dernils/duplicity/backend-testing? Your robust-dropbox-backed branch was last modified last year. Have you managed to fix this yourself (the last commit to your backend-testing branch has a message of "working")? I'm struggling to find your ftp test.
I know that this is a work in progress, but you are currently copying a lot of code from the functional tests __init__.py into a second __init__.py (run_duplicity etc) rather than using the existing versions. I would prefer to see any functional backend tests sit in the existing functional folder (or a subfolder of it) and use the existing functional test __init__. Same with any backend unit tests.
Please feel free to ask any further questions. I do a fair bit on the testing side, so will help where I can.
Kind regards, Aaron
| Thread Previous • Date Previous • Date Next • Thread Next |
