OPush calendar tests

 

 

Test Case obm-41: UserPDA creates, modifies and cancel an event with attendees with a Smartphone
Summary:

UserPDA creates a new event with attendees, an internal OBM user UserB and an external user extA. After all synchronizations and notifications received, he modifies it. After all synchronizations and notifications, he cancels the event.

Preconditions:
  • UserB is an OBM user using Thunderbird with OBM Connector
  • ExtA is an external user using Outlook in an exchange architecture
  • UserPDA is an OBM User using a PDA
  • Synchronization configuration (with Exchange or proprietary software...) is made on the PDA, using Pull option (or a synchronization every 1 minute)
#: Step actions: Expected Results:
1

In the PDA calendar, UserPDA creates a new event "EVENT PDA" with UserB and ExtB as attendees, located in LYON with a small description "Event created with <PDA name>"

 
2

UserPDA wait for a synchronization of the PDA

 
3

In OBM/UI, UserB opens the waiting event window

Check that a new waiting event "EVENT PDA" appears in the list

4

UserB accepts the event by clicking accept

 
5

UserB opens the event "EVENT PDA"

Checks that the location is "LYON" and the description "Event created with <PDA name>"

6

ExtA opens the email in Oulook, accepts the event and sends notifications

 
7    
8

With the PDA, UserPDA checks emails

Check that he receives 2 new emails of notification

9

UserPDA opens the calendar on the PDA

Check that the status of UserB and ExtA are "Accepted" in "EVENT PDA"

10

UserPDA modifies the date/time of the event "EVENT PDA" and saves it

 
11

UserPDA waits for a synchronization of the PDA

 
12

In OBM/UI, UserB opens the waiting event window

 Check that an event "EVENT PDA" appears in the list with the new date/time of the event

13

UserB declines the event by clicking decline

Check that the event "EVENT PDA" has disappeared of the OBM/UI calendar of UserB

14

ExtA opens the email in Outlook and declines the event

 
15

UserPDA receives new emails of notification

 Check that one message talks about the refuse of UserB to attend "EVENT PDA" and the other one of ExtA

16

UserPDA modifies again the date/time of the event "EVENT PDA" and save it on the PDA

 
17

 UserPDA waits for a synchronization of the PDA

 
18

In OBM/UI, UserB accepts the waiting event

Check that the event "EVENT PDA" reappears in UserB calendar

19

ExtA opens the email in Outlook and accept the event

 
20

UserPDA receives 2 new emails of notification and opens the event "EVENT PDA" in the calendar

Check that the status of UserB and ExtA are 'Accepted" in "EVENT PDA"

21

UserPDA deletes the event "EVENT PDA" in the PDA calendar and notifies attendees

Check that the event has disappeared in the calendar

22

UserPDA waits for a synchronization of the PDA

 
23

In OBM/UI, UserB opens the calendar

Check that the event has disappeared in the Calendar

25

In Outlook, ExtA receives one email for the cancellation of the event "EVENT PDA"

See that the event has disappeared in the Outlook calendar

Execution type: Manual
 

 

Test Case obm-127: UserPDA creates a new not allday recurrent event
Summary:

 Create a new not allday yearly, monthly and daily recurrent event with and without end date. Check what is added in the obm database

#: Step actions: Expected Results:
1

On the smartphone create a new yearly event during 1 hour, with an end date and add UserB as an attendee. Synchronize

 Check that the event is correctly created and the invitation received by attendee

2

 On the smartphone create a new monthly event during 1 hour with an end date and add UserB as an attendee. Synchronize

 Check that the event is correctly created and the invitation received by attendee

3

 On the smartphone create a new weekly event during 1 hours with an end date and add UserB as an attendee. Synchronize

 Check that the event is correctly created and the invitation received by attendee

4

 On the smartphone create a new daily event with an end date and add UserB as an attendee. Synchronize

 Check that the event is correctly created and the invitation received by attendee

5

 Repeat the 4 previous steps with recurrent events without end date

 
6    
Execution type: Manual
 

 

Test Case obm-176: UserPDA creates a new allday recurrent event
Summary:

 Create a new allday yearly, monthly, weekly and daily recurrent event with and without end date. Check what is added in the obm database

#: Step actions: Expected Results:
1

On the smartphone create a new allday and yearly event with an end date and add UserB as an attendee. Synchronize

 Check that the event is correctly created and the invitation received by attendee

2

On the smartphone create a new allday and weekly event with an end date and add UserB as an attendee. Synchronize

 Check that the event is correctly created and the invitation received by attendee

3

On the smartphone create a new allday and monthly by date event with an end date and add UserB as an attendee. Synchronize

 Check that the event is correctly created and the invitation received by attendee

4

 On the smartphone create a new allday and daily event with an end date and add UserB as an attendee. Synchronize

 Check that the event is correctly created and the invitation received by attendee

5

 Repeat the 4 previous steps with an event without end date

 
6    
Execution type: Manual
 

 

Test Case obm-179: UserPDA receives a new, a modified and a cancelled simple event from an internal OBM user
Summary:

UserPDA receives a new simple event created by another OBM user. He accepts then receives a modification for the event, he refuses then receives a modification and accepts. The he receives a cancellation notification for this event.

Preconditions:
  • userB is an OBM user using TBird and obm-ui
  • UserPDA is an OBM User using a PDA
  • Synchronization configuration (with Exchange or proprietary software...) is made on the PDA, using Pull option (or a synchronization every 1 minute)
#: Step actions: Expected Results:
1

Using TBird/lightning, UserB creates a new event "EVENT TB" with UserPDA as an attendee, located in LYON with a small description "Event created for test on a PDA"

 
2

UserB accepts to notify and synchronizes with TBird

 
3

UserPDA checks his emails on the PDA

Verify that a new email for the new event "EVENT TB" is in INBOX

If you use an Iphone verify also that a new meeting request is added in the calendar corresponding to the "EVENT TB"

4

UserPDA accepts the new event "EVENT TB" with the button "Accept"

Check that the event "EVENT TB" appears in the Calendar on the PDA with the correct location LYON and the description

5

UserPDA waits for a synchronization of PDA

Check that UserB receives a notification by email for the answer of UserPDA

6

UserB modifies the date/time of the event "EVENT TB" in TBird and synchronizes

 
7

UserPDA waits for a synchronization

 
8

UserPDA checks his emails on the PDA

Verify that a new email for the update of "EVENT TB" is in INBOX

9

UserPDA declines the new date of meeting

Check that the event has disappeared in the Calendar

10

UserPDA waits for a synchronization

Check that UserB receives a notification by email for the answer of UserPDA. Check that it is a rejection

11

UserB modifies the date/time of the event again in TBird

 
12

UserPDA waits for a synchronization

 
13

UserPDA checks his emails on the PDA

Verify that a new email for the update of "EVENT TB" is in INBOX

14

UserPDA accepts the new date/time of "EVENT TB"

Check that the event "EVENT TB" appears in the Calendar and that the content is correct (Location=Lyon, Description="Event created for test on a PDA")

15

UserB deletes the event in TBird, notifies attendees and synchronizes

 
16

UserPDA waits for a synchronization

 
17

UserPDA checks his emails on the PDA

Verify that the email contains a cancellation for the event "EVENT TB"

18

UserPDA opens the calendar on the PDA

Check that the event "EVENT TB" has disappeared in the Calendar

Execution type: Manual
 

 

Test Case obm-42: UserPDA receives a new, a modified and a cancelled simple event from an external user
Summary:

UserPDA receives a new simple event created by an external user. He accepts then receives a modification for the event, he refuses then receives a modification and accepts. Then he receives a cancellation notification for this event.

Preconditions:
  • extB is an external non-OBM user
  • UserPDA is an OBM User using a PDA
  • Synchronization configuration (with Exchange or proprietary software...) is made on the PDA, using Pull option (or a synchronization every 1 minute)
#: Step actions: Expected Results:
1

extB creates a new event "EVENT ext" with UserPDA as an attendee, located in LYON with a small description "Event created for test on a PDA". Notify, send invitation

 
3

UserPDA checks his emails on the PDA

Verify that a new email for the new event "EVENT ext" is in INBOX

If you use an Iphone verify also that a new meeting request is added in the calendar corresponding to the "EVENT ext"

4

UserPDA accepts the new event "EVENT ext" with the button "Accept"

Check that the event "EVENT ext" appears in the Calendar on the PDA with the correct location LYON and the description

5

UserPDA waits for a synchronization of PDA

Check that extB receives a notification by email for the answer of UserPDA

6

extB modifies the date/time of the event "EVENT ext"  and synchronizes

 
7

UserPDA waits for a synchronization

 
8

UserPDA checks his emails on the PDA

Verify that a new email for the update of "EVENT ext" is in INBOX

9

UserPDA declines the new date of meeting

Check that the event has disappeared in the Calendar

10

UserPDA waits for a synchronization

Check that extB receives a notification by email for the answer of UserPDA. Check that it is a rejection

11

extB modifies the date/time of the event again

 
12

UserPDA waits for a synchronization

 
13

UserPDA checks his emails on the PDA

Verify that a new email for the update of "EVENT ext" is in INBOX

14

UserPDA accepts the new date/time of "EVENT ext"

Check that the event "EVENT ext" appears in the Calendar and that the content is correct (Location=Lyon, Description="Event created for test on a PDA")

15

extB deletes the event, notifies attendees and synchronizes

 
16

UserPDA waits for a synchronization

 
17

UserPDA checks his emails on the PDA

Verify that the email contains a cancellation for the event "EVENT ext"

18

UserPDA opens the calendar on the PDA

Check that the event "EVENT ext" has disappeared in the Calendar

Execution type: Manual
 

 

Test Case obm-178: UserPDA receives a new, a modified and a cancelled recurrent event from an internal OBM user
Summary:

UserPDA receives a new recurrent event created by an OBM internal user. He accepts then receives a moved exception for the event, he refuses then receives a modification and accepts. Then he receives a cancellation notification for the all event

Preconditions:
  • UserB is an OBM user using Thunderbird with OBM Connector
  • UserPDA is an OBM User using a PDA
  • Synchronization configuration (with Exchange or proprietary software...) is made on the PDA, using Pull option (or a synchronization every 1 minute)
#: Step actions: Expected Results:
1

Using TBird/lightning, UserB creates a new daily event "Recurrent EVENT TB" with UserPDA as an attendee, located in LYON with a small description "Event created for test on a PDA"

 
2

UserB accepts to notify and synchronizes with TBird

 
3

UserPDA checks his emails on the PDA

Verify that a new email for the new event "Recurrent EVENT TB" is in INBOX

If you use an Iphone verify also that a new meeting request is added in the calendar corresponding to the "Recurrent EVENT TB"

4

UserPDA accepts the new event "Recurrent EVENT TB" with the button "Accept"

Check that the event "Recurrent EVENT TB" appears in the Calendar on the PDA with the correct location LYON and the description

5

UserPDA waits for a synchronization of PDA

Check that UserB receives a notification by email for the answer of UserPDA

6

UserB modifies the date/time of an occurence the event "recurrent EVENT TB" in TBird and synchronizes (by drag'n'drop)

 
7

UserPDA waits for a synchronization

 
8

UserPDA checks his emails on the PDA

Verify that a new email for the update of "Recurrent EVENT TB" is in INBOX

9

UserPDA declines the moved exception

Check that the moved exception has disappeared in the Calendar

10

UserPDA waits for a synchronization

Check that UserB receives a notification by email for the answer of UserPDA. Check that it is a rejection

11

UserB modifies the date/time of the moved exception again in TBird

 
12

UserPDA waits for a synchronization

 
13

UserPDA checks his emails on the PDA

Verify that a new email for the update of "Recurrent EVENT TB" is in INBOX

14

UserPDA accepts the new date/time of "Recurrent EVENT TB"

Check that the event "Recurrent EVENT TB" appears in the Calendar and that the content is correct (Location=Lyon, Description="Event created for test on a PDA")

15

UserB deletes the event in TBird, notifies attendees and synchronizes

 
16

UserPDA waits for a synchronization

 
17

UserPDA checks his emails on the PDA

Verify that the email contains a cancellation for the event "Recurrent EVENT TB"

18

UserPDA opens the calendar on the PDA

Check that the event "Recurrent EVENT TB" has disappeared in the Calendar

Execution type: Manual
 

 

Test Case obm-180: UserPDA receives a new, a modified and a cancelled recurrent event from an external user
Summary:

UserPDA receives a new recurrent event created by an external non-OBM user. He accepts then receives a moved exception for the event, he refuses then receives a modification and accepts. Then he receives a cancellation notification for the all event

Preconditions:
  • extB is an external user not using OBM
  • UserPDA is an OBM User using a PDA
  • Synchronization configuration (with Exchange or proprietary software...) is made on the PDA, using Pull option (or a synchronization every 1 minute)
#: Step actions: Expected Results:
1

extB creates a new daily event "Recurrent EVENT ext" with UserPDA as an attendee, located in LYON with a small description "Event created for test on a PDA"; Notify, synchronize

 
3

UserPDA checks his emails on the PDA

Verify that a new email for the new event "Recurrent EVENT ext" is in INBOX

If you use an Iphone, verify also that a new meeting request is added in the calendar corresponding to the "Recurrent EVENT ext"

4

UserPDA accepts the new event "Recurrent EVENT ext" with the button "Accept"

Check that the event "Recurrent EVENT ext" appears in the Calendar on the PDA with the correct location LYON and the description

5

UserPDA waits for a synchronization of PDA

Check that extB receives a notification by email for the answer of UserPDA

6

extB modifies the date/time of an occurence (moved occurence) of the event "recurrent EVENT ext" and synchronizes

 
8

UserPDA checks his emails on the PDA

Verify that a new email for the update of "Recurrent EVENT ext" is in INBOX

9

UserPDA declines the moved exception

Check that the moved exception has disappeared in the Calendar

10

UserPDA waits for a synchronization

Check that extB receives a notification by email for the answer of UserPDA. Check that it is a rejection

11

extB modifies the date/time of the moved exception again

 
12

UserPDA waits for a synchronization

 
13

UserPDA checks his emails on the PDA

Verify that a new email for the update of "Recurrent EVENT extB" is in INBOX

14

UserPDA accepts the new date/time of "Recurrent EVENT extB"

Check that the event "Recurrent EVENT extB" appears in the Calendar and that the content is correct (Location=Lyon, Description="Event created for test on a PDA")

15

extB deletes the event in TBird, notifies attendees and synchronizes

 
16

UserPDA waits for a synchronization

 
17

UserPDA checks his emails on the PDA

Verify that the email contains a cancellation for the event "Recurrent EVENT extB"

18

UserPDA opens the calendar on the PDA

Check that the event "Recurrent EVENT extB" has disappeared in the Calendar

Execution type: Manual
 

 

Test Case obm-181: User A change participation of an event organized by someone else on a Smartphone
Summary:

User A is invited to an event, has accepted it, but User A decides to change its participation to the event and wants to warn the organizer.

Preconditions:
  • User A has been invited to an event by User B and has already accepted it
#: Step actions: Expected Results:
1

On its Smartphone, User A opens the event

 
2

User A change the participation to Decline

 
3

User A decides to send a mail to organizer

Check that the event has disappear in the calendar of the smartphone, and that a mail has been sent

4

User B opens UI and check User A to that event

Check that User A has refused the invitation

5

User B opens TBird or Roundcube

 Check that an email has been received notifying that User A has refused to be part of the event

Execution type: Manual
 

 

 

Test Case obm-182: User A deletes an event organized by external user on a Smartphone
Summary:

User A is invited to an event by an external non*OBM user, has accepted it, but User A decides to delete the event and wants to warn the organizer.

Preconditions:
  • User A has been invited to an event by extB (external user) and has already accepted it
#: Step actions: Expected Results:
1

On its Smartphone, User A opens the event to delete

 
2

User A Deletes the event

 
3

User A decides to send a mail to organizer

Check that the event has disappear and that a mail has been sent

5

User B opens emails

 Check that an email has been received notifying that User A has refused to be part of the event

Execution type: Manual
 

 

 

Test Case obm-16: User A deletes an event organized by another OBM User on a Smartphone
Summary:

User A is invited to an event by another OBM user, has accepted it, but User A decides to delete the event and wants to warn the organizer.

Preconditions:
  • User A has been invited to an event by another OBM user and has already accepted it
#: Step actions: Expected Results:
1

On its Smartphone, User A opens the event to delete

 
2

User A Deletes the event

 
3

User A decides to send a mail to organizer

Check that the event has disappear and that a mail has been sent

4

User B opens UI and check User A to that event

Check that User A has refused the invitation

5

UserB opens emails

 Check that an email has been received notifying that User A has refused to be part of the event

Execution type: Manual
 

 

Prime Hype DF 2016 EP