In blue = ACTION
In green = VERIFICATION

Functional Tests

Switching views

• Script file: TestSwitchingViews.py
• Report file name : TestSwitchingViews.log
• Scenario :
  (remarks : All the view switchs are made by emulation of mouse click on the corresponding 'application bar' button.
  Verification of the button sate is include in the switch method.)
  1. Switch to All view
  2. Switch to Tasks view
  3. Switch to Mail view
  4. Switch to Cal view

Item stamping

• Script file: TestStamping.py
• Report file name : TestStamping.log
• Scenario description :
  (remarks : All stamping are made by emulation of mouse click on the corresponding 'markup bar' button.)
  1. Create a new note
  2. Stamp the note as a mail
  3. Check the note state in the DV
  4. Stamp the note as a task
  5. Check the note state in the DV
  6. Stamp the note as an event
  7. Check the note state in the DV
  8. Remove all stamps
  9. Check the note state in the DV

New Event creation

• Script file: TestNewEvent.py
• Report file name : TestNewEvent.log
• Scenario description :
  
  1. Create a new event
  2. Set event attributes in the DV (emulate UI user actions)
  3. Check the event state in the DV

New Task creation

• Script file: TestNewTask.py
• Report file name : TestNewTask.log
• Scenario description :
  
  1. Create a new task
  2. Set task attributes in the DV (emulate UI user actions)
  3. Check the task state in the DV

New Note creation

• Script file: TestNewNote.py
• Report file name : TestNewNote.log
• Scenario description :
  
  1. Create a new note
  2. Set note attributes in the DV (emulate UI user actions)
  3. Check the note state in the DV

New mail creation

• Requirements : IMAP/SMTP accounts (with OSAF certificates for OSAF accounts)
• Script file: TestNewMail.py
• Report file name : TestNewMail.log
• Scenario description :
  
  1. Create a new mail
  2. Set mail attributes in the DV (emulate UI user actions)
  3. Send the mail (emulate UI user actions) + Verification
  4. Check the mail state in the DV

Calendar importing

• Script file: TestImporting.py
• Report file name : TestImporting.log
• Scenario :
  1. Import a importTest.ics calendar into chandler
  2. Check if the expected items are present in the repository

Calendar exporting

• Script file: TestExporting.py
• Report file name : TestExporting.log
• Scenario :
  1. Export all the events in exportTest.ics

Creating a new calendar

• Script file: TestNewCollection.py
• Report file name : TestNewCollection.log
• Scenario :
  1. Create a new collection
  2. Set the title of the collection to "Meeting" (emulate UI user actions)
  3. Check if the expected collection exists in the sidebar
  4. Create a new note
  5. Put the created note in the created collection

Accounts setting

• Script file: TestCreateAccounts.py
• Report file name : TestCreateAccounts.log
• Scenario :
  (remarks : all accounts settings are made by UI user action emulation and the created accounts
  correspond to QA accounts)
  1. Open the Accounts dialog window
  2. Create/set a new SMTP account named 'Personnal SMTP'
  3. Create/set a new IMAP account named 'Personnal IMAP'
  4. Create/set a new POP account named 'Personnal POP'
  5. Create/set a new WebDAV account named 'Personnal WebDAV'
  6. Check the accounts settings

Subscribe to a calendar

• Requirements : importTest.ics published on the qacosmo server
• Script file: TestSubscribe.py
• Report file name : TestSubscribe.log
• Scenario :
  1. Create/set a new WebDAV account named 'Subscribe Test WebDAV'
  2. Subscribe to "webcal://qacosmo.osafoundation.org:8080/home/demo1/importTest.ics"

Sharing

• Script file: TestSharing.py
• Report file name : TestSharing.log
• Scenario :
  1. Create/set a new WebDAV account named 'Sharing Test WebDAV'
  2. Share the 'All' collection

Move to Trash

• Script file: TestMoveToTrash.py
• Report file name : TestMoveToTrash.log
• Scenario :
  1. Create a new Note
  2. Set title and body of this Note
  3. Move this Note in the Trash
  4. Check if this Note is in the Trash collection
  5. Check if this Note doesn't exist in the All collection

Collection Delete

• Script file: TestDeleteCollection.py
• Report file name : TestDeleteCollection.log
• Scenario :
  1. Create a new Collection
  2. Delete this Collection
  3. Check if this Collection doesn't exist in the All collection

Performance Tests

Here the description of the scripts corresponding to the Performance Project Primary 0.6 Use cases

Event Creation (file-menu)

• Script file: PerfNewEventFileMenu.py
• Report file name : PerfNewEventFileMenu.log
• Scenario :
  1. Create a new event from the file menu while being in the calendar view.
  2. Verify the creation of the event in the detail view

Event Creation (in-place)

• Script file: PerfNewEventCalView.py
• Report file name : PerfNewEventCalView.log
• Scenario :
  1. Create a new event by double clicking in the calendar view.
  2. Verify the creation of the new event in the detail view

New Calendar Creation

• Script file: PerfNewCalendar.py
• Report file name : PerfNewCalendar.log
• Scenario :
  1. Create a new calendar in the sidebar by using the File menu -> New Collection option.
  2. Verify the collection exists in the sidebar

Switch view

• Script file: PerfSwitchToAllView.py
• Report file name :!PerfSwitchToAllView.log
• Scenario :
  1. Swich to All view from the default calendar view.

Stamping

• Script file: PerfStampEvent.py
• Report file name : PerfStampEvent.log
• Scenario :
  1. Create a new note and stamp it as an event in the detail view.
  2. Verify the note is stamped in the detail view

Importing a 3000 items calendar

• Script file: PerfImportCalendar.py
• Report file name : PerfImportCalendar.log
• Scenario :
  1. Import a 3000 event calendar into Chandler.
  2. Check for 4 of the events from the calendar in Chandler