Common causes for failure during the Symbian Signed Test Process - Symbian Developer Network Public Wiki

Common Failures During Symbian Signed Testing

Symptom: Failure to complete "Declarative Statements" with complete and accurate information

Test Case Ref: CHECK-06

Solution: Should complete declarative statement information for all capabilities used during the submission process

Symptom: Uninstall does not remove all files that were created either during the installation of the application or during the execution of the application

Test Case Ref: UNI-08

Solution: Should ensure all files created on the device, during the installation or execution of the application, are removed on uninstall

Symptom: It should be possible to close an application using the Task Manager

Test Case Ref: UNI-05

Solution: Should ensure that app can be closed using Task Manager

Symptom: Using test range id for SID

Test Case Ref: CHECK-13

Solution: Submitter is using a SID from the list of "test" UIDs. The submitter should apply for a SID from the SDN

Symptom: Uninstall fails when the submitted application is open during the uninstall

Test Case Ref: UNI-08

Solution: Should go through all uninstall test cases listed in the Test Criteria

Symptom: Backup and restore compliance is not met

Test Case Ref: UNI-07

Solution: Submitter should test backup and restore functionality documented in the Test Criteria

Symptom: Submitted "zip" file is created with the path information

Test Case Ref: N/A

Solution: Submitter has used the "Save full path info" option when zipping up the files for submission

Symptom: Submitted files use a file name that is greater than 64 characters in length

Test Case Ref: N/A

Solution: The maximum length for submitted files is 64 characters

Recommended changes

These tests will not cause a failure in the process but should be fixed for any future submissions to the Symbian Signed Test Process.

Symptom: Dll names should include UID because all dlls share the sys/bin folder

Test Case Ref: CHECK-14

Cause: Submitter may not be aware of potential clashes

Solution: Submitter should include the UID in the dll name

Symptom: Include the correct UID in pkg file to ensure backwards compatibility

Test Case Ref: CHECK-09

Solution: Submitter should include relevant UIDs in pkg to ensure BC, these are documented in the Test Criteria document