nextcloud-desktop/csync/tests/ownCloud
2014-04-08 12:39:46 +02:00
..
ownCloud Allow tests to run against SSL-self-signed servers 2014-04-08 12:39:46 +02:00
testfiles
toremote1
exclude.cfg
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 Add a new test script to check for big file chunking. 2014-04-04 16:33:57 +02:00
t2.pl Add missing license headers in tests 2014-02-24 11:08:58 +01:00
t3.pl Add missing license headers in tests 2014-02-24 11:08:58 +01: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 Minor cleanup 2014-04-01 16:14:24 +02:00
t6.pl Fix info print in test script. 2014-04-07 16:36:35 +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.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>