Testing of Mobile Application

WHAT IS SOFTWARE TESTING?

Software testing is defined as an activity to check whether the actual results match the expected
results and to ensure that the software system is Defect free. It involves execution of a software
component or system component to evaluate one or more properties of interest.

Software testing also helps to identify errors, gaps or missing requirements in contrary to the
actual requirements. It can be either done manually or using automated tools. Some prefer saying
Software testing as a White Box and Black Box Testing.

In simple terms, Software Testing means Verification of Application Under Test (AUT).

Why is Software Testing Important?

Testing is important because software bugs could be expensive or even dangerous. Software
bugs can potentially cause monetary and human loss, and history is full of such examples..

 Nissan cars have to recall over 1 million cars from the market due to software failure in
the airbag sensory detectors. There has been reported two accident due to this software
failure.
 Starbucks was forced to close about 60 percent of stores in the U.S and Canada due to
software failure in its POS system. At one point store served coffee for free as they
unable to process the transaction.
 China Airlines Airbus A300 crashed due to a software bug on April 26, 1994, killing 264
innocent live

Types of Software Testing

Typically Testing is classified into three categories.

 Functional Testing
 Non-Functional Testing or Performance Testing
 Maintenance (Regression and Maintenance)

Department of Computer Applications Page 1

Testing of Mobile Application

MANUAL TESTING PROCESS

1.) Requirement Analysis

2.) Test Plan Creation

3.) Test Case Creation

4.) Test Case Execution

5.) Defect Logging

6.) Defect Fix & Re-verification

Department of Computer Applications Page 2

Testing of Mobile Application

1.) SOFTWARE REQUIREMENTS SPECIFICATION

(SRS)

A software requirements specification (SRS) is a document that contains complete description

about how the system is expected to perform. After completing, it is signed off at the end of
requirements. SRS review is nothing but going through the functional requirements specification
document and trying to understand what the target application is going to be like.

Challenges

 We cannot gather all information at one time

 Lots of discussion needed
 Sometimes the speed of discussion would be too fast or too slow to understand

Best Practice

 We should pay attention and listen carefully

 Keep note book or laptop for writing notes
 Draw diagram or rough block code for better understanding and for reference

2.) TEST PLAN CREATION

It’s a document developed by test manager. It is set of ideas that guides and is created to inform
all the managers, testers, developer about the testing process.

Test plan contains detailed understanding of workflow. It consist test templates which has
introduction, scope, test strategy, environment requirements, test schedule, functions to be tested,
resources and responsibilities, deliverables, suspension/ exit criteria, resumption criteria,
dependencies, risks, tools, documentation and approvals.

Department of Computer Applications Page 3

Testing of Mobile Application

3.) TEST CASE CREATION

A test case is a set of conditions or variables under which a tester will determine whether a
system under test satisfies requirements or works correctly.
The process of developing test cases can also help find problems in the requirements or design of
an application.

Test Case Template

Test Case ID The ID of the test case.

Test Case Name of the module for which test cases are written.
Module

Test Procedure Step-by-step procedure to execute the test.

Test Data The test data, or links to the test data, that are to be used while conducting
the test.

Expected The expected result of the test.

Result

Actual Result The actual result of the test; to be filled after executing the test.

Status Pass or Fail. Other statuses can be ‘Not Executed’ if testing is not
performed and ‘Blocked’ if testing is blocked.

Remarks Any comments on the test case or test execution.

Created By The name of the author of the test case.

Department of Computer Applications Page 4

Testing of Mobile Application

Date of The date of creation of the test case.

Creation

Executed By The name of the person who executed the test.

Date of The date of execution of the test.

Execution

Test The environment (Hardware/Software/Network) in which the test was

Environment executed.

4.) TEST CASE EXECUTION

Test execution is the process of executing the code and comparing the expected and actual
results.

Department of Computer Applications Page 5

Testing of Mobile Application

5.) DEFECT LOGGING

Defect logging/tracking is basically a continuous activity throughout the life cycle of a software
product. Testers and developers consistently look out for defects in the application may be
collecting facts from the users, or with the help of defect tracking tools.

Defect Tracking Parameters:

1. Defect Id - Lists each defect uniquely

2. Priority - Assigning priority to a defect on the basis of the degree of risk involved

3. Severity - Determines to what extent the defect can affect the system

4. Created By - The name of the person who has detected the defect

5. Created Date - The date on which the defect was captured

6. Assigned to - The person to whom the defect is reported for resolving it

7. Resolved Date - The date on which the defect is resolved

8. Resolved By - The team/person who resolved the defect

9. Status - Defect fixed or postponed (based on the severity of the defect)

Department of Computer Applications Page 6

Testing of Mobile Application

6.) DEFECT FIX AND RE-VERIFICATION

When all the bugs are fixed from the developer side, testing team started re-verification of the
bugs.

STATUS:

Status Alternative Status

NEW

ASSIGNED OPEN

DEFERRED

DROPPED REJECTED

COMPLETED FIXED, RESOLVED, TEST

REASSIGNED REOPENED

CLOSED VERIFIED

Department of Computer Applications Page 7