Apps/Evolution/Interoperability – GNOME Wiki Archive

Component	Category	Test case ID	Summary	Steps	Result
Mailer	Interoperability between evolution and other applications	Interoperability between openoffice and evolution	Opening the compose mail window from openoffice	i) Open an openoffice document, click on a mail-id shown as a hyperlink ii) Open an openoffice document, goto file > send and select a. document as email b. document as pdf attachment c. document as MS_Excel attachment (if doc is spreadsheet) d. document as MS-PPT attachment (if doc is presentation) e. document as MS-DOC attachment (if doc is a text document)	The compose mail window should open-up with the mail-id in the 'to' text-box

<TR>
- <TD HEIGHT=121>
 - Mailer
 </TD> <TD>
 - Interoperability between evolution and other applications
 </TD> <TD>
 - Interoperability between firefox and evolution
 </TD> <TD>
 - Opening the compose mail window from firefox
 </TD> <TD>
 - Open a webpage in firefox. i) Click on a mail id shown as a hyperlink ii) Right-click on the webpage and select 'Send link...' iii) Right-click on a link (not a mail-id) and select 'Send link...'
 </TD> <TD>
 - Compose mail window should open up with i) the mail id in the 'to' text box ii) the URL of the webpage in the body of the mail iii) URL of the link in the body of the mail
 </TD>
</TR> <TR>
- <TD HEIGHT=77>
 - Mailer
 </TD> <TD>
 - Interoperability between evolution and other applications
 </TD> <TD>
 - Interoperability between nautilus and evolution
 </TD> <TD>
 - Opening the compose mail window using nautilus
 </TD> <TD>
 - Select one or more files, right-click and select 'Send to...'
 </TD> <TD>
 - The compose mail window should open-up with the selected files attached
 </TD>
</TR> <TR>
- <TD HEIGHT=136>
 - Mailer
 </TD> <TD>
 - Interoperability between evolution and other applications
 </TD> <TD>
 - Interoperability between nautilus and evolution
 </TD> <TD>
 - Using nautilus to add attachments
 </TD> <TD>
 - Open the compose mail window. Open the attachment bar. Drag-n-drop i) a file into the attachment bar ii) a folder into the attachment bar iii) a folder created by the user into the attachment bar iv) a default folder into the attachment bar v) an icon shown in the panel into the attachment bar
 </TD> <TD>
 - The files should be attached
 </TD>
</TR> <TR>
- <TD HEIGHT=77>
 - Mailer
 </TD> <TD>
 - Groupwise â€“ Evolution
 </TD> <TD>
 - sending mails from groupwise
 </TD> <TD>
 - Mails sent from groupwise in different forms should appear in evolution in the same form
 </TD> <TD>
 - Send a mail from groupwise i) with attachments ii) without attachments iii) in HTML format iv) in plain-text format
 </TD> <TD>
 - Should receive the mail in the same way as it was sent. Should be able to perform any type of operations on the mail.
 </TD>
</TR> <TR>
- <TD HEIGHT=151>
 - Mailer
 </TD> <TD>
 - Groupwise â€“ Evolution
 </TD> <TD>
 - receving mails sent from groupwise in evolution
 </TD> <TD>
 - Mails sent from groupwise and received in evolution should appear in the same format as it was sent and the mails should be accessible
 </TD> <TD>
 - Receive a mail from groupwise. Perform i) open the mail ii) save attachments of the mail iii) Reply to the mail iv) Forward the mail v) Open the attachments vi) Verify the number of attachments and the type of attachments vii) Verify the attachment icon if the mail has an attachment in the message view
 </TD> <TD>
 - The user in evolution should be able to access the messages received from groupwise and perform operations on the message.
 </TD>
</TR> <TR>
- <TD HEIGHT=92>
 - Mailer
 </TD> <TD>
 - Groupwise â€“ Evolution
 </TD> <TD>
 - Sharing a groupwise folder with a user using evolution
 </TD> <TD>
 - A user using the groupwise Win32 client should be able to share a folder with a user using evolution
 </TD> <TD>
 - Share a folder from groupwise mail client i) Create a folder and share it ii) Share an existing folder iii) Share a default folder
 </TD> <TD>
 - The user in evolution should receive a mail regarding the shared folder and if he accepts it, he should be able to access the shared folder and its contents
 </TD>
</TR> <TR>
- <TD HEIGHT=62>
 - Mailer
 </TD> <TD>
 - Groupwise â€“ Evolution
 </TD> <TD>
 - Sharing a groupwise folder with a user using evolution
 </TD> <TD>
 - Delete the shared folder after the user in evolution accepts to share the folder
 </TD> <TD>
 - i) Delete the shared folder from groupwise ii) If the evolution user has enough permissions, delete the shared folder from evolution
 </TD> <TD>
 - The user in evolution should get a message regarding the deletion of the shared folder and 
 </TD>
</TR> <TR>
- <TD HEIGHT=256>
 - Mailer
 </TD> <TD>
 - Groupwise â€“ Evolution
 </TD> <TD>
 - Sharing a groupwise folder with a user using evolution
 </TD> <TD>
 - Giving permissions to the evolution user
 </TD> <TD>
 - Give i) only read permissions ii) only add permissions iii) only edit permissions iv) only delete permissions v) read and add permissions vi) read and edit permissions vii) read and delete permissions viii) add and edit permissions ix) add and delete permissions x) edit and delete permissions xi) all the permissions xii) no permissions xiii) read, add and edit permissions xiv) read, add and delete permissions xv) read, edit and delete permissions xvi) add, edit and delete permissions
 </TD> <TD>
 - The user in evolution should be able to access the shared folder only upto the privileges given to the user.
 </TD>
</TR> <TR>
- <TD HEIGHT=92>
 - Mailer
 </TD> <TD>
 - Groupwise â€“ Evolution
 </TD> <TD>
 - Sharing a groupwise folder with a user using evolution
 </TD> <TD>
 - Syncing the shared folder if any changes are made
 </TD> <TD>
 - Make changes like i) Renaming the shared folder ii) deleting a mail from the shared folder iii) Moving a mail into the shared folder iv) Marking a mail in the shared folder v) Adding/ removing users of the shared folder
 </TD> <TD>
 - The shared folder should be updated in all the users who have access to the shared folder
 </TD>
</TR> <TR>
- <TD HEIGHT=330>
 - Mailer
 </TD> <TD>
 - Groupwise â€“ Evolution
 </TD> <TD>
 - Sending mails from groupwise by applying send options
 </TD> <TD>
 - The user in groupwise should receive acknowledgments or notifications related to the settings (s)he has applied
 </TD> <TD>
 - i) Set the priority of the mail a. normal priority b. high priority c. low priority ii) Set the classification of the mail a. normal b. proprietary c. confidential d. secret e. top secret f. for your eyes only iii) Set the reply requested a. when convenient b. within 0 days c. within 99 days d. within (0-99) days iv) set the return notification a. only when opened b. only when deleted c. both opened and deleted d. none
 </TD> <TD>
 - The sender using groupwise should get back a notification from the receiver using evolution according to the settings that (s)he has applied.
 </TD>
</TR> <TR>
- <TD HEIGHT=77>
 - Mailer
 </TD> <TD>
 - Groupwise â€“ Evolution
 </TD> <TD>
 - Sending a meeting request from groupwise to evolution
 </TD> <TD>
 - The evolution user should receive a meeting request in his calendar folder.
 </TD> <TD>
 - Send a meeting request from groupwise to evolution i) Create a meeting inviting a user using evolution ii) Update the meeting and send updates iii) Delete the meeting and send updates
 </TD> <TD>
 - The user in evolution should receive a mails regarding the meeting updates whenever the meeting is updated
 </TD>
</TR> <TR>
- <TD HEIGHT=136>
 - Mailer
 </TD> <TD>
 - Groupwise â€“ Evolution
 </TD> <TD>
 - Receiving the meeting request in evolution
 </TD> <TD>
 - The user in evolution should be able to access the meeting request mail sent from a groupwise mail client
 </TD> <TD>
 - i) Verify the push-buttons accept, decline, tentative and open calendar in the meeting request mail that they appear in a proper format. ii) Verify the drop-down box which shows into which calendar the meeting has to be sent if it is accepted iii) Verify that the check-box (send reply to sender or RSVP) appears in the proper format iv) Verify the labels appear in the proper format
 </TD> <TD>
 - The mail should be accessible in evolution and should be able to select the calendar (drop-down list), click on one of the push-buttons, (un)mark the check-box (RSVP).
 </TD>
</TR> <TR>
- <TD HEIGHT=77>
 - Mailer
 </TD> <TD>
 - Groupwise â€“ Evolution
 </TD> <TD>
 - Migration from groupwise to evolution
 </TD> <TD>
 - The user using groupwise should be able to migrate to evolution comfortably.
 </TD> <TD>
 - Verify that all the data has been migrated from groupwise to evolution in the same format as it was in groupwise
 </TD> <TD>
 - All the data should be migrated to evolution from groupwise in the same format as it was in groupwise
 </TD>
</TR> <TR>
- <TD HEIGHT=121>
 - Mailer
 </TD> <TD>
 - Interoperability between mailer and other components
 </TD> <TD>
 - Interoperability between mailer and tasks
 </TD> <TD>
 - Converting a mail into a task
 </TD> <TD>
 - Convert a mail that i) has an attachment ii) has no attachments iii) formatted in HTML iv) is in plain-text format v) single recipient vi) multiple recipients
 </TD> <TD>
 - The mail should be converted into a task with(out) attachments if it has a single recipient. Else converted into an assigned task with the other recipients as the required participants.
 </TD>
</TR> <TR>
- <TD HEIGHT=121>
 - Mailer
 </TD> <TD>
 - Interoperability between mailer and other components
 </TD> <TD>
 - Interoperability between mailer and tasks
 </TD> <TD>
 - Receiving assigned task request and updates about the task
 </TD> <TD>
 - 
 
 </TD> <TD>
 - The participant should receive the meeting request in his tasks folder. (s)He should get the updates about the task only if he accepts or tentatively accepts or does not take any action
 </TD>
</TR> <TR>
- <TD HEIGHT=106>
 - Mailer
 </TD> <TD>
 - Interoperability between mailer and other components
 </TD> <TD>
 - Interoperability between mailer and contacts
 </TD> <TD>
 - Sending a message to a contact
 </TD> <TD>
 - i) Select a contact, right-click and select 'Send message to contact...' ii) Select a contact list, right-click and select 'Send message to contact...' iii) View the contact in the preview pane. Click on one of the email addresses that is shown as a hyperlink
 </TD> <TD>
 - It should open the compose mail window with the mail id in the 'to' text box
 </TD>
</TR> <TR>
- <TD HEIGHT=62>
 - Mailer
 </TD> <TD>
 - Interoperability between mailer and other components
 </TD> <TD>
 - Interoperability between mailer and contacts
 </TD> <TD>
 - Sending a contact
 </TD> <TD>
 - Select a contact or a contact-list, right-click and select 'Send contact'
 </TD> <TD>
 - Should open the compose mail window with the contact as an attachment
 </TD>
</TR> <TR>
- <TD HEIGHT=62>
 - Mailer
 </TD> <TD>
 - Interoperability between mailer and other components
 </TD> <TD>
 - Interoperability between mailer and contacts
 </TD> <TD>
 - adding a contact from the mailer
 </TD> <TD>
 - Right-click on an email address shown as hyperlink and select 'Add to addressbook'
 </TD> <TD>
 - The mail-id should be added in the selected address book
 </TD>
</TR> <TR>
- <TD HEIGHT=77>
 - Mailer
 </TD> <TD>
 - Interoperability between mailer and other components
 </TD> <TD>
 - Interoperability between mailer and contacts
 </TD> <TD>
 - adding frequent contacts
 </TD> <TD>
 - Adding frequent contacts. Goto edit > preferences. Select automatic contacts in the mail preferences tab. Mark the check-box 'Automatically create entries in the addressbook when responding to mail'
 </TD> <TD>
 - An entry should be created in the selected addressbook with the known contact information
 </TD>
</TR> <TR>
- <TD HEIGHT=62>
 - Mailer
 </TD> <TD>
 - Interoperability between mailer and other components
 </TD> <TD>
 - Interoperability between mailer and calendar
 </TD> <TD>
 - Sending meeting requests
 </TD> <TD>
 - Create a meeting. Add a few participants and send the meeting request. Verify that the meeting request is being sent to the participants.
 </TD> <TD>
 - The meeting request should be sent to the participants and the mail should be present in the sent items
 </TD>
</TR> <TR>
- <TD HEIGHT=121>
 - Mailer
 </TD> <TD>
 - Interoperability between mailer and other components
 </TD> <TD>
 - Interoperability between mailer and calendar
 </TD> <TD>
 - Receiving meeting requests and updates about the meeting if it is accepted
 </TD> <TD>
 - 
 
 </TD> <TD>
 - The participant should receive the meeting request in his calendar folder. (s)He should get the updates about the meeting only if he accepts or tentatively accepts or does not take any action
 </TD>
</TR>

</TABLE>