nextcloud-desktop/tests/ownCloud
2013-05-16 16:12:27 +02:00
..
HTTP More blackbox testing of csync ownCloud - enhanced test script. 2012-08-23 17:57:04 +03:00
mocka Add owncloud module files to build. 2013-05-09 13:26:28 +02:00
ownCloud Rather use eq and ne for string comparison. 2013-05-16 16:12:27 +02:00
testfiles Testfile added. 2013-04-26 17:41:55 +02:00
tolocal1 tests: Added test script to test the ownCloud module of csync. 2012-04-17 10:40:21 +02:00
toremote1 Normalized UTF-8 and createLocalFile added. 2013-05-14 17:46:35 +02:00
CMakeLists.txt Added mocka tests for the ownCloud module. 2012-07-09 14:16:20 +02:00
exclude.cfg Reworked integration test: File assert traversal fixed. 2013-05-09 13:26:28 +02:00
mockatest.cfg.in added test data as well as a test config template. 2012-08-29 15:26:31 +03:00
README Dependency info added. 2013-05-14 16:32:36 +02:00
t1.pl Pulled Test.pm out of t1.pl for reuse. Simplified t1.pl. 2013-05-15 11:15:50 +02:00
t3.pl t3.pl: test renaming folder 2013-05-15 17:59:13 +02:00

t1 - a 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.
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, open it in an editor and 
edit the values for the owncloud-url and the credentials. Yeah,
this test script is not secure, make sure to run it with a weak
account and in a save environment.

Further down, in sub csync, you can configure the LD_LIBRARY_PATH
and the binary for csync. That allows to adopt the test script to
local development environments. Make sure to check these.

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>