P. 1
SyncML IOP Smoke

SyncML IOP Smoke

|Views: 20|Likes:
Publicado porqpepyq

More info:

Published by: qpepyq on Sep 22, 2010
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as XLS, PDF, TXT or read online from Scribd
See more
See less

09/22/2010

pdf

text

original

ts_title #

Client Smoke Testing
Creation Date: 10/14/2004 Written By: Core ISRo

# ts_tester ts_version data_type test_type os language comm_type num_pims < Select a Device from drop down list pim1 < Select a PIM from Drop down list pim2 sys_condition ts_start ts_estimated_end ts_actual_end # Nokia6085 # Intera_Client # Native PIM serialization/deserialization; Hack for Contact/Unfiled used. Pass / # Action Item Automated Fail # tc title

Provisioning
Make sure that all needed handlers are properly uploaded on the server Logon in WebUI. Go to Device Setup. Choose the device you want to provision. Don't enter the IMEI. Check all the section supported by the phone and perform a provisioning. Perform a sync Go to Devices tab in WebUI. Perform a provisioning on each section supported by the device using "Provisioning existing device" and after each provisioning perform a sync Go to Devices tab in WebUI. Delete the device from WebUI from Devices tab. Go to Device Setup. Choose the device you want to provision. Enter the IMEI. Check all the section supported by the phone and perform a provisioning. Perform a sync Go to Devices tab in WebUI.

#

SAN / SAS
Make sure that all needed SAN handlers are properly uploaded on the server for the device you are testing. Make sure that in devices.xml have the correct SAN parameter set. Make sure your device is correctly configured for SAN. In case you already provisioned your device the needed information (phone number) should be already set. Notify Device option within Devices should be checked by default. Make sure you have all the section checked for sync. Create a record on each section on WebUI and perform a logout Modify/delete a record on each section on WebUI and perform a logout

Uncheck Notify Device option within devices section. In WEBUI Add/ mod/ del some records for each section. Logout. Add/ mod/ del some records for each section. Perform SAN using a second device Sync on device. Make sure you have only one section checked for sync. Add/modify/delete a record in WebUI on that specific section and logout. Perform this step on all sections supported by the client Add/ mod/ del some records from one device. Sync

tc title

Contacts SIM
Create a comprehensive(fill all data fields) contact in WebPIM. Sync Modify the contact in WebPIM (change Last name). Sync Modify in device any field. Sync Delete a contact on the client. Sync Create a contact in client. Sync Modify the contact in the client change the First name). the contact in WebPIM. Sync Modify Sync NO PASS

NO NO NO NO NO NO

PASS PASS PASS PASS PASS PASS

delete another contact in client. Sync Delete the contact in WebPIM NO NO YES NO NO PASS PASS PASS PASS PASS Create three contacts on the client. Sync Add a contact on phone. Sync Modify the contact in WebPIM.Delete a contact in WebPIM. modify same contact in NO WebPIM. Sync Modify Sync Delete a contact on the client. Sync NO PASS Delete a contact in client. Sync Add a contact in WebPIM. then sync Delete a contact in WebPIM. then sync Delete a contact in WebPIM. Sync NA . modify same contact in client. Sync Change a photo in WebPIM. Sync NO NO NO PASS PASS PASS PASS PASS PASS NA NA NA NA Delete a contact in client. in WebPIM. Sync Modify the contact in the client change the First name). in device any field. Sync Modify in contact in WebPIM (change Last name). Delete NO # contact infor photo sync field if available on device) Support client. modify same Delete a then sync NO contacta contact then sync delete another in client. Sync NO NO NO NO NO NO NO NO NO NO PASS PASS PASS PASS PASS PASS PASS PASS PASS PASS Modify a contact in client. Sync Delete a contact in WebPIM. Sync Modify a contact in WebPIM. modify same contact in NO WebPIM. Sync Add a photo in WebPIM. Sync Create a contact in client. Sync Modify a contact in WebPIM. Sync Delete the contact in WebPIM Create three contacts on the client. Sync Create a contact in client.contact in WebPIM. Sync NO NO PASS PASS PASS tc title Contacts Phone Create a comprehensive(fill all data fields) contacttheWebPIM. Sync Add a photo on phone. Sync Modify a contact in client. Sync Create a contact in client.

weekly and monthly event in both WebPIM and client sides. Sync Delete the photo in WebPIM. Sync Create a daily.Change a photo on phone. Sync Modify the event in WebPIM. Sync Create a task in the client. Sync . Sync Delete one event in client. Sync created at Modify/ deleteon some records tc title previous step on WebUI and the rest of them on cllient side. Sync Modify the event in WebPIM. Sync Delete the task on the client. Sync Create a Simple event in client. Sync Modify in device any field. Sync Delete the event in WebPIM. Sync Modify the event in the client. Sync Modify the event in WebPIM. Sync Modify in device any field. Sync Delete the event in WebPIM Create three events on the client. then sync NO NO NO NO NO NO NO NO NO NO NO PASS PASS PASS PASS PASS PASS PASS PASS PASS PASS PASS NO PASS Delete an event in WebPIM. Sync Modify the task in the client. Sync NA tc title Appointments Create a Simple event in WebPIM (fill all data fields). modify same event in WebPIM. delete another event NO in client. Sync NO NO PASS FAIL PASS Tasks Create a task in WebPIM (fill all data fields). then sync Delete an event in WebPIM. Sync NO NO NO PASS PASS PASS Delete the event on the client. Sync Modify the task in WebPIM. modify same event in client. Sync Modify the event in client. Sync Modify the task in WebPIM. Sync NA NA Delete the photo on phone. Sync Create a Simple event in the client. Sync Delete the task in WebPIM.

Sync Modify the note in WebPIM. Sync WebPIM. then sync . Sync Create a note in client. then sync Delete an task in WebPIM. Sync Modify the note in WebPIM. Sync Delete the note in WebPIM Create one note in client. Sync Modify the note in WebPIM. Sync Create a note in the client. modify same task in client. Sync Modify in device any field. modify same task in WebPIM. Sync Delete one task in client. Sync tc title Memos Create a note in WebPIM (fill all data fields). modify same note in client. Sync Modify the task in client. Sync Modify the note in client. Sync Delete the note in WebPIM. modify same note in Delete three notes on the client. Sync Modify the task in WebPIM. then sync Delete an task in WebPIM. Sync Delete the task in WebPIM Create three tasks on the client. delete another task in client.Create a task in client. Sync Modify the note in the client. then sync Delete an note in WebPIM. Sync Delete the note on the client.

Sync Perform a normal sync.Laurentia Toma .2 server mandatory) Set one way sync from server. Enter several records in client. Oneway sync from server only(SyncML1. Sync Perform a normal sync. Sync tc title # Sync Types Oneway sync from client only Set one way sync from client. Sync During synchronization Cancel the sync Start another sync. Enter several records in client.3/17/2005 . # Oneway Refresh sync from client only Set refresh sync from client only Modify and Delete existing record on both sides. Sync Perform a normal sync. Sync Perform a normal sync.Delete an note in WebPIM. # # # # Suspend/resume only for clients that know SyncML 1. # # # Revision History Update the test case to use the latest test suite . Enter serval records in server.03/10/1005 Added support photo field . Add/Mod/Del records from both server and client. Oneway Refresh sync from server only Set refresh sync from server only Modify and Delete existing record on both sides. Mod/ del same record from both sides.2 Add some records on both sides. Enter serval records in server. Mod/ mod same record from both sides. Sync Perform a normal sync.Alina Pacurar . Slow Sync/Full Sync Enter new records in client/ server. delete another note in client.Set slow sync as a sync type. Add/Mod/Del records from both server and client.

06/16/2005 Changed the photo field and change provisioning to be at the first part of the test case.Laurentia Toma .Alina Pacurar 05/11/2006 Updated the check sheet . .Alina Pacurar Updated the check sheet in order to be use by IOP team . changed provisioning and SAN in order to test acording with the changes from .# # # # Updated the test case for devices having native clients .

Device from drop down list (add additional Devices to cell B18) PIM from Drop down list (add additional PIMs to cell B19) Bug No. (Use comma delimiter for multiple bugs) Testers Notes .

.

All tests pass but the device is only supported a defined set of fields when serializing/deserializing. . Photo not handled by client. Photo not handled by client. Photo not handled by client. This means it will only work with the supported fields. Photo not handled by client. Photo not handled by client.

Photo not handled by client. Repeat Rule not handled by Client.Photo not handled by client. . Photo not handled by client.

.

03/10/1005 .2 ma .ry) know SyncML 1.

.tia Toma .Alina Biji 10/20/2006 . added steps for suspend/resume .Alina Pacurar .8/29/2005 Pacurar 05/11/2006 der to test acording with the changes from WebUI.06/16/2005 rst part of the test case.

All information can be entered and is saved. All information can be entered and is saved. All sections available on device are displayed in WebUI and can be checked.The device should receive a message and should be correctly provisioned The sync should end succesfully Make sure that you have only one device with IMEI and with the phone number .The device should receive a message and should be correctly provisioned The sync should end succesfully Make sure that you have only one device with IMEI and with the phone number The device should be correctly provisioned and the sync should end succesfully. All sections available on device are displayed in WebUI and can be checked.Expected Results All handlers are availble in WebUi. Make sure that you have only one device with IMEI and with the phone number The device is deleted from WebUi.

After the sync ends all the records should be correctly transferred on the client All devices configured to be notified should receive notification alerts. Records should be transferred correctly Contact is in the client Contact has been modified on the client The modification should be transferred on server side. Sync should be initiated on the sections configured within notification request. The message should not be received on device.All handlers are availble in WebUi. Changes done before are correctly done. All settings for SAN are correct. Contact is in WebPIM Contact is modified in WebPIM Contact is modified on the client . After the sync ends all the records should be correctly added on the client The device should receive a message and a synchronization should start. All the fields previously completed should Contact is deleted from WebPIM remain in WebUI. All devices configured for SAN should receive a message and a synchronization should start. Information is correctly set. After the sync ends all the records should be correctlytransferred on the client The message should not be received on device. The device should receive a message and a synchronization should start.

in order the modification prevails over deletion The contact must remain in both places with the changes. in order the modification prevails over Both contacts are deleted from both WebPIM deletion and client Contact is in the client Contact has been modified on the client The modification should be transferred on server side.Contact is deleted in client Contact in in the WebPIM Contact is modified on the client Changes are in WebPIM Contact is deleted in client Contacts are in WebPIM The contact must remain in both places with the changes. in order remain in both places with the The contact must the modification prevails over deletion in order the modification prevails over changes. All is deleted previously completed should Contact the fields from WebPIM remain in WebUI. Both contacts are deleted from both WebPIM deletion and client The contact is transferred on phone The contact is transferred in WebPIM The contact is updated on phone The contact is updated in WebPIM The photo is changed on phone . Contact is in WebPIM Contact is modified in WebPIM Contact is modified on the client Contact is deleted in client Contact in in the WebPIM Contact is modified on the client Changes are in WebPIM Contact is deleted in client Contacts are in WebPIM The contact must remain in both places with the changes.

task is in the client task has been modified on the client The modification should be transferred on server side. event is deleted from WebPIM event is in WebPIM event is modified in WebPIM event is modified on the client event is deleted in client event is in WebPIM event is modified on the client Changes are in WebPIM event is deleted in client events are in WebPIM The event must remain in both places with the changes. task is in WebPIM task is modified in WebPIM task is modified on the client task is deleted in client . in order the modification prevails over deletion Both events are deleted from both WebPIM and client The events should be correctly transferred The records should be transferred correctly on both sides.The photo is changed in WebPIM The photo is deleted from phone The photo is deleted from WebPIM event is in the client event has been modified on the client The modification should be transferred on server side. in order the modification prevails over deletion The event must remain in both places with the changes. All the fields previously completed should remain in WebUI. All the fields previously completed should task is deleted from WebPIM remain in WebUI.

Note is deleted from WebPIM Note is in WebPIM Note is modified in WebPIM Note is modified on the client Note is deleted in client Note is in WebPIM Note is modified on the client Changes are in WebPIM Note is deleted in client The note must remain in both places with the Notes arein order the modification prevails over changes. in WebPIM deletion The note must remain in both places with the changes.task is in WebPIM task is modified on the client Changes are in WebPIM task is deleted in client tasks are in WebPIM The task must remain in both places with the changes. in order the modification prevails over deletion . All the fields previously completed should remain in WebUI. in order the modification prevails over deletion Both tasks are deleted from both WebPIM and client Note is in the client Note has been modified on the client The modification should be transferred on server side. in order the modification prevails over deletion The task must remain in both places with the changes.

option remains checked within client UI Only changes from client side should be transferred All records from server should be added on client side User is able to change sync type. option remains checked within client UI All records from server are on client.Both notes are deleted from both WebPIM and client User is able to change sync type. Records which existed on the server and not on the client. option remains checked within client UI Only changes from server side should be transferred All records from client should be transferred to server side User is able to change sync type. option remains checked within client UI All records from client are on the server. are deleted from the server Nothing should change User is able to change sync type. Records which existed on the client and not on the server. are deleted from the client Nothing should change Records shouldn't be duplicated on any side Nothing should change The stync should start correctly After the sync ends check the logs and in the last client see if the client sends 224 After the sync ends check the logs and see if the client requires 225 .

Alina Biji 10/20/2006 .pend/resume .

You're Reading a Free Preview

Descarga
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->