Christian Kamm
276985f6c3
Fix perl tests for sync journal db name
|
9 lat temu | |
|---|---|---|
| .. | ||
| ownCloud | 9 lat temu | |
| testfiles | 12 lat temu | |
| toremote1 | 11 lat temu | |
| .gitignore | 11 lat temu | |
| README | 11 lat temu | |
| exclude.cfg | 11 lat temu | |
| t1.cfg.in | 11 lat temu | |
| t1.pl | 9 lat temu | |
| t2.pl | 9 lat temu | |
| t3.pl | 11 lat temu | |
| t4.pl | 10 lat temu | |
| t5.pl | 11 lat temu | |
| t6.pl | 9 lat temu | |
| t7.pl | 9 lat temu | |
| t8.pl | 11 lat temu | |
| t9.pl | 9 lat temu | |
| t_recall.pl | 9 lat temu | |
| testfiles.tar.xz | 12 lat temu | |
README
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
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