Overview
iTunes software on Windows XP and Mac OS X will take care of Contacts/Address Book synchronization as long as the data is located in the local desktop/laptop.
Known Issues
There may be some minor issues that affect a small number of people at MIT:
- If the user's data is stored in the TechTime database, it might not be possible to synchronize the data with the iPhone.
- Current users of Palm OS devices may need to export the data from Palm Desktop Software to Outlook (Windows XP) or Address Book (Mac OS).
Verifying Main Functionality
Note: "Server" refers to local desktop/laptop data storage for Contacts.
Testing should be performed for Windows XP (Outlook), Mac OS (Address Book). While there are other applications that users might use to store Contacts, for the purpose of the evaluation, the above should suffice.
ID |
Test |
Objective |
Procedure |
Expected Result |
Result |
---|---|---|---|---|---|
1.1.1 |
Create new contact with minimal fields from the server. |
To ensure that the fields that are already supported for a device are properly transferred from server to device upon creation and from device to server upon modification. |
Create a new contact entry from the server with all fields (except for addresses, emails, telephone numbers, and URLs) |
The address book entry created on the server should be reflected on the device with an appropriate mapping of fields taking advantage of what the device supports. |
|
1.1.2 |
Create new contact with minimal fields from the device. |
To ensure that the fields that are already supported for a device are properly transferred from device to server upon creation and from device to server upon modification. |
Create a new contact entry from the device with all fields filled out (except for addresses, emails, telephone numbers, and URLs) |
The address book entry created on the device should be reflected on the server with an appropriate mapping of fields taking advantage of what the server supports |
|
1.1.3 |
Create new contact with incomplete fields from the server |
Verify that fields with no data can be synchronized from the server correctly |
Create a new contact entry from the server without specification of the name suffix, name prefix and job title fields (NULL characters). |
The address book entry created on the device is displayed correctly and can be edited. |
|
1.2.1 |
Create new contact with addresses from the server. |
To ensure that the address fields that are supported for a device are properly transferred from server to device upon creation, modification and deletion. |
Create a contact with several addresses (home, business, etc...) from the server, |
The contact should appear on the device and address types supported by the device should be available and formatted in a way that is usable to the user. |
|
1.2.2 |
Create new contact with addresses from the device. |
To ensure that the address fields that are supported for a device are properly transferred from device to server upon creation, modification and deletion. |
Create a contact with several addresses (home, business, etc...) from the device (if the device supports it), |
The contact should appear on the server and address types entered on the device should be properly mapped, available, and formatted in a way that is usable to the user on the server. |
|
1.3.1 |
Create new contact with telephone numbers from the server. |
To ensure that the telephone fields that are supported for a device are properly transferred from server to device upon creation, modification and deletion. |
Create a contact with several phone numbers (home1, home2, business, etc...) from the server, |
The contact should appear on the device and the phone numbers supported by the device should be available and formatted in a way that is usable to the user. |
|
1.3.2 |
Create new contact with telephone numbers from the device. |
To ensure that the telephone fields that are supported for a device are properly transferred from device to server upon creation, modification and deletion. |
Create a contact with several phone numbers (home1, home2, business, etc...) from the device (if the device supports it), |
The contact should appear on the server and phone numbers entered on the device should be properly mapped, available, and formatted in a way that is usable to the user on the server. |
|
1.4.1 |
Create new contact with emails from the server. |
To ensure that the email fields that are supported for a device are properly transferred from server to device upon creation, modification and deletion. |
Create a contact with several email addresses (home1, home2, business, etc...) from the server, |
The contact should appear on the device and the email addresses supported by the device should be available and formatted in a way that is usable to the user. |
|
1.4.2 |
Create new contact with urls/web page addresses from the server. |
To ensure that the url fields that are supported for a device are properly transferred from server to device upon creation, modification and deletion. |
Create a contact with several web page URLS (work web site, home web site, etc...) from the server, |
The contact should appear on the device and the URLs supported by the device should be available and formatted in a way that is usable to the user. |
|
1.4.3 |
Create new contact with emails from the device. |
To ensure that the email fields that are supported for a device are properly transferred from device to server upon creation, modification and deletion. |
Create a contact with several email addresses (home1, home2, business, etc...) from the device, |
The contact should appear on the server and email addresses entered on the device should be properly mapped, available, and formatted in a way that is usable to the user on the server. |
|
1.4.4 |
Create new contact with urls/web page addresses from the device. |
To ensure that the URL fields that are supported for a device are properly transferred from device to server upon creation, modification and deletion. |
Create a contact with several web page URLS (work web site, home web site, etc...) from the device, |
The contact should appear on the server and URls entered on the device should be properly mapped, available, and formatted in a way that is usable to the user on the server. |
|
1.5.1 |
Special Characters |
Verify that special characters in contacts properly sync to and from the device. |
From the Server, create a contact filling out all text fields with special characters. |
The contact should appear on the device with all fields on the server correctly mapped to corresponding fields on the device. All special characters should properly appear on the device as it is displayed on the server. |
|
1.6.1 |
Delete a contact from the server |
To ensure that when a contact is deleted on the server, it is also deleted on the device. |
From the server, delete an existing contact entry and sync. |
The corresponding address book entry is removed from the device. |
|
1.6.2 |
Delete a contact from the device |
To ensure that when a contact is deleted on the device, it is also deleted on the server. |
From the device, delete an existing contact entry and sync |
The corresponding address book entry is removed from the server. |
|