Mobile Testing Practical

Testing Team - Roles  Sanity Team/Build Generate 1FF(Build) using Component Labels, KJava Packs, Flex File and then test for the Basic functionalities like Power Up, check for the working of all the features.  Integration Team Testing with one level Interaction of all features.  System Test Team Multiple Interaction. We will see more about the roles of System Test in the next few slides.  Field Test Team Testing on the move.  Interoperability Team Testing the compatibility of the phone with other devices/products.

1

System Test – Roles and Responsibilities  Test Case Execution  Test Case Development and Validation  Test Case Automation

2

Test Case - Execution 

 

 

Manual Test Case Execution phase, involves Normal and Exploratory Testing which covers feature & feature interaction testing (Functionality Testing). We are using GSM/GPRS network for testing these features. Due to current Network limitations, 3G related features will be tested in places where 3G network is available. We test features like Browser, MMS, Email, UPA, Games, Connectivity, IM, Security, Themes, Syncml along few other basic features like Messaging, Multimedia, and Telephony. Test Cases will be allocated to the Test Engineers, and Executed Results will be updated in the Test Central by the Test Engineers. The defects found out during testing are logged in DDTS, centralized database as CR, with the relevant severity & priority. The logged defects are tracked until it gets fixed appropriately. Products will be tested under different cycle plans like Pre STRR, ST-1, ST-2, Macro regression, Micro regression, Soak Regression and bug fix cycle till Shipment Acceptance(SA). Proprietary tools like RSD Lite, MiniFlexTool, RTA are used for flashing, flexing, and datalogging. 3

Execution – Roles and Responsibilities  Bug tracking and reporting in Dynamic Defect Tracking System (DDTS).  Testing features like Browser, MMS, Email, UPA, Connectivity, IM, Security, Themes, SyncML and few other basic features like Messaging, Multimedia, Telephony and Games.  Interacting with the Client for reporting and issue discussion frequently through IM and Tele Conference.  Preparing the performance metrics of the team on a Monthly basis (on a rotation basis).  Update the team on New Tools and Upcoming Features in your feature areas. 4

Test Case Development 

Testcase Development activity includes Test Case Development and Validation. During the starting phase, the developer will be assigned with a new feature for which Test Cases needs to be developed. New Work CR will be raised for the Assigned Feature. Number of Test Cases will be Estimated by the Developer after analyzing the SUIS/TRS and will be updated in the New Work Development CR after getting the approval from FA Lead. Test Case Design Document, which covers the all the States and Events, will be prepared by the Testcase developer using FI Matrix Tool including all the Requirements mentioned in TRS. Prepared Document will be sent to the FA Lead for Approval. FA Lead will Sign-off the Document, if no changes are required.



During the Next Phase, Test Cases will be developed based on the Test Case Design Document. Developed Test Cases will be reviewed internally within the Team. The Test Cases, if required, will be modified based on the Internal Review, and will be sent to the FA Lead for Review and Approval. Based on the final review comments, if required, the test cases will be modified, and moved to the Production Branch from the Development Branch. Finally, the New Work CR will be moved to closed state.

5

Test Case - Validation  The next phase of Development will be validating the developed Test Cases. A Validation CR will be raised for validating the Test Cases Developed. Test Cases developed based on the SUIS/TRS will be validated in the Testing Phones. Validator will raise a Testware CR after getting the approval from the Test Case Developer, in case, if modification is required in the Test Case. A product CR will be raised by the Validator if a defect is found in the Software during the Validation Phase. Finally, the Validation CR will be moved to closed state. 6

Development/Validation – Roles and Responsibilities  Analysis of SUIS/TRS for the new feature and estimation of test case to be developed.  Preparation of Test case Design document for the new feature.  Developing test cases for the identified new feature.  Involved in Reviews and Inspections for test cases developed for the new feature.  Validating the new feature, once it gets implemented on the product. 7

Test Case - Automation  

  

System test automation phase involves Analysis, Scripts Development & Maintenance. During initial phase, the TRS/TestPlan/TestCase is analyzed for the feasibility of automation on the grounds of complexity, time required for execution, repeatability and maintainability of scripts. Once the Analysis Report is approved by our Project Lead, then the Test Cases will be picked up for Automation. Next Phase starts with script development which includes Coding, Validation, Inspection, Inspection rework and Final Release. The released scripts are to be run using automation tool like PTF & STAT. Types of testing conducted during automation execution process are Regression Testing, Stress Testing, Stability Testing and Performance Testing. Using STAT, Test cases will be picked up from Test Central and Results will be entered accordingly. From the logs provided by STAT, the Test Engineer will analyze, and report the bugs found out, if any, in DDTS with relevant severity & priority. The logged bugs are tracked until it gets closed appropriately.

8

Automation – Roles and Responsibilities  Validating and executing the test scripts using PTF and STAT automation tool.  Analyzing the failure of the scripts from the logs provided by STAT Tool.  Involved in executing the test scripts by conducting Stress testing, Stability testing and Performance testing on the product.  Interacting with client for issue discussion and reporting bugs on weekly basis by either Tele Conference or Net meeting. 9

Metrics  Escape Defect Analysis  Phase Screening Efficiency

10

 Thank You - Murugan A.

11