mirror of
https://gitlab.com/davical-project/davical.git
synced 2026-01-27 00:33:34 +00:00
This allows us to have more complex test files where an action is taken, then we test something, then another action is taken, etc. Changes to test files are required so that URL is defined after all the required settings are set. Changes to the result files are either whitespace changes due to above logic changes, or printing out a SQL Result header before each result. I figured it was useful.
39 lines
1.2 KiB
Plaintext
39 lines
1.2 KiB
Plaintext
1..16
|
|
# Subtest: Login
|
|
1..4
|
|
ok 1 - Fetch first page
|
|
ok 2 - Not logged in
|
|
ok 3 - Login to site
|
|
ok 4 - Logged in
|
|
ok 1 - Login
|
|
ok 2 - Create collection - 0
|
|
ok 3 - Collection created message displayed - 0
|
|
ok 4 - Create collection - 1
|
|
ok 5 - Collection created message displayed - 1
|
|
ok 6 - Create collection - 2
|
|
ok 7 - Collection created message displayed - 2
|
|
ok 8 - New collection exists - 0
|
|
ok 9 - New collection exists - 1
|
|
ok 10 - New collection exists - 2
|
|
ok 11 # skip Database error thrown see #319
|
|
ok 12 # skip Database error thrown see #319
|
|
ok 13 - Collection deleted message displayed
|
|
# Subtest: Login as user1
|
|
1..4
|
|
ok 1 - Fetch first page
|
|
ok 2 - Not logged in
|
|
ok 3 - Login to site
|
|
ok 4 - Logged in
|
|
ok 14 - Login as user1
|
|
ok 15 - Collection deletion error displayed when specifying other principal and their collection
|
|
ok 16 - Collection deletion error display when specifying our principal and their collection
|
|
SQL Query 1 Result:
|
|
dav_displayname: >Test Collection 1<
|
|
dav_name: >/user2/test_collection_1/<
|
|
user_no: >11<
|
|
|
|
dav_displayname: >Test Collection 2<
|
|
dav_name: >/user2/test_collection_2/<
|
|
user_no: >11<
|
|
|