nextcloud-desktop/csync/tests/ownCloud
Markus Goetz 22c1629dd3 SyncEngine: Keep csync_journal with proper values for fileId and remotePerm
Before this patch, we had a lot of empty rows because we created
the SyncFileItems with the wrong(=local) data.
2014-08-07 10:14:14 +02:00
..
ownCloud Allow tests to run against SSL-self-signed servers 2014-04-08 12:39:46 +02:00
testfiles Move csync in order to merge it with mirall 2014-01-13 14:39:50 +01:00
toremote1 Removed another file for Jenkins. 2014-04-23 13:22:06 +02:00
exclude.cfg Move csync in order to merge it with mirall 2014-01-13 14:39:50 +01:00
README Enable SSL for testing. 2014-04-01 16:14:24 +02:00
t1.cfg.in Added t5.pl which does basic testing with a Shared directory. 2014-03-28 15:04:14 +01:00
t1.pl test fles with '%' and '#' 2014-06-03 17:27:06 +02:00
t2.pl propagator: Fix folder duplication if the folder is renamed on the server while uploading 2014-06-24 12:00:13 +02:00
t3.pl test fles with '%' and '#' 2014-06-03 17:27:06 +02:00
t4.pl Make sure we do not remove files that are replaced by a symlink 2014-04-03 17:47:49 +02:00
t5.pl Add t7.pl Test for operation of files with restrictions 2014-06-27 11:22:53 +02:00
t6.pl Fix info print in test script. 2014-04-07 16:36:35 +02:00
t7.pl SyncEngine: Keep csync_journal with proper values for fileId and remotePerm 2014-08-07 10:14:14 +02:00
testfiles.tar.xz Move csync in order to merge it with mirall 2014-01-13 14:39:50 +01:00

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.46 at least. Many distros deliver older versions.
A working version is part of the github checkout.

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

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.

Second, unpack the test file collection with 
tar xf testfiles.tar.xz
in the directory where the tarball can be found.

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>