syncml iop smoke

8/8/2019 SyncML IOP Smoke

1/21

ts_title Client Smoke Testing# Creation Date: 10/14/2004

#

ts_tester

ts_versiondata_type

test_type

os

language

comm_type

num_pims

pim1

pim2

sys_condition

ts_start

ts_estimated_end

ts_actual_end

# Nokia6085

# Intera_Client

# Native PIM serialization/deserialization; Hack for Contact/Unfiled used.

# Action Item Automated

#

tc Provisioningtitle

Perform a sync

Go to Devices tab in WebUI.


Delete the device from WebUI from Devices tab.

Perform a sync


Written By: Core ISRo

< Select a Device fro

< Select a PIM from D

Pass /Fail

Make sure that all needed handlers are properly

uploaded on the serverLogon in WebUI. Go to Device Setup. Choosethe device you want to provision. Don't enter theIMEI. Check all the section supported by thephone and perform a provisioning.

Perform a provisioning on each section supportedby the device using "Provisioning existing device"

and after each provisioning perform a sync

Go to Device Setup. Choose the device you wantto provision. Enter the IMEI. Check all the sectionsupported by the phone and perform aprovisioning.


2/21

# SAN / SAS

Sync on device.

tcContacts SIM

title

NO PASS

NO PASS

Modify in device any field. Sync NO PASS

Delete a contact on the client. Sync NO PASS

Create a contact in client. Sync NO PASS

NO PASS

Modify the contact in WebPIM. Sync NO PASS

Make sure that all needed SAN handlers areproperly uploaded on the server for the deviceyou are testing.

Make sure that in devices.xml have the correctSAN parameter set.

Make sure your device is correctly configured forSAN. In case you already provisioned yourdevice the needed information (phone number)should be already set. Notify Device optionwithin Devices should be checked by default.

Make sure you have all the section checked forsync. Create a record on each section on WebUIand perform a logout

Modify/delete a record on each section on WebUI

and perform a logout

Uncheck Notify Device option within devicessection. In WEBUI Add/ mod/ del some recordsfor each section. Logout.

Add/ mod/ del some records for each section.Perform SAN using a second device

Make sure you have only one section checked forsync. Add/modify/delete a record in WebUI on

that specific section and logout. Perform this stepon all sections supported by the client

Add/ mod/ del some records from one device.Sync

Create a comprehensive(fill all data fields)contact in WebPIM. Sync

Modify the contact in WebPIM (change Last

Modify the contact in the client change the First


3/21

Delete a contact in WebPIM. Sync NO PASS


Modify a contact in WebPIM. Sync YES PASS

Modify a contact in client. Sync NO PASS

Delete the contact in WebPIM NO PASS

Create three contacts on the client. Sync NO PASS

NO PASS

NO PASS

NO PASS

tc

Contacts PhonetitleNO PASS

NO PASS


Delete a contact on the client. Sync NO PASS


NO PASS

Modify the contact in WebPIM. Sync NO PASS

Delete a contact in WebPIM. Sync NO PASS


Modify a contact in WebPIM. Sync NO PASS

Modify a contact in client. Sync NO PASS

Delete the contact in WebPIM NO PASS

Create three contacts on the client. Sync NO PASS

NO PASS

NO PASS

NO PASS

# Support for photo sync field if available on device)

Add a contact in WebPIM. Sync NA

Add a contact on phone. Sync NA

Add a photo in WebPIM. Sync NA

Add a photo on phone. Sync NA

Change a photo in WebPIM. Sync NA

Delete a contact in client, modify same contact inWebPIM, then sync

Delete a contact in WebPIM, modify same

Delete a contact in WebPIM, delete another

Create a comprehensive(fill all data fields)

Modify the contact in WebPIM (change Last

Modify the contact in the client change the Firstname). Sync

Delete a contact in client, modify same contact in

Delete a contact in WebPIM, modify same

Delete a contact in WebPIM, delete another


4/21

Change a photo on phone. Sync NA

Delete the photo in WebPIM. Sync NA

Delete the photo on phone. Sync NA

tcAppointmentstitle

NO PASS

Modify the event in WebPIM. Sync NO PASS


Delete the event on the client. Sync NO PASS

Create a Simple event in the client. Sync NO PASS

Modify the event in the client. Sync NO PASS


Delete the event in WebPIM. Sync NO PASS

Create a Simple event in client. Sync NO PASS


Modify the event in client. Sync NO PASS

Delete the event in WebPIM NO PASS

Create three events on the client. Sync NO PASS

NO PASS

NO PASS

NO PASS

NO FAIL

NO PASS

tc

TaskstitleCreate a task in WebPIM (fill all data fields). Sync

Modify the task in WebPIM. Sync

Modify in device any field. Sync

Delete the task on the client. Sync

Create a task in the client. Sync

Modify the task in the client. Sync

Modify the task in WebPIM. SyncDelete the task in WebPIM. Sync

Create a Simple event in WebPIM (fill all data

Delete one event in client, modify same event inWebPIM, then sync

Delete an event in WebPIM, modify same eventin client, then sync

Delete an event in WebPIM, delete another eventin client. Sync

Create a daily, weekly and monthly event in both

Modif / deleteon some records created at


5/21

Create a task in client. Sync

Modify the task in WebPIM. Sync

Modify the task in client. Sync

Delete the task in WebPIM

Create three tasks on the client. Sync

tc

Memostitle

Create a note in WebPIM (fill all data fields). Sync

Modify the note in WebPIM. Sync

Modify in device any field. Sync

Delete the note on the client. Sync

Create a note in the client. Sync

Modify the note in the client. Sync


Delete the note in WebPIM. Sync

Create a note in client. Sync


Modify the note in client. Sync

Delete the note in WebPIM

Create three notes on the client. Sync

Delete one task in client, modify same task inWebPIM, then sync

Delete an task in WebPIM, modify same task inclient, then sync

Delete an task in WebPIM, delete another task inclient. Sync

,WebPIM, then sync

Delete an note in WebPIM, modify same note inclient, then sync


6/21

tc Sync Typestitle

# Oneway sync from client only

Perform a normal sync.

# Oneway Refresh sync from client only


# Oneway sync from server only(SyncML1.2 server mandatory)

Perform a normal s nc.

# Oneway Refresh sync from server only


# Slow Sync/Full Sync


# Suspend/resume only for clients that knowAdd some records on both sides. Sync

During synchronization Cancel the sync

Start another sync.

# Revision History

# Update the test case to use the latest test suite - Laurentia Toma - 03/10/10

# Added support photo field - Alina Pacurar - 3/17/2005

Delete an note in WebPIM, delete another note inclient. Sync

Set one way sync from client.

Add/Mod/Del records from both server and client.Sync

Set refresh sync from client only

Modify and Delete existing record on both sides.Enter several records in client, Enter servalrecords in server. Sync

Set one way sync from server.

Add/Mod/Del records from both server and client.Sync

Set refresh sync from server only

Modify and Delete existing record on both sides.Enter several records in client, Enter servalrecords in server. Sync

Enter new records in client/ server. Mod/ modsame record from both sides. Mod/ del samerecord from both sides.Set slow sync as a synctype. Sync


7/21

# Updated the test case for devices having native clients - Laurentia Toma - 0

# Changed the photo field and change provisioning to be at the first part of th

# Updated the check sheet in order to be use by IOP team - Alina Pacurar 05/

# Updated the check sheet , changed provisioning and SAN in order to test a


8/21

Bug No. Testers Notes

drop down list (add additional Devices to cell B18)

rop down list (add additional PIMs to cell B19)

(Use comma delimiter formultiple bugs)


9/21


10/21

Photo not handled by client.





All tests pass but the device is only


11/21




Repeat Rule not handled by Client.


12/21


13/21

yncML 1.2

05


14/21

6/16/2005

test case. - Alina Pacurar - 8/29/2005

11/2006

ording with the changes from WebUI, added steps for suspend/resum


15/21

Expected Results

All handlers are availble in WebUi.

The sync should end succesfully

The device is deleted from WebUi.

The sync should end succesfully

All information can be entered and is saved. Allsections available on device are displayed inWebUI and can be checked.The device shouldreceive a message and should be correctlyprovisioned

Make sure that you have only one device withIMEI and with the phone number

The device should be correctly provisioned andthe sync should end succesfully.


All information can be entered and is saved. Allsections available on device are displayed inWebUI and can be checked.The device shouldreceive a message and should be correctlyprovisioned



16/21

All handlers are availble in WebUi.

Information is correctly set.

All settings for SAN are correct.

Changes done before are correctly done.

Contact is in the client

Contact has been modified on the client

Contact is deleted from WebPIM

Contact is in WebPIM

Contact is modified in WebPIM

Contact is modified on the client

The device should receive a message and asynchronization should start. After the syncends all the records should be correctly addedon the client

The device should receive a message and a

synchronization should start. After the syncends all the records should becorrectlytransferred on the client

The message should not be received ondevice.

The message should not be received ondevice.

All devices configured for SAN should receive amessage and a synchronization should start.

After the sync ends all the records should becorrectly transferred on the client

All devices configured to be notified shouldreceive notification alerts. Sync should beinitiated on the sections configured withinnotification request. Records should betransferred correctly

The modification should be transferred on server


17/21

Contact is deleted in client

Contact in in the WebPIM


Changes are in WebPIM


Contacts are in WebPIM

Contact is in the client

Contact has been modified on the client

Contact is deleted from WebPIM

Contact is in WebPIM

Contact is modified in WebPIM



Contact in in the WebPIM




Contacts are in WebPIM

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

The contact must remain in both places with thechanges, in order the modification prevails over

The contact must remain in both places with the

Both contacts are deleted from both WebPIM




Both contacts are deleted from both WebPIM


18/21

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

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


event is deleted in client

events are in WebPIM

The events should be correctly transferred

task is in the client

task has been modified on the client

task is deleted from WebPIM

task is in WebPIM

task is modified in WebPIM

task is modified on the clienttask is deleted in client

The modification should be transferred on serverside. All the fields previously completed shouldremain in WebUI.

The event must remain in both places with thechanges, in order the modification prevails overdeletion

The event must remain in both places with thechanges, in order the modification prevails overdeletion

Both events are deleted from both WebPIM andclient

The records should be transferred correctl on



19/21

task is in WebPIM

task is modified on the client


task is deleted in client

tasks are in WebPIM

Note is in the client

Note has been modified on the client

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


Note is deleted in client

Notes are in WebPIM

The task must remain in both places with thechanges, in order the modification prevails over

The task must remain in both places with thechanges, in order the modification prevails overdeletion

Both tasks are deleted from both WebPIM andclient

The modification should be transferred on serverside. All the fields previously completed shouldremain in WebUI.

,

deletion

The note must remain in both places with the

changes, in order the modification prevails overdeletion


20/21

Nothing should change


Records shouldn't be duplicated on any side


The stync should start correctly

Both notes are deleted from both WebPIM andclient

User is able to change sync type; optionremains checked within client UI

Only changes from client side should betransferred

All records from server should be added on


All records from client are on the server.Records which existed on the server and not onthe client, are deleted from the server


Only changes from server side should betransferred

All records from client should be transferred to


All records from server are on client. Recordswhich existed on the client and not on theserver, are deleted from the client

After the sync ends check the logs and in thelast client see if the client sends 224

After the sync ends check the logs and see ifthe client requires 225


21/21

- Alina Biji 10/20/2006

syncml iop smoke

Documents