An in depth study of mobile application testing in reference to real time scenario

An In-depth Study of Mobile Application
Testing in Reference to Real Time Scenario
Amit Aggarwal
QA Engineer
Sakshay Web Technologies Pvt. Ltd., Noida
amit.aggarwal@sakshay.in
amitaggarwal2151@gmail.com
Dr. Rabins Porwal
Associate Professor
Department of IT
Institute of Technology & Science (ITS)
Mohan Nagar, Ghaziabad, India
rabinsporwal@its.edu.in
ABSTRACT
Mobile Application Testing has become an integral part of the quality assurance of modern software’s. Software
Testing (Mobile Application Testing) is an important part of software engineering life cycle. Mobile Application
Testing requires the use of a model to guide such efforts as test selection and test verification. Being given a large
number of test cases can consume a great deal of time and resources, often ruling out their use in an interactive context.
This paper attempts to provide a comprehensive view of the field of Mobile Application Testing. The objective is to
pull all the relevant issues into a unified context, although admittedly the overview is biased toward our research and
expertise. In view of the vastness of the field, for each topic problems and approaches are only briefly tackled, with
appropriate references provided to dive into them. In this work efforts are not confined specifically on providing a
complete survey of Mobile Application Testing, rather to show how an unwieldy mix of theoretically and technical
problems challenge software testers and to identify the gap exists between the state-of-the-art and of the practice.
Keywords:
Testing, Mobile Application Testing, Errors, Bugs
1 SCOPE OF THE STUDY
1.1 Technical Scope
In this paper, the focus is on the technology maturation of Mobile Applications testing techniques, including functional
and structural testing techniques that have been influential in the academic world and widely used in practice. We are
going to examine the growth and propagation of the most established strategy and methodology used to select test cases
and analyse test results. Research in Mobile Application testing techniques can be roughly divided into two branches:
Theoretical and methodological, and the increase in both branches pushes the development of mobile application testing
technology together. Inhibitors of growth, which explains why the in-depth research hasn’t brought revolutionary
advantage in industry mobile application's testing practice, are also within our scope of involvement.
1.2 Goal and standard of progress
The ultimate goal of Mobile Application testing is to help App UI designers, developers, and managers construct
systems with high quality. Thus research and development on Mobile testing aim at efficiently performing effective
testing – to detect more errors in requirement, design and execution, and to increase confidence that the Mobile
Application has various qualities. Mobile Testing technique research leads to the destination of practical testing
methods and 3 tools. Progress toward this destination requires basic fundamental research, and the creation,
refinement/rectification, extension, and popularization of better strategies.
The standard of progress for the research of mobile application testing techniques includes:
 Degree of acceptance of the mobile application technology inside and outside the research community
 Degree of dependability on other areas of Mobile application software engineering
 Variety of research paradigms in response to the growth of mobile application development technologies.
 Feasibility of strategies being used in a widespread practical scope
 Spread of technology – classes, training's, management attention
2 INTRODUCTION

The testing of Mobile Application is an important means of assessing the mobile application to ensure its quality. Since
Mobile application testing typically consumes 40-50% of development/design efforts, and takes in more effort for
systems that need higher levels of trustworthiness, it is a important component of the mobile application software
technology. With the development of 4th generation languages (4GL), which speeds up the implementation process, the
remainder of time granted to testing increased.
Equally the quantity of maintenance and upgrade of existing systems grows, a substantial quantity of testing will also be
needed to verify systems after changes are produced. Despite advances in formal methods and confirmation techniques,
a system still needs to be examined before it is applied. Testing remains the truly efficient means to assure the caliber of
a mobile application software system of significant complexity, as well as one of the most complex and least
understood areas in software engineering. Mobile Application Testing is an important research field within computer
science is likely to become even more significant in the future.
2.1 The Psychology of Mobile Application Testing
One of the primary causes of poor program testing is the fact that most programmers begin with a false definition of the
term. They might say: “Mobile Application Testing is the process of demonstrating that errors are not present.” Or “The
purpose of Mobile Application testing is to show that a program performs its intended functions correctly.” Or “Mobile
Application Testing is the process of establishing confidence that application does what it is supposed to do.” These
definitions are upside-down.
When you test a Mobile Application, you want to add some value to it. Adding values through testing mean - Raising
the quality or reliability of the mobile application. Raising the reliability of the mobile application means finding and
removing errors.
Therefore, don’t test a Mobile Application to show that it works; rather, you should start with the assumption that the
Mobile Application contains errors (a valid Assumption for almost any Application) and then test the Application to
find as many of the errors as possible. Thus, a more appropriate definition is this:
“Mobile Application Testing is the process of executing an application on the mobile platform with the
intent of finding errors.”
2.2 The Economics of Testing
Given the above definition of mobile application testing, an appropriate next step is the determination of whether it is
possible to test an application to find all of its errors. We will show you that the answer is negative, In general, it is
impractical, often impossible, to find all the errors in a mobile application. This fundamental problem has implications
for the economics of testing, assumptions that the tester will have to make about the mobile application, and the manner
in which test cases are designed.
2.3 Principles of Software Testing [14] (Including Mobile Application)
A number of testing principles have been suggested over the past 40 years and offer general guidelines common for all
testing including Mobile Application testing.
 Principle 1 - Testing shows presence of defects
Testing can show that defects are present, but cannot prove that there are no defects. Testing reduces the
probability of undiscovered defects remaining in the software but, even if no defects are found, it is not a proof of
correctness.
 Principle 2 - Exhaustive testing is impossible
Testing everything (all combinations of inputs and preconditions) is not feasible except for trivial cases. Instead of
exhaustive testing, risk analysis and priorities should be used to focus testing efforts.
 Principle 3 - Early testing
To find defects early, testing activities shall be started as early as possible in the software or system development
life cycle, and shall be focused on defined objectives.
 Principle 4 - Defect clustering
Testing effort shall be focused proportionally to the expected and later observed defect density of modules. A
small number of modules usually contains most of the defects discovered during pre-release testing, or is
responsible for most of the operational failures.
 Principle 5 - Pesticide paradox
If the same tests are repeated over and over again, eventually the same set of test cases will no longer find any new
defects. To overcome this "pesticide paradox", test cases need to be regularly reviewed and revised, and new and
different tests need to be written to exercise different parts of the software or system to find potentially more
defects.
 Principle 6 - Testing is context dependent
Testing is done differently in different contexts. For example, safety-critical software is tested differently from an
e-commerce site.
 Principle 7 - Absence-of-errors fallacy
Finding and fixing defects does not help if the system built is unusable and does not fulfil the users' needs and
expectations.
2.4 Where exactly Mobile Application Testing comes in to picture?

In the software Industries testing is comes during the development of project there are two types of testing which are
done at the testing phase of SDLC. These types of testing are as following:
2.4.1 Conventional Testing
It is sort of testing in which one will check the developed mobile applications or its related parts are working according
to the exceptions or not, from the Coding phase to the end. It can referred as prevention activity. The various validation
strategies will be used in these testing. It is done by Test Engineers to check whether the developed mobile application
is working fine as per the requirements.
2.4.2 Unconventional Testing
It is sort of testing in which the Quality assurance people will check each and every outcome document is according to
the company standards or not right from the Initial phase to the end.
Unconventional testing is a verification process performed by developers along with the QA Engineers. Various
verification techniques will be used like:
1) Analysis Reviews
2) Design Reviews
3) Code Walkthroughs
4) Code Inspections.
3 THE TAXONOMY OF TESTING TECHNIQUES
Software testing is a very broad area, which involves many other technical and non-technical areas, such as
specification, design and implementation, maintenance, process and management issues in software engineering. Our
study focuses on the state of the art in Mobile application testing techniques, as well as the latest techniques which
representing the future direction of this area. Before stepping into any detail of the maturation study of these techniques,
let us have a brief look at some technical concepts that are relative to our research.
3.1 The Goal of Testing
In different articles, the definition of testing varies according to the purpose, process, and level of testing described.
Miller gives a good description of testing: The general aim of testing is to affirm the quality of software systems by
systematically exercising the software in carefully controlled circumstances.
Miller’s description of testing views most software quality assurances activities as testing. He contends that testing
should have the major intent of finding errors. A good test is one that has a high probability of finding an as yet
undiscovered error, and a successful test is one that uncovers an as yet undiscovered error.
This general category of software testing activities can be further divided. For purposes of this paper, testing is the
dynamic analysis of a piece of software, requiring execution of the system to produce results, which are then compared
to expected outputs.
3.2 The Testing Spectrum
Testing is involved in every stage of software life cycle, but the testing done at each level of software development is
different in nature and has different objectives.
3.2.1 Unit Testing
Unit Testing is done at the lowest level. It tests the basic unit of software, which is the smallest testable piece of
software, and is often called “unit”, “module”, or “component” interchangeably.
3.2.2 Integration Testing
Integration Testing is performed when two or more tested units are combined into a larger structure. The test is often
done on both the interfaces between the components and the larger structure being constructed, if its quality property
cannot be assessed from its components.
3.2.3 System Testing
System Testing tends to affirm the end-to-end quality of the entire system. System test is often based on the
functional/requirement specification of the system. Non-functional quality attributes, such as reliability, security, and
maintainability, are also checked.
3.2.4 Acceptance Testing
Acceptance Testing is done when the completed system is handed over from the developers to the customers or users.
The purpose of acceptance testing is rather to give confidence that the system is working than to find errors.
3.3 Static Analysis and Dynamic Analysis
Based on whether the actual execution of software under evaluation is needed or not, there are two major categories of
quality assurance activities:
3.3.1 Static Analysis
Static Analysis focuses on the range of methods that are used to determine or estimate software quality without
reference to actual executions. Techniques in this area include code inspection, program analysis, symbolic analysis,
and model checking.
3.3.2 Dynamic Analysis

Dynamic Analysis deals with specific methods for ascertaining and/or approximating software quality through actual
execution, i.e. with real data and under real (or simulated) circumstances. Techniques in this area include synthesis of
inputs, the use of structurally dictated testing procedures, and the automation of testing environment generation.
Generally the static and dynamic methods are sometimes inseparable, but can almost always discuss separately. In this
paper, we mean dynamic analysis when we say testing, since most of the testing activities (thus all the techniques
studied in this paper) require the execution of the software.
3.4 Functional Technique and Structural Technique
Figure 1: Information Flow of Software Testing
The information flow of testing is shown in Figure 1. As we can see, testing involves the configuration of proper inputs,
execution of the software over the input, and the analysis of the output. The “Software Configuration” includes
requirements specification, design specification, source code, and so on. The “Test Configuration” includes test cases,
test plan and procedures, and testing tools.
Based on the testing information flow, a testing technique specifies the strategy used in testing to select input test cases
and analyze test results. Different techniques reveal different quality aspects of a software system, and there are two
major categories of testing techniques, functional and structural.
3.4.1 Functional Testing
The software program or system under test is viewed as a “black box”. This selection of test cases for functional testing
is based on the requirement or design specification of the software entity under test. Examples of expected results,
sometimes are called test oracles, include requirement/design specifications, hand calculated values, and simulated
results. Functional testing emphasizes on the external behavior of the software entity.
3.4.2 Structural Testing
The software entity is viewed as a “white box”. The selection of test cases is based on the implementation of the
software entity. The goal of selecting such test cases is to cause the execution of specific spots in the software entity,
such as specific statements, program branches or paths. The expected results are evaluated on a set of coverage criteria.
Examples of coverage criteria include path coverage, branch coverage, and data-flow coverage. Structural testing
emphasizes on the internal structure of the software entity.
4 MOBILE APPLICATION TESTING
Functional Testing:
The functional testing of Mobiles normally consists in the areas of testing user interactions as well as testing the
transactions. The various factors which are relevant in functional testing are:
1. Type of application based upon the business functionality usages (banking, gaming, social or business)
2. Target audience type (consumer, enterprise, education)
3. Distribution channel which is used to spread the application (e.g. Apple App Store, Google play, direct
distribution)
The most fundamental test scenarios in the functional testing can be considered as:
1. To validate whether all the required mandatory fields are working as required.
2. To validate that the mandatory fields are displayed in the screen in a distinctive way than the non-mandatory
fields.
3. To validate whether the application works as per as requirement whenever the application starts/stops.
4. To validate whether the application goes into minimized mode whenever there is an incoming phone call. In
order to validate the same we need to use a second phone, to call the device.
5. To validate whether the phone is able to store, process and receive SMS whenever the app is running. In order
to validate the same we need to use a second phone to send sms to the device which is being tested and where
the application under test is currently running.

6. To validate that the device is able to perform required multitasking requirements whenever it is necessary to
do so.
7. To validate that the application allows necessary social network options such as sharing, posting and
navigation etc.
8. To validate that the application supports any payment gateway transaction such as Visa, Mastercard, Paypal
etc as required by the application.
9. To validate that the page scrolling scenarios are being enabled in the application as necessary.
10. To validate that the navigation between relevant modules in the application are as per the requirement.
11. To validate that the truncation errors are absolutely to an affordable limit.
12. To validate that the user receives an appropriate error message like "Network error. Please try after some
time" whenever there is any network error.
13. To validate that the installed application enables other applications to perform satisfactorily and it does not eat
into the memory of the other applications.
14. To validate that the application resumes at the last operation in case of a hard reboot or system crash.
15. To validate whether the installation of the application can be done smoothly provided the user has the
necessary resources and it does not lead to any significant errors.
16. To validate that the application performs auto start facility according to the requirements.
17. To validate whether the application performs according to the requirement in all versions of Mobile that is 2g,
3g and 4g.
18. To perform regressions testing to uncover new software bugs in existing areas of a system after changes have
been made to them. Also rerun previously performed tests to determine that the program behavior has not
changed due to the changes.
19. To validate whether the application provides an available user guide for those who are not familiar to the app
Performance testing:
This type of testing's fundamental objective is to ensure that the application performs acceptably under certain
performance requirements such as access by a huge number of users or the removal of a key infrastructure part like a
database server.
The general test scenarios for performance testing in a Mobile application are:
1. To determine whether the application performs as per the requirement under different load conditions.
2. To determine whether the current network coverage is able to support the application at peak, average and
minimum user levels.
3. To determine whether the existing client-server configuration setup provides the required optimum
performance level.
4. To identify the various application and infrastructure bottlenecks which prevent the application to perform at
the required acceptability levels.
5. To validate whether the response time of the application is as per as the requirements.
6. To evaluate product and/or hardware to determine if it can handle projected load volumes.
7. To evaluate whether the battery life can support the application to perform under projected load volumes.
8. To validate application performance when network is changed to WIFI from 2G/3G or vice versa.
9. To validate each of the required the CPU cycle is optimization
10. To validate that the battery consumption, memory leaks, resources like GPS, Camera performance is well
within required guidelines.
11. To validate the application longevity whenever the user load is rigorous.
12. To validate the network performance while moving around with the device.
13. To validate the application performance when only intermittent phases of connectivity is required.
Security testing:
The fundamental objective of security testing is to ensure that the application's data and networking security
requirements are met as per guidelines.
The following are the most crucial areas for checking the security of Mobile applications:
1. To validate that the application is able to withstand any brute force attack which is an automated process of
trial and error used to guess a person's username, password or credit-card number.
2. To validate whether an application is not permitting an attacker to access sensitive content or functionality
without proper authentication.
3. To validate that the application has a strong password protection system and it does not permit an attacker to
obtain, change or recover another user's password.
4. To validate that the application does not suffer from insufficient session expiration.
5. To identify the dynamic dependencies and take measures to prevent any attacker for accessing these
vulnerabilities.
6. To prevent from SQL injection related attacks.
7. To identify and recover from any un-managed code scenarios.
8. To ensure whether the certificates are validated, does the application implement Certificate Pinning or not.
9. To protect the application and the network from the denial of service attacks.
10. To analyze the data storage and data validation requirements.
11. To enable the session management for preventing unauthorized users to access unsolicited information.

12. To check if any cryptography code is broken and ensure that it is repaired.
13. To validate whether the business logic implementation is secured and not vulnerable to any attack from
outside.
14. To analyze file system interactions, determine any vulnerability and correct these problems.
15. To validate the protocol handlers for example trying to reconfigure the default landing page for the
application using a malicious frame.
16. To protect against malicious client side injections.
17. To protect against malicious runtime injections.
18. To investigate file caching and prevent any malicious possibilities from the same.
19. To prevent from insecure data storage in the keyboard cache of the applications.
20. To investigate cookies and preventing any malicious deeds from the cookies.
21. To provide regular audits for data protection analysis.
22. Investigate custom created files and preventing any malicious deeds from the custom created files.
23. To prevent from buffer overflows and memory corruption cases.
24. To analyze different data streams and preventing any vulnerabilities from these.
Usability testing:
The usability testing process of the Mobile application is performed to have a quick and easy step application with less
functionality than a slow and difficult application with many features. The main objective is to ensure that we end up
having an easy-to-use, intuitive and similar to industry-accepted interfaces which are widely used.
1. To ensure that the buttons should have the required size and be suitable to big fingers.
2. To ensure that the buttons are placed in the same section of the screen to avoid confusion to the end users.
3. To ensure that the icons are natural and consistent with the application.
4. To ensure that the buttons, which have the same function should also have the same color.
5. To ensure that the validation for the tapping zoom-in and zoom-out facilities should be enabled.
6. To ensure that the keyboard input can be minimized in an appropriate manner.
7. To ensure that the application provides a method for going back or undoing an action, on touching the wrong
item, within an acceptable duration.
8. To ensure that the contextual menus are not overloaded because it has to be used quickly.
9. To ensure that the text is kept simple and clear to be visible to the users.
10. To ensure that the short sentences and paragraphs are readable to the end users.
11. To ensure that the font size is big enough to be readable and not too big or too small.
12. To validate the application prompts the user whenever the user starts downloading a large amount of data
which may be not conducive for the application performance.
13. To validate that the closing of the application is performed from different states and verify if it re-opens in the
same state.
14. To ensure that all strings are converted into appropriate languages whenever a language translation facility is
available.
15. To ensure that the application items are always synchronized according to the user actions.
16. To ensure that the end user is provided with a user manual which helps the end user to understand and operate
the application who may be not familiar with the application's proceedings
Usability testing is normally performed by manual users since only human beings can understand the sensibility and
comfort ability of the other users.
Compatibility testing:
Compatibility testing on mobile devices is performed to ensure that since mobile devices have different size,
resolution, screen, version and hardware so the application should be tested across all the devices to ensure that the
application works as desired.
The following are the most prominent areas for compatibility testing.
1. To validate that the user Interface of the application is as per the screen size of the device, no text/control is
partially invisible or inaccessible.
2. To ensure that the text is readable for all users for the application.
3. To ensure that the call/alarm functionality is enabled whenever the application is running. The application is
minimized or suspended on the event of a call and then whenever the call stops the application is resumed.
Recoverability Testing
1. Crash recovery and transaction interruptions
2. Validation of the effective application recovery situation post unexpected interruption/crash scenarios.
3. Verification of how the application handles a transaction during a power failure (i.e. Battery dies or a sudden
manual shutdown of the device)
4. The validation of the process where the connection is suspended, the system needs to re-establish for
recovering the data directly affected by the suspended connection.
Other Important Checks:

1. Installation testing (whether the application can be installed in a reasonable amount of time and with required
criterion)
2. Uninstallation testing (whether the application can be uninstalled in a reasonable amount of time and with
required criterion)
3. Network test cases (validation of whether the network is performing under required load or not, whether the
network is able to support all the necessary applications during the testing procedures)
4. Check unmapped eys
5. Check application splash screen
6. Continued keypad entry during interrupts and other times like network issues
7. Methods which deal with exiting the application
8. Charger effect while an application is running in the background
9. Low battery and high performance demand
10. Removal of battery while an application is being performed
11. Consumption of battery by application
12. Check Application side affects
5 MOBILE APPLICATION PERFORMANCE TESTING
Performance testing is a type of testing intended to determine the responsiveness, throughput, reliability, and/or
scalability of a system under a given workload. Performance testing is commonly conducted to accomplish the
following:
 Assess production readiness
 Evaluate against performance criteria
 Compare performance characteristics of multiple systems or system configurations
 Find the source of performance problems
 Support system tuning
 Find throughput levels
5.1 Core Activities of Performance Testing
Performance testing is typically done to help identify bottlenecks in a system, establish a baseline for future testing,
support a performance tuning effort, determine compliance with performance goals and requirements, and/or collect
other performance-related data to help stakeholders make informed decisions related to the overall quality of the
application being tested. In addition, the results from performance testing and analysis can help you to estimate the
hardware configuration required to support the applications when you “go live” to production operation.
Figure 2: Core Activities of Performance Testing
The performance testing approach used in this guide consists of the following activities:
 Activity 1. Identify the Test Environment: Identify the physical test environment and the production
environment as well as the tools and resources available to the test team. The physical environment includes
hardware, software, and network configurations. Having a thorough understanding of the entire test environment at
the outset enables more efficient test design and planning and helps you identify testing challenges early in the
project. In some situations, this process must be revisited periodically throughout the project’s life cycle.

 Activity 2. Identify Performance Acceptance Criteria: Identify the response time, throughput, and resource
utilization goals and constraints. In general, response time is a user concern, throughput is a business concern, and
resource utilization is a system concern. Additionally, identify project success criteria that may not be captured by
those goals and constraints; for example, using performance tests to evaluate what combination of configuration
settings will result in the most desirable performance characteristics.
 Activity 3. Plan and Design Tests: Identify key scenarios, determine variability among representative users and
how to simulate that variability, define test data, and establish metrics to be collected. Consolidate this information
into one or more models of system usage to be implemented, executed, and analysed.
 Activity 4. Configure the Test Environment: Prepare the test environment, tools, and resources necessary to
execute each strategy as features and components become available for test. Ensure that the test environment is
instrumented for resource monitoring as necessary.
 Activity 5. Implement the Test Design: Develop the performance tests in accordance with the test design.
 Activity 6. Execute the Test: Run and monitor your tests. Validate the tests, test data, and results collection.
Execute validated tests for analysis while monitoring the test and the test environment.
 Activity 7. Analyse Results, Report, and Retest: Consolidate and share results data. Analyse the data both
individually and as a cross-functional team. Reprioritize the remaining tests and re-execute them as needed. When
all of the metric values are within accepted limits, none of the set thresholds have been violated, and all of the
desired information has been collected, you have finished testing that particular scenario on that particular
configuration.
6 CONCLUSION
Mobile Application Testing has been widely used as a way to help engineers develop high-quality mobile applications,
and the techniques for mobile application testing have evolved from ad-hoc activities means of small group of
programmers to an organized discipline in software engineering. However, the maturation of mobile application testing
techniques has been fruitful, but not adequate. Pressure to produce higher-quality mobile applications at lower cost is
increasing and existing techniques used in practice are not sufficient for this purpose. Fundamental research that
addresses the challenging problems, development of methods and tools, and empirical studies should be carried out so
that we can expect significant improvement in the way we test mobile applications. Researchers should demonstrate the
effectiveness of many existing techniques for large industrial mobile applications, thus facilitating transfer of these
techniques to practice. The successful use of these techniques in industrial software development will validate the
results of the research and drive future research. The pervasive use of mobile applications and the increased cost of
validating it will motivate the creation of partnerships between industry and researchers to develop new techniques and
facilitate their transfer to practice. Development of efficient testing techniques and tools that will assist in the creation
of high-quality mobile applications will become one of the most important research areas in the near future.
REFERENCES
[1] G. Bernet, L. Bouaziz, and P. LeGall, “A Theory of Probabilistic Functional Testing,” Proceedings of the 1997
International Conference on Software Engineering, 1997, pp. 216 –226
[2] S. Beydeda and V. Gruhn, “An integrated testing technique for component-based software,” ACS/IEEE
International Conference on Computer Systems and Applications, June 2001, pp 328 – 334
[3] D. Gelperin and B. Hetzel, “The Growth of Software Testing”, Communications of the ACM, Volume 31 Issue 6,
June 1988, pp. 687-695
[4] E. F. Miller, “Introduction to Software Testing Technology,” Tutorial: Software Testing & Validation Techniques,
Second Edition, IEEE Catalog No. EHO 180-0, pp. 4-16
[5] J. A. Whittaker, “What is Software Testing? And Why Is It So Hard?” IEEE Software, January 2000, pp. 70-79
[6] Whittaker, J. A. 2000. What is Software Testing? And Why is it so hard? IEEE Software, v.17 No.1, pp.70-79.
[7] Stout, G.A. 2001. Testing a Website: Best Practices. Retrieved from the World Wide Web:
http://www.reveregroup.com/exchange/articles/stout2.pdf
[8] Gerrard, P. (2000a). Risk-Based E-Business Testing: Part 1 – Risks and Test Strategy.URL-
http://www.evolutif.co.uk/articles/EBTestingPart1.pdf
[9] Manual Testing Help eBook by http://sotwaretestinghelp.com/
[10] Hagen, M. (2000). Performance Testing E-Commerce Web Systems Presentation Paper. URL-
http://www.stickyminds.com/docs_index/XDD2070filelistfilename1.doc
[11] Mobile Testing Tutorials for the real scenarios,A Complete guide to test your mobile Application URL-
http://www.guru99.com/mobile-testing.html
[12] SOFTWARE TEST ENGINEERING (PCSR) softwaretestengineeringmanualtesting-110730124458-phpapp02.pdf
[13] Crispin, L. (2001). Stranger in a Strange Land: Bringing QA to a Web Start-up. URL-
http://www.stickyminds.com/docs_index/XUS247559file1.doc
[14] Foundation of Software Testing ISTQB CERTIFICATION, e-book by Dorothy Graham, Erik van Veenendaal,
Isabel Evans & Rex Black

An in depth study of mobile application testing in reference to real time scenario

Recommended

More Related Content

What's hot (16)

Similar to An in depth study of mobile application testing in reference to real time scenario (20)

Recently uploaded (20)

An in depth study of mobile application testing in reference to real time scenario