This document discusses using exploratory testing with risk analysis for mobile applications. It begins with an introduction to exploratory testing and risk-based testing. It then explains how blending exploratory testing with risk analysis provides structure and prioritizes testing areas of high risk. The document provides an example approach, discussing identifying risks and conducting exploratory tests on risky areas. It describes how exploratory testing is useful for mobile applications given their complexity. Finally, it covers pros and cons of exploratory testing and concludes that combining it with other techniques can improve test coverage and reduce risks.

1. Archana Krushnan, Test Analyst
Nihilent Technologies Pvt Ltd
1
Exploratory Testing explored using
Risk Analysis for Mobile Applications

2. Agenda
 Introduction
 Blend of Exploratory Testing along with Risk based Analysis
 Need for Risk based Exploratory Testing in Mobile applications.
 Approach to Exploratory Testing in any Application using Risk analysis
 How is Exploratory testing useful in Mobile applications?
 Pros and Cons
 Conclusion
2

3. Introduction
• Testing approach that can be described as simultaneous learning, test
design and test execution.
• “Think Different” every time we do exploratory testing.
• Scripted testing alone often fails to find hidden defects.
• It incorporates exploration and experience into the testing process.
• Risk-based testing (RBT) is a type of software testing that is used to
prioritize the tests of features and functions in software, based on the risk
of failure, the function of their importance and likelihood or impact of
failure.
3

4. A Quick Example
4

5. Exploratory Testing Explained..
• Its not a testing technique. It can be applied to any testing technique
• Every experienced tester does some exploratory testing some time or the
other.
• Scripted Vs Exploratory Tests
5

6. Scripted Testing, Adhoc Testing, Exploratory Testing Explained..
6

7. Blend of Exploratory Testing along with Risk based Analysis
• Risk based exploratory testing gives a proper structure to exploratory
testing.
• “Exploratory testing"--coined by Cem Kaner, in Testing Computer
Software-- refers to a sophisticated, thoughtful approach to ad hoc
testing.
• Explore the application and identity the risks and execute the test
accordingly.
• Strategy is to categorize the system based on scope and do Risk analysis
on that particular scope “Risk based Scope”.
7

8. Need for Risk based Exploratory Testing in Mobile applications.
• Mobile systems involve a lot of learning from system and Customers, lot
of changes are made based on what the customer wants, the typical
errors in mobile systems, device dependencies make mobile testing more
complex.
• One step leads to another and new scenarios can be identified in each
round of testing, which basically adds to knowledge of the tester.
• Exploratory Testing in Mobile Applications using Risk analysis comes a
very powerful way to find defects.
• Testing on wide range of mobile devices makes it impossible to test all
test cases, Risk Analysis in such cases becomes essential for testing in such
cases.
8

9. Approach to Exploratory Testing in any Application using Risk
analysis
• Step 1: Risk Identification and Analysis for the application.
• Step 2: Carry out Exploratory Tests on the identified areas of Risk
• Step 3: Maintain a Test Charter to document for the test scenarios and outputs
• Step 4: Perform Gap analysis to check if any test scenarios have been missed.
9

10. How is Exploratory testing useful in Mobile applications?
• Exploratory testing is useful in case of complex projects, where there is very little
known about the project. This type of testing can be implemented in Acceptance
phases (UAT) where end user can be asked to do a round of exploratory testing.
• Mobile Testing has a very wide scope, because of the number of platforms, Device
range and network scenarios. Mobile testing requires rapid feedback and is mostly
done with agile technology. Mobile screens and navigations keeps changing as per
design and OS, so the traditional test scripts become obsolete very soon. In this
case, exploratory risk testing comes handy.
• The tests can be run based on prioritization and defects can be reported. During
exploration testers come across newer flows and hence chances to uncover newer
defects.
10

11. Pros and Cons
Pros
•Less preparation is needed, important bugs are found quickly, and the approach
tends to be more intellectually stimulating to execute than scripted tests.
•Testers can derive conduct tests based on previous results to guide their future
testing on-the-fly. They do not have to complete a current series of scripted tests
before focusing in on or moving on to exploring a more target rich environment.
Cons
•Exploratory testing requires highly skilled testers who are able to produce results
quickly and consistently
•Defining Exit criteria for exploratory testing becomes difficult.
•If not documented properly, exploratory test can lead to clutter and make Test
reporting difficult.
•How will tester learn, analyze, execute, document if he is an amateur?
11

12. Conclusion
• Main objective of testing is to achieve quality while working with deadlines.
Exploratory testing can be combined with several other testing techniques and
contribute to achieving the goal. The best results can be achieved using this
technique.
• This paper only covers a few ways that adding exploratory testing to your testing
regimen can improve your test coverage and help reduce risk. It can take the
testing to a newer level .There are many, many other advantages, Pros and Cons
not covered here in this paper. So keep exploring!
12

13. 13
References & Appendix
1) White Paper : A Tutorial in Exploratory Testing : Cem Kaner J.D, Ph.D
2) White Paper : How to perform Exploratory Testing by using Test Charter : ENEA ,
Andres Claesson
3) Exploratory Testing Explained : James Bach

14. 14
Author Biography
Archana Krushnan is currently working as Test Analyst at Nihilent Technologies
Pvt Ltd. She has been in the field of Software Testing for 5 years and worked on
several domains such as Telecom, Ecommerce and Healthcare. Her interests
include exploring new things in testing and sharing on her blog. She has
previous experiences of working with companies like Reliance Communications
Ltd and Fab.com. She has good knowledge in Selenium, Jmeter and Soap UI. She
is ISTQB Foundation Level Certified.

15. 15
Thank You!!!