[[Test Criteria/3.0.1 ISSUEDに戻る>Test Criteria/3.0.1 ISSUED]]
----
*5.1:Universal Tests(一般テスト) [#y10ab78a]
-Test Title|(タイトル)
-Estimated Test Time (minutes)(必要な時間(分))
-Test Description(詳細)
-Not Required for(不要なケース)
-Required for|(必要なケース)
-Testing Notes(注意)
-Testing Steps(手順)
-Exception(例外)



(以下、UNI-01~UNI-11)
**UNI-01 [#s942ca28]
***Test Title [#q5960ee8]
Installation, Normal and Stressed Usage

***Test Description [#aa1291fd]
The application .SIS file installs and successfully functions after start up. The application does not affect the use of the core system features or other applications. During extended usage, the application can handle exceptional, illegal, or erroneous user actions. At no time should the application cause the phone to crash or freeze, and it should exit gracefully from any application-specific exceptions.

***Estimated Test Time (minutes) [#o258bd21]
60-120

***Not Required for [#w923c1ca]
-Passive content

***Required for [#y227fd6f]
-Pre Symbian OS v9.x application
-No Capabilities - Symbian OS v9.x
-ALL Symbian OS v9.x Capabilities

***Testing Notes [#t777e67d]
+Do not carry out emergency call test on the public telephone network as it will cause calls to actual emergency services.
+The practical purpose of this test is as a regression test prior to release. For wide scale deployment, it is expected that the application has been extensively and thoroughly system tested in many different scenarios prior to submission, which is anticipated to be essential to successfully pass this test case.

***Testing Steps [#x2c6e47b]
+Install the .SIS file.
++RESULT: The .SIS file installs successfully.
+Start the application.
++RESULT: The application starts successfully within a reasonable time period (5 seconds) or provides appropriate progress indication.
+Exit the application and re-start the application (if possible).
++RESULT: The application exits and restarts successfully.
+Use the application as per normal operation as specified in the user guide and in accordance with Declarative Statements received via submission.
++RESULT: The application works in accordance with the end user expectations for the applications.
+Whilst using the application, switch away and use the main system applications and features (e.g. ''Phone, Calendar/Agenda, Clock, Contacts'').
++RESULT: The application does not inappropriately control thread priority or switch/steal focus from other applications, and it releases resources when not in use.
++RESULT: The application allows other applications access to sufficient OS resources to run, i.e. the application shuts down/releases resources if the system requests it to do so.
+Whilst the application is running in the foreground proceed to activate the ''System Lock''. Verify it is still possible to unlock the phone and return to the application.
++RESULT: The application must not inadvertently override the system lock; i.e. unless it is a feature or characteristic of the application in line with the user’s expectation.
+Apply stressful scenarios to the device whilst using application as per its normal operation. For example:
++Switching rapidly between applications.
++Opening and using many other applications simultaneously.
++Launch the camera application and take several pictures whilst the application is running.
++Pressing keys rapidly and/or tapping the screen rapidly (if touch-screen driven) in the application to send it many events at once..
++Enter inappropriate data into the application.
+++Special characters.
+++Leaving input fields blank.
+++Entering strings of maximum length (where possible)..
++Removing memory cards whilst the application is under test.
++If the application creates connections start a connection and close it from the connection manager before the connection is fully established..
++If the application uses connections. Use the connection manager to close the connection suddenly.
++RESULT: The application must not invalidate basic Type Approval of the phone, i.e. it must always be able to switch away from the application and to make an Emergency Call.
++RESULT: The application must be able to handle exceptional, illegal, or erroneous actions. It will not cause the phone to crash, freeze or the phone to become unusable.
++RESULT: The application exits gracefully (i.e. with appropriate error message not system panics) from unrecoverable exceptions and can be restarted successfully following any exception.

***Exception [#de4ed64c]
:UNI-01.EX1:Infrequent or Non Repeatable Crash.|If an application fails this test as a result of crashing, it may receive an exception if the crash is infrequent, non repeatable and the application, other applications and mobile phone remains usable within user expectations.


**UNI-02 [#fe593b80]
***Test Title [#bba7ec26]
Service Interruption

***Test Description [#e0d0d56c]
The application should handle interruptions appropriately for the type of application and the type of interruption.

***Estimated Test Time (minutes) [#b3691c86]
none

***Not Required for [#ha38c353]
-Passive content

***Required for [#d295de85]
-Pre Symbian OS v9.x application
-No Capabilities - Symbian OS v9.x
-ALL Symbian OS v9.x Capabilities

***Testing Notes [#qd31f43f]
none

***Testing Steps [#mbed20e5]
+Start and/or use the application as per normal use conditions.
+Create and test the following scenarios.
++Receiving an incoming voice call.
++Receiving an incoming SMS.
++Receiving an incoming MMS.
++An alarm notification event.
++Connecting external power charger.
++Switching of UI Modes (e.g. flip, horizontal/vertical).
++RESULT: All interruptions are handled as a user would expect and the application continues to operate normally after the interruption. For example: a game should store its state and pause, whereas a timer application should continue even with the incoming interruption.
++RESULT: The interruptions are given user interface focus, e.g. audio, visual and user interface notifications occur as per normal phone operation.

***Exception [#x167d28c]
:No exceptions permitted.|


**UNI-03 [#q2c64862]
***Test Title [#x6835447]
Low Memory Startup

***Test Description [#za68e904]
The application should gracefully handle low memory situations during startup as per the LowMem Tool User Guide. When exiting due to low memory, the application displays appropriate error messages.

***Estimated Test Time (minutes) [#h32f04c2]
none

***Not Required for [#ded74ccf]
-Passive content

***Required for [#l574b5a3]
-Pre Symbian OS v9.x application
-No Capabilities - Symbian OS v9.x
-ALL Symbian OS v9.x Capabilities

***Testing Notes [#tc40766a]
none

***Testing Steps [#x9b60ec5]
+Run <LowMem Tool> to simulate a low memory situation.
+Start the application.
++RESULT: The application displays appropriate warning messages if it is unable to start during low memory conditions.
+Exit <LowMem Tool>.
++RESULT: The <LowMem Tool> application reports a failure rate of no more than 10% errors..

***Exception [#of8a9ebc]
:UNI-03.EX1:Non native application/s|If the application under test is running inside a Virtual Machine (e.g. Python, Flash Lite) then the application should not be responsible for memory failures caused by the Virtual Machine itself. As such, these applications are exempted from low memory testing.
:UNI-03.EX2:<LowMem Tool> Not Available For Symbian OS v9.x|Until LowMem Tool is generally available, this test can be skipped for applications on Symbian OS v9.x (I.e. S60 3rd Edition and UIQ3.x).


**UNI-04 [#h5b606d1]
***Test Title [#vda45a9c]
Low Storage Memory During Startup & Execution

***Test Description [#e81a889a]
The application should not fill all the available storage space of the device. If there is not enough storage space to run, the application indicates this to the user and exits gracefully.

***Estimated Test Time (minutes) [#d9227003]
none

***Not Required for [#a237042d]
-Passive content

***Required for [#o61895a3]
-Pre Symbian OS v9.x application
-No Capabilities - Symbian OS v9.x
-ALL Symbian OS v9.x Capabilities

***Testing Notes [#s992c164]
none

***Testing Steps [#fdc21f51]
+Start application.
+Simulate a low storage memory situation by filling the space with a number of large files (e.g. miscellaneous JPGs, MP4, MP3).
+Use application as per normal expected use.
++RESULT: The application either runs successfully or provides appropriate warning messages to the user to explain why it cannot run, exiting gracefully.
+Close the application (if not already closed).
+Start and use the application as per normal expected use.
++RESULT: The application either runs successfully or provides appropriate warning messages to the user to explain why it cannot run, exiting gracefully.
+If desired, delete files added in STEP2.

***Exception [#yb7415ba]
:UNI-04.EX1:Executing within a Run Time Environment or VirtualMachines|If the application under test is running inside a Virtual Machine (including, but not necessarily limited to, OPL, Python, Flash Lite) then the application should not be responsible for memory failures caused by the Virtual Machine itself. As such, these applications are exempted from low memory testing and Symbian will work with the Virtual Machine vendors to ensure these environments behave appropriately.
:UNI-04.EX2:Warning the End User Degrades the User Experience|For applications that do not have any user interaction, for example system and middleware services without a user interface, it is permissible to not provide a warning. However, the application should still handle low storage memory situations gracefully (i.e. the phone should remain usable and the application should be usable once sufficient memory is available).&br;&br;Examples are&br;-DLLs&br;-System and middleware components (without any user interaction)..&br;-Daemons

**UNI-05 [#o7711605]
***Test Title [#s13ad68f]
System Events and Task List Compliance

***Test Description [#x315b3fc]
The application can be closed by the Task List or Task Manager.

***Estimated Test Time (minutes) [#z796bc9b]
none

***Not Required for [#zf7d82d6]
-Passive content

***Required for [#u28b0ea8]
-Pre Symbian OS v9.x application
-No Capabilities - Symbian OS v9.x
-ALL Symbian OS v9.x Capabilities

***Testing Notes [#y4cf705d]
none

***Testing Steps [#xd49799a]
+Ensure the application is running.
+''On S60 device:''
++Switch focus to ''Task List'' (by holding down the S60 Applications key).
++Close application from ''Task List'' using the ‘c’ or back key.
+''On Series 80 device:''
++Press ''Menu''.
++Select the ''Task List'' menu item.
++Close the application from the ''Task List'' by selecting ''End Task''.
+''On UIQ device (''Task Manager'' present):''
++Run the system ''Task Manager''.
++Select the menu option to close the application from the ''Task List''.
+''On UIQ device (''Task Manager'' not present):''
++Run <File Storage Tool> to force a low memory message to the application.
++Use <Task Profiler Tool> to list active tasks and processes, or the built in task manager if applicable.
+''RESULT:''The application is visible in the task list and can be closed such that it is no longer running in memory.

***Exception [#d4540053]
:UNI-05.EX1:Application Already Closed|If the application closes down on change of focus in accordance with end user expectations, it is not required to be closable via the Task List as this can never occur. An example of this type of application may be a business card scanner that uses camera to capture input, upon loss of focus it may close as to release the camera for general use.
:UNI-05.EX2:Application Should Not Close or Does Not Run|If the SIS file contains only shared DLLs, it cannot be ‘run’ and therefore closed in this manner.
:UNI-05.EX3:Application Meets End User Expectations|With certain types of applications it is inherent in their functionality that they are not intended to close. Providing the application clearly functions within the end-user expectations of the application it can receive an exception from being closed via the task list. However in such case the user must be able to close the application from an Exit or Close option in the application menu.&br;&br;Examples are&br;-Anti-virus applications,&br;-Firewall and VPN clients,&br;-Device Management,&br;-Front End Processor (FEP) plug-ins,&br;-System and middleware components (without any user interaction)..&br;-Daemons

**UNI-06 [#e0c2bbd6]
***Test Title [#x861ae9c]
Application Functionality In Between Device Reboots

***Test Description [#w2c49907]
The application and device should both run normally after a sudden loss of power (whilst the application was running) and subsequent reboot of the device. The application should not crash, panic or freeze the device at any time.

***Estimated Test Time (minutes) [#x76d6a21]
none

***Not Required for [#r547f311]
-Passive content

***Required for [#wb218f30]
-Pre Symbian OS v9.x application
-No Capabilities . Symbian OS v9.x
-ALL Symbian OS v9.x Capabilities

***Testing Notes [#sbd1d2e5]
none

***Testing Steps [#w68ec87b]
+Ensure the application is running.
+Remove the battery to force the phone to suddenly power down.
+Re-insert battery, reboot the phone and restart the application.
+Verify the application is running correctly (as before).
++RESULT: The application and device operate normally. The device reboots successfully.

***Exception [#x20b515f]
:No exceptions permitted.|


**UNI-07 [#w1f1e4fe]
***Test Title [#zefcad52]
Backup and Restore Compliance

***Test Description [#nd954732]
The application should not interfere with a system backup and restore. If the application is intended to be backed-up, i.e. it is registered for back-up with the system, it should also continue to operate successfully upon restore.

***Estimated Test Time (minutes) [#b7a1d21e]
none

***Not Required for [#w98b5d5e]
-Passive content

***Required for [#sb88f54a]
-Pre Symbian OS v9.x application
-No Capabilities - Symbian OS v9.x
-ALL Symbian OS v9.x Capabilities

***Testing Notes [#f0a8cb4b]
+Applications and data are ''not'' automatically backed up on Symbian OS v9.x phones. You must explicitly register with the backup server to do this.
+Backup and restore may not work during testing and/or when the application is signed via Open Signed in early some earlier versions of S60 3rd Edition devices. To complete tests in such devices the application will need to be Express Signed or Certified Signed. This is issue is fixed in S60 3rd Edition Feature Pack 1.

***Testing Steps [#rb391349]
+Start the application.
+Connect the phone to the PC Suite supplied by the manufacturer and commence a backup. If there is no appropriate PC Suite version or software for the phone (e.g. a prototype), attempt to commence a Backup to Memory Stick/Card from the appropriate utility on the phone itself.
++RESULT: The backup process completes with no errors . the application does not lock and fail to release any files, for example.
+Once backup has completed, uninstall the application under test.
+Commence a full restore.
+Run the application once the restore process has completed.
++RESULT: The restore process completes with no errors. Once restore has completed, the application can be run and functions correctly.
+Exit the application under test.
+Run the main system applications and features (e.g. ''Phone, Calendar/Agenda, Clock, Contacts'') and verify they still work.
++RESULT: The device continues to operate normally after the restore.
+Take another compliant clean phone or format the phone you have, after which repeat STEP4 to STEP7 again with the new/formatted phone.
++RESULT: The restore process completes with no errors. Once restore has completed, the application can be run and functions correctly.
++RESULT: The device continues to operate normally after the restore.

***Exception [#d991474b]
:UNI-07.EX1:Backup Not Possible|An appropriate PC Suite or supplied a ‘to memory card’ backup option which functions is not available (e.g. prototype devices).
:UNI-07.EX2:Testing Not Possible (S60 3rd Edition on Symbian OS v9.1, i.e. prior to FP1)|This functionality is not testable on S60 3rd Edition on Symbian OS v9.1 devices hence this test case is not required for applications if the device ID (in the PKG file) constrains the application to only these device types.


**UNI-08 [#rf645fe6]
***Test Title [#mdd0c84e]
Uninstall

***Test Description [#ledd5ee9]
The application should uninstall itself cleanly.

***Estimated Test Time (minutes) [#z5172bf8]
none

***Not Required for [#bfa68129]
none

***Required for [#rd333221]
-Passive content
-Pre Symbian OS v9.x application
-No Capabilities - Symbian OS v9.x
-ALL Symbian OS v9.x Capabilities

***Testing Notes [#j7c4a3af]
+''Pre-Symbian OS v9.x (i.e. Symbian OS v6.x, v7.x, v8.x):''&br;Do not forget to remove .INI files which are automatically created in !:\System\Apps\AppName\ by adding the following to your PKG file:&br;&br;; Files to remove on uninstallation&br;""-"!:\System\Apps\AppName\AppName.ini",FN
+''Symbian OS v9.x onwards:''&br;In Symbian OS v9.x, all data in your private folder will be automatically removed. If you create data in public areas you should follow the advice in Note 1, to ensure that your data in these areas is also removed.

***Testing Steps [#b9d6d873]
+Ensure that the application is already installed and then uninstall the application
++RESULT: Any icon which was present in the system screen(s) disappears.
+Use <Disk Usage Tool> to check that all files are removed
++RESULT: Application uninstalls removing all application files with the exception of only leaving small configuration files to save user preferences.
+Excluding user generated files (e.g. as a result of creating documents, bookmarks MP3s etc) use Use <Disk Usage Tool> to check the amount of free storage memory is the same as when testing started.
++RESULT: Amount of free storage memory, before installation vs after uninstall, is within a 100Kb tolerance.

***Exception [#q617fd31]
:UNI-08.EX1:Font File Installation on Symbian OS v6.1 and v7.0|If your application installs additional fonts there is a known defect on earlier versions of Symbian OS (v6.1, v7.0) causing issues with font file removal. Hence, if your application would otherwise passes this test case, you are granted an exception.&br;&br;See FAQ-0860 in the Symbian OS FAQ database at developer.symbian.com for more details.
:UNI-08.EX2:Known Defects|Where a known defect in the installer prevents compliance with a test case, applications are considered exempt until such time as approved workarounds are published [[here>http://developer.symbian.com/wiki/display/sign/Symbian+Signed+Known+Defects]]. Developers should clearly state on their declarative statements when a known defect is preventing then from passing this test case.


:UNI-08.EX3:Intended Behavior To Not Allow Uninstall|In certain circumstances, if it is intended to prevent uninstall, as per the following scenarios.&br;-upgrading a ROM application on Symbian OS v9.x with a Partial Upgrade (PU) type SIS file, the user is given no option to uninstall the update/new version.&br;-The end user expectation of the application is such that it should not be installed and it is clearly documented in user guides.


**UNI-09 [#pef2f129]
***Test Title [#y2042a34]
Reinstallation and mass memory storage

***Test Description [#r4927e8e]
After uninstall, the application can be reinstalled successfully, including to other media locations (e.g. memory card).

***Estimated Test Time (minutes) [#z40d2792]
none

***Not Required for [#s3a3dd20]
none

***Required for [#q9db142e]
-Passive content
-Pre Symbian OS v9.x application
-No Capabilities - Symbian OS v9.x
-ALL Symbian OS v9.x Capabilities

***Testing Notes [#l5a4468f]
none

***Testing Steps [#wb4f1f2b]
+Having uninstalled the application, reinstall it.
+Start the application.
++RESULT: Application should successfully re-install and function after initial uninstall.
+Uninstall it again.
+Reinstall it to an alternative memory location (i.e. if you installed to the Internal drive initially, try to install to the Memory card and vice versa).
+Verify it works correctly again on the new memory location.
++RESULT: Application should install and run from any user-selected memory location correctly.
+After installation to the removable memory card, take another compliant clean phone or format the phone you have, and insert the memory card into the new/formatted phone.
++RESULT: The application should install automatically to the new/formatted phone or if the application is copy protected it provides suitablemessage to user indicating why it will not install.
++RESULT: The application should run correctly from the inserted memory card.

***Exception [#p7427381]
:UNI-09.EX1:Installation To All Storage Devices Not Intended|This exception can apply where it is not appropriate for an application to be installed on all mass memory devices. The application is expected to provide notification, warning or a mechanism to prevent installation on inappropriate mass storage devices; where no such mechanism is in place, it will be assumed that the application can be installed (and function correctly) on all mass memory devices.&br;&br;The application must states the memory device and/or the application is also prevented from being installed onto other memory devices (e.g. by hard-coding locations in the .PKG file to this effect).&br;&br;Valid reasons may include installer defects in complex situations, especially when attempting to upgrade ROM applications with a Partial Update (PU) type SIS file, or an unusually large application which may not be suitable for installation on the internal drive which may not be big enough on some phones.

**UNI-10 [#g7988201]
***Test Title [#k8a13051]
Scalable UI Compliance (S60 3rd Edition or UIQ3.x)

***Test Description [#y09717e5]
The application should function and render its display as specified, regardless of the device screen resolution and format.

***Estimated Test Time (minutes) [#i9d28886]
none

***Not Required for [#ka182831]
-Passive content
-Pre Symbian OS v9.x application

***Required for [#adcd302a]
-No Capabilities - Symbian OS v9.x
-ALL Symbian OS v9.x Capabilities

***Testing Notes [#ye80d6ea]
+To aid testing and access to different devices there are remote device testing solutions available for developers:-
++Nokia Remote Device Access:[[here>http://www.forum.nokia.com/main/technical_services/testing/rda_introduction.html]]
++Sony Ericsson Virtual Lab:[[here>http://developer.sonyericsson.com/site/global/products/virtuallab/p_virtual_lab.jsp]]

***Testing Steps [#h574e6ed]
If a device ID is identified in the PKG file the test should be carried out on all lead device/s as identified in the PKG file.&br;OR&br;If no device ID is specified in the PKG file, then the application should be tested on a lead device of all different screen resolutions for the version of S60 or UIQ user interface. &br;&br;A list of lead devices and screen resolutions is available at [[here>http://developer.symbian.com/wiki/display/sign/Scaleable+UI+Details]].

+Install to lead device for screen resolution type as identified in the PKG file.
+Start the application.
+Use the application normally through as many screens and scenarios as possible.
++RESULT: The application responds to orientation switch events appropriately, adjusting its display accordingly and continues to operate normally.
+++Provides its full functionality on all screen resolutions/orientations that are defined as supported within the application PKG file.
+++Uses the display area to its full extent.
+++Responds to orientation switch events appropriately, adjusting its display accordingly and continues to operate correctly, redrawing the screen properly.
++RESULT: If a flip or slider is present, upon moving the flip/slider:
+++[S60 applications only] the application adjusts accordingly between portrait and landscape orientation.
+++[UIQ applications only] the application adjusts its display accordingly and continues to operate normally. On closing the flip/slider, the application can return to the system default view.
+Exit the application.

***Exception [#ja9bed24]
:UNI-10.EX1:Not Testable . No User Interface|If the SIS file is supplying only shared libraries (DLLs) and/or system/middleware components with no user interaction (i.e. no user interface) then this test case is not required.
:UNI-10.EX2:Not a Generic Application|Application is intended for a specific device and User interface size only.
:UNI-10.EX3:Application Provides warning to user upon first startup|If an application fails this test, it may be granted an exception if it provides appropriate error message, e.g. “Screen Resolution Not Supported”, to the end user to indicate that the device's screen resolution is not supported


**UNI-11 [#h2e46f51]
***Test Title [#c0f6b3f4]
Correct Auto-start Behavior

***Test Description [#xb00d8ea]
Application must provide end user option to enable/disable automate application start up at the device boot.

***Estimated Test Time (minutes) [#z43bc5d6]
none

***Not Required for [#yeea3b1e]
-Passive content

***Required for [#a3d21b06]
-Pre Symbian OS v9.x application
-No Capabilities - Symbian OS v9.x
-ALL Symbian OS v9.x Capabilities

***Testing Notes [#s4d2f375]
none

***Testing Steps [#qd61b9f4]
+Start the application
+Close the application
+Turn off the test device and then turn back on
++RESULT: Upon restart the application does not start automatically by default.
+Start the application again
+Check the settings within the application that auto-start can be set to on/off.
++RESULT: There must be an ON/OFF setting available.
+Set auto-start to ON
+Turn off the test device and then turn back on
++RESULT: The test device starts up successfully.
+Start the application again
+Set auto-start to OFF
++RESULT: The user can disable auto-start successfully having enabled it previously.
+Turn off the test device and then turn back on
+Start the application again
++RESULT: The test device starts up successfully.

***Exception [#d53120cb]
:UNI-11.EX1:Functionality Not Present|An exception to this test case is granted to applications that do not provide auto-start functionality


トップ   新規 一覧 単語検索 最終更新   ヘルプ   最終更新のRSS   最終更新のRSS