Soumis par Anonymous le
Test Case obm-16: User A deletes 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 delete the event and wants to warn the organizer. |
||
Preconditions:
|
||
#: | 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 |
User B opens miniG or TBird |
Check that an email has been received notifying that User A has refused to be part of the event |
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:
|
||
#: | 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 |
Test Case obm-42: UserPDA receives a new event, a modified event and a cancelled event from an internal OBM user | ||
---|---|---|
Summary:
UserPDA receives a new event created by an OBM internal 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:
|
||
#: | 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 |