r5 - 26 Feb 2008 - 11:38:27 - RandyLetnessYou are here: OSAF >  Journal Web  >  ContributorNotes > RandyLetnessNotes > CosmoZeroPointThirteenTesting
Testing to focus on for 0.13:

1. Publish Items in multiple collections with old client

  1. create user on hub (user1)
  2. publish new collection as user1 with a few items
  3. create another user on hub (user2)
  4. use different Chandler client (profile) and subscribe to collection with read-write ticket
  5. create new collection in 2nd client, add a few items from subscribed collection
  6. publish collection with 2nd client (as user2)

Result: 2nd publish should fail (error will be "collection has already been published") This error message results because the old client interprets a 403 response (forbidden) as meaning that the collection already exists, when in this case the collection doesn't exist, but the request wasn't authorized for an existing item.

2. Update Items in multiple collections with old client

  1. create user on hub (user1)
  2. publish new collection as user1 with a few items
  3. create another user on hub (user2)
  4. use different Chandler client (profile) and publish new collection as user2 with different items
  5. subscribe to collection with read-write ticket using second profile
  6. add a few items from subscribed collection to already published collection using second profile
  7. sync collection (as user2)

Result: Sync should fail.

3. Publish Items in multiple collections with old client same user

  1. create user on hub (user1)
  2. publish new collection as user1 with a few items
  3. create new collection, add a few items from first collection
  4. publish second collection as same user
  5. update an item in the second collection
  6. sync collections

Result: everything should work

4. Publish Items in multiple collections with new client

  1. create user on hub (user1)
  2. publish new collection as user1 with a few items
  3. create another user on hub (user2)
  4. use different Chandler client (profile) and subscribe to collection with read-write ticket
  5. create new collection in 2nd client, add a few items from subscribed collection
  6. publish collection with 2nd client (as user2)

Result: Everything should work.

5. Publish Items in multiple collections multi-level with new client

  1. create user on hub (user1)
  2. publish new collection col1 as user1 with a few items (get RW ticket T1)
  3. create another user on hub (user2)
  4. use different Chandler client (profile) and subscribe to collection with read-write ticket T1
  5. create new collection col2 in 2nd client, add a few items from subscribed collection
  6. publish collection with 2nd client (as user2, get RW ticket T2)
  7. create user on hub (user3)
  8. use different Chandler client (profile), subscribe to col2 using RW ticket T2
  9. create new collection col3 in 3rd client, add items that exist in both col1 and col2 to col3
  10. publish col3 with 3rd client (user3)

Result: Everything should work.

6. Update Items in multiple collections with new client

  1. create user on hub (user1)
  2. publish new collection as user1 with a few items
  3. create another user on hub (user2)
  4. use different Chandler client (profile) and publish new collection as user2 with different items
  5. subscribe to collection with read-write ticket using second profile
  6. add a few items from subscribed collection to already published collection using second profile
  7. sync collection (as user2)
  8. update items that exist in multiple collections (as user2)
  9. sync collection (as user2)

Result: Everything should work

7. Publish Items in multiple collections with new client (fail)

  1. create user on hub (user1)
  2. publish new collection as user1 with a few items
  3. create another user on hub (user2)
  4. use different Chandler client (profile) and subscribe to collection with read-only ticket
  5. create new collection in 2nd client, add a few items from subscribed collection (you may have to unsubscribe first)
  6. publish collection with 2nd client (as user2)

Result: publish should fail because items that were added to 2nd collection did not include a read-write ticket

8. Publish Items in multiple collections with new client, use webui to update 2nd collection

  1. create user on hub (user1)
  2. publish new collection as user1 with a few items
  3. create another user on hub (user2)
  4. use different Chandler client (profile) and subscribe to collection with read-only ticket
  5. create new collection in 2nd client, add a few items from subscribed collection
  6. publish collection with 2nd client (as user2)
  7. login to webui as user2 and update item that was added from use1's collection to user2's collection

Result: update should succeed

9. Base Security Check old client and new client

  1. create user on hub (user1)
  2. publish new collection as user1 with a few items
  3. create another user on hub (user2)
  4. use different Chandler client (profile) and subscribe to collection (minus the ticket, using user2's credentials when prompted)

Result: subscribe should fail because user2 is not authorized for user1's collection

10. CalDAV security check I

  1. create user on hub (user1)
  2. publish new collection as user1 with a few items
  3. create another user on hub (user2)
  4. login to hub as user1, get dav address for published collection
  5. attempt to access shared collection with user2's credentials

Results: should fail

11. CalDAV security check II

  1. create user on hub (user1)
  2. publish new collection as user1 with a few items
  3. create another user on hub (user2)
  4. login to hub as user1, get dav address for published collection
  5. attempt to access shared collection with user1's credentials

Results: should succeed

12. webcal security check I

  1. create user on hub (user1)
  2. publish new collection as user1 with a few items
  3. create another user on hub (user2)
  4. login to hub as user1, get webcal address for published collection
  5. attempt to access shared collection using webcal address with user2's credentials

Results: should fail

13. webcal security check II

  1. create user on hub (user1)
  2. publish new collection as user1 with a few items
  3. create another user on hub (user2)
  4. login to hub as user1, get dav address for published collection i. attempt to access shared collection using webcal address with user1's credentials

Results: should succeed

14. Attempt to hi-jack items using read-only ticket using old and new desktop client

  1. create user on hub (user1)
  2. publish new collection as user1 with a few items
  3. create another user on hub (user2)
  4. use different Chandler client (profile) and subscribe to collection with read-only ticket
  5. after subscribing read-only, do an "unsubscribe"
  6. create new collection in 2nd client, add a few items from subscribed collection
  7. publish collection with 2nd client (as user2)

Result: 2nd publish should fail (error will be "collection has already been published") This error message results because the old client interprets a 403 response (forbidden) as meaning that the collection already exists, when in this case the collection doesn't exist, but the request wasn't authorized for an existing item.

-- RandyLetness - 25 Feb 2008

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r5 < r4 < r3 < r2 < r1 | More topic actions
 
Open Source Applications Foundation
Except where otherwise noted, this site and its content are licensed by OSAF under an Creative Commons License, Attribution Only 3.0.
See list of page contributors for attributions.