nextcloud-desktop/csync/tests/ownCloud
Olivier Goffart 5a109d9293 Fix t3.pl
The fix in commit 86d8079 made the detection of changes inside
a directory more robust.
As a result, changes are detected inside a directory, even if the
files that are changed were moved away on the other remote, the algorithm
won't let the directory be removed and the directory will be re-created
2014-10-21 12:10:12 +02:00
..
ownCloud tx.pl: Fix sharing api url, some whitespace fixes. 2014-10-15 13:28:53 +02:00
testfiles
toremote1
.gitignore CSync tests: Add t1.cfg to gitignore. 2014-09-19 14:21:14 +02:00
exclude.cfg t4.pl: add a test to test that ignored file are not deleted 2014-08-28 19:33:52 +02:00
README Doc: Update csync test script README. 2014-09-17 16:18:55 +02:00
t1.cfg.in t1.cfg.in: saner placeholder executable name 2014-09-17 14:39:34 +02:00
t1.pl Reconcile: Make sure not to loose new files added in a directory removed on the server 2014-10-21 10:38:21 +02:00
t2.pl Tests: Get rid of the Carp package that ogoffart does not have. 2014-08-28 18:10:53 +02:00
t3.pl Fix t3.pl 2014-10-21 12:10:12 +02:00
t4.pl t4.pl: add a test to test that ignored file are not deleted 2014-08-28 19:33:52 +02:00
t5.pl Tests: Get rid of the Carp package that ogoffart does not have. 2014-08-28 18:10:53 +02:00
t6.pl tx.pl: Adopt test t6.pl to the new way of handling precondition failed. 2014-10-15 19:25:34 +02:00
t7.pl owncloudcmd: restart the sync if required 2014-09-12 17:23:01 +02:00
t8.pl Propagator: Fix renaming of files and case confflicts 2014-10-17 16:15:03 +02:00
testfiles.tar.xz

t1 - an integration test script for csync syncing to ownCloud.

Note: This test script uses perl HTTP::DAV. This package needs to
be in version 0.47 at least. Many distros deliver older versions.

t1 uses a perl WebDAV client lib to sync to an existing instance of
ownCloud. For that, various files are copied around, synced and the
results are tested through their existance, the filesize and the 
modification times. All tests are asserts, which means that the 
scripts stops if a test fails.

How to call:

First, configure the script. For that, create a file t1.cfg. There
is t1.cfg.in as an example. Yeah, this test script is not secure,
make sure to run it with a weak account and in a save environment.

To start the script, call ./t1.pl on the commandline. A lot of 
output is generated. If the script does not fail, everything works.

Before it actually ends, it takes a four seconds break for you to 
interrupt with Ctrl-C. If you don't do that, it removes all its 
traces...

If SSL should be used, SSL must be available to LWP connections. To
disable host checking for crappy SSL certs, do
export PERL_LWP_SSL_VERIFY_HOSTNAME=0

Have fun,
Klaas Freitag <freitag@owncloud.com>