Porting and Handset Compatibility

Wirkle has considerable experience in porting and doing handset compatibility testing for mobile applications. We have tested and ported applications using tools such as Device Anywhere (www.deviceanywhere.com) as well as in house handsets. A typical porting/handset compatibility exercise tests spans:

1. Preparation of test cases: A test case document (excel sheet) is updated that details out all the test cases relevant for the stage. It contains all information related to test case such as objective, priority, steps to be taken, expected and actual results as well as any test data.

2. Preparation of the Handset Compatibility Matrix: This document is intended to provide a one snapshot view of the features of the application and the handsets that those features work / do not work on.

3. Test case / Matrix review: The test case document and the handset compatibility matrix is reviewed to ensure that all possible test scenarios / features are covered.

4. Test case execution: Reviewed test cases are now executed on pre-specified handsets. The following steps are followed (a) bugs will be filed in a defect tracking tool such as bugzilla for all failed test cases and are also recorded in the test report for every handset, (b) weekly review meetings are conducted to gauge progress and discuss the bugs found and their impact.

5. Handset Test Report: After execution of all test cases, test report for each handset is updated and all related information like software release number, build number, test id, bug id, result is recorded.

6. Retesting: If a patch release is created to fix critical bugs, the test cases required to verify those fixes are re-executed and the result is reviewed; repeating this until all critical bugs are resolved.

7. Regression Testing: Regression of high priority test cases is done with a single handset of each family. Regression is executed again if bugs are found and are fixed.

8. Updated Test Reports: Result of all test cases which are executed in re-testing and regression testing is recorded in further cycles of test report.

9. Test Summary Report: At the end of a stage a summary report is maintained which summarizes the number of test cases that are executed, passed, failed and re-tested for individual handsets, which helps to review frequency of bugs in the testing process.

10. Updated Handset Compatibility Matrix: Compatibility matrix is updated to give a one snapshot view of the test results.