nextcloud-desktop/tests/ownCloud
2013-10-29 13:47:08 +01:00
..
HTTP tests: Added test data for the owncloud integration test script. 2013-07-23 07:32:01 +02:00
ownCloud Fix t1.pl since the argument of owncloudcmd have changed 2013-10-29 13:47:08 +01:00
testfiles Testfile added. 2013-04-26 17:41:55 +02:00
toremote1 Merge remote-tracking branch 'origin/master' into ocsync 2013-08-18 16:21:18 +02:00
exclude.cfg tests: Added test data for the owncloud integration test script. 2013-07-23 07:32:01 +02:00
README Merge remote-tracking branch 'origin/master' into ocsync 2013-08-18 16:21:18 +02:00
t1.cfg.in tests: Added test data for the owncloud integration test script. 2013-07-23 07:32:01 +02:00
t1.pl tests: Modularize ownCloud's integration test script. 2013-07-23 07:33:32 +02:00
t3.pl Fix cases where the file has been replaced by another with the same mtime 2013-07-23 16:03:50 +02:00
t4.pl Add ignore files that need cleanup 2013-07-29 15:03:25 +02:00
testfiles.tar.xz tests: Package testfiles as xz archive. 2013-08-01 17:08:19 +02: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...

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