Test Plan for a mobile applications

Test Plan for a mobile applications

Introduction or Overview: Here we will discuss and describe about the methodology of mobile application testing, and it to be use as the guide for the activity of testing.

The intended audience for this content are: The Project Manager, Product Developers and members of Test Team.

Now what is the Scope:

The testing scope as describe in the doc is for testing the operating characteristic of an app that execute on the mobile device supporting the J2ME. The test is organized by the category requirement such as the usability, security, functionality etc. The procedures for the carrying out the testing in the term of preparations of the test case, Test environments setup, defect log and report are described.

The article doesn't point the following:

• Censorship of content for the purpose of ignoring the deployment or the sale of any applications. Distribution, DRM etc.
• Testing requirement specific to the particular manufacturer user interface, devices, and the standard implementation like WAP.

=> Mentioning the Document reference

• Acronyms
  Acronym Expansion
  DRM Digital Right Management
  J2ME JAVA 2 Platform Micro Edition

Test Plan for a mobile applications

2 → Test Plan and The Strategy:

2.1 Unit Testing
2.1.1 Objective of this Testing
The main motto of this unit testing is to validate that a specific module of any source code is working properly or not mean the testing of any one unit of any mobile application.

2. → Entry Criteria:
   - Test Cases Reviewed
   - Self Test and Build is completed or Done
   - Set up the unit testing environments

2. Criteria for Exit:
   - All Test cases executed as planned
   - Unit Testing result is matching with Expected result
   - found issues fixed by code and tracked as closure

2. Test and Reporting Log:
   The Developers will fix the bugs that found in the this unit testing. Additionally if bugs corresponding to another module or the component are found then during unit testing, these bugs also will be reported to the related development teams.
   2.2 System Testing:
   Now in System Testing, All Separate unit will be tested in the integration of one unit. The purpose or the motto of this testing is to test the system in the merged application and complete application is working fine in the co operation of all component of units. On this stage the verification of the system contains → usability, installation, security, functionality etc. It is the intended to verify the app as in a whole system.

The remained doc mainly explain how system testing is processed by the team of testing.

1. Procedure of Testing:
   Testing steps contains:
   - All possible Test Cases and the Test Scenarios need to create
   - Preparations of test case doc that have a brief descriptions of the test cases, Step to conduct test and the expected result
   - Defect the Report generation.

Outline below are the main type of test that will be perform

a. AC – Application Characteristic → Information related to the apps is given to the testing team for help in the work of testing.

b. ST-Stability → Targeting on the app being stable on the available devices.

100. AL-Application Launch → Once app is loaded it should execute and stop correctly in the relation to the devices and another application on the devices.

500. UI-User Interface:

e. FN-Functionality → Document feature are applied in the app and work done as in expected way. Source for info are users formatted application specification document, manuals and the online documentation.

f. CO-Connectivity → The app must demonstrates it's capability to communicate over a network perfectly. It should be capable of dealing with the both network problem and the server side problem.

g. PI-Personal Information Management → The App accessing user information requires to be capable to do it an appropriate manner and not to destroy the records.

h. Security

3. Regression Testing:
   This is an additional step and require to complete prior to complete the system testing which is to test the new functionality. Regression test cases contains of executing a set of standard test cases to confirm that the old functional has not broken by this newly added functionality. Regression Test Cases are also execute if a newly release is made after fixing the multiple found bugs.
4. Conditions for Pass or Fail: Is is called expected result where an application pass the decided test cases, By this way application should pass all the test cases to pass or if not pass then it called Fail.
5. Testing Report Template:
   For all type of report, The following record is given like the Name of Application
   - The application version number
   - Which devices are used for testing
   - Firmware Version for used devices
   - Occurrence of error and its Frequency
   - Location of the bug – where is the error in application
   - Step how the issue can be reproducible

3. Schedules for The Testing:

This decision under the consultation with the manager of project.

4. Assumptions and Risks:
   Risks:
   - Availability of Devices
   - New Features Modifications or Additions in the apps which is not the communicate in Advance
   - Any Type of Delay under the Delivery of Software schedule containing defect fix. All change in the functionality requirement since the requirement was signed off or formulate.
   Assumptions:
   - Every Release for Quality Analyst will co-operate the release note specifying detail of the feature implemented and its impact on the modules under testing.
   - All Show stopper issues get immediately attention from the developers team
   - All defects found in the versions of software will be solved and testing of unit will be done by the developers before the release of next version.
   - Complete documentation will be up to date and will be provided to test team of system.
   - Emulators, Devices and the another supporting tool will by fully functional prior to the commencement of project.
   - If there is lack of mandatory equipment or the change in the feature requirement, then the test scheduled may require to be review.
5. Entry and the Exit Criteria:
   Entry Criteria:
   - Developer work of the app is completely
   - Successful completion of the unit test for the apps
   - Release of the current software for the environment of test
   - Allocated the dedicated resource
   - Test cases approval, test bed to bring out system testing.
   - Testing environment is set up and working properly

Exit Criteria:
- When all the tests are run and at least 95% are passed successfully. The remained test cases don't impact critical functionality.
- All Test cases result or output will be evaluated and then accepted.
- There are not any showstopper or high criticality defect unresolved or outstanding.
4. Test Metrics:
   - Report for Summary
   - Effort for Test Design
   - Effort for Test execution
   - Test Case execution number
   - Numbers if bugs and their categorizations
   - Test Coverage metrics
5. Logging the Test Cases and The Reporting:
   Here third party apps will be use for the report the issues catching in the execution of test cases. The team of Test engineer or QA will log the bugs in the tool as the progress of Testing.
6. Responsibilities and the Roles:
   The Responsibilities and the roles of the team of testing for the project are given below:
   - Responsibilities of Project Manager or Test Manager
   → Overall Testing Process management
   → Test document approval
   → Test Plan Inspection approval
   → Giving the resource for the available current project
   - Test Lead Responsibilities:
   → Gathering the Requirement
   → Estimating and the Planing for The Testing
   → Monitoring and Tracking the Test cases as per the Test Plan
   → Reporting the status of Project
   - Test Engineer Responsibilities:
   → According to Test Plan creating the test Cases
   → Now Executing the Test Cases
   → Documentation the Result and the Errors logging
7. Project Deliverables:
   - Test Plan
   - Documentation of Test Cases
   - Test Result with the Pass or Fail status of each test case and the list of bugs.

MOBILE APPS    QTP TESTING QUESTIONS  MANUAL TESTING  ANDROID APPS