Embracing AUTOBOTS &

CHATBOTS in the Real

Business World
Presented by. BI&A Practice

www.hexaware.com
Table of Contents
Introduction 3
Exploratory Testing- ‘Breaking away from the Traditional Testing’ 3
Objectives of Exploratory Testing 3
Adapting Test Design Techniques 4
More of Experimentation 4
Exploratory Testers Are Creative and Critical Thinkers 4
Innovative Solutions and Value Adds 5
Mechanics to structure your Exploration Testing 5
Charters that guide scope of Testing 5
Timeboxing 5
Mind Maps 5
Benefits and drawbacks 5
Conclusion –Let’s Explore 6

2
Introduction
Today’s Users expects high quality applications and software in short time frame and using digital technologies. Organizations are
under critical pressure to meet their business commitments, while delivering innovative solutions and services. They need to be
nimble, quickly respond to competitive threats and create sustainable market advantage. Does the traditional way of testing help
Quality Assurance team achieve this objective? A new approach to testing, allows the Quality Assurance team to induct and explore
the functionality by simultaneously learning, designing and executing. This new method of testing is called as the “Exploratory Testing”
and is considered a value addition to other kinds of testing.

Exploratory Testing- ‘Breaking away from the Traditional Testing’

Exploratory Testing is a thoughtful testing approach. It goes beyond the traditional testing concepts. The method helps in detecting
uncovered/hidden defects. It’s an out-of-the-box testing approach, where we don’t go with the usual set of test cases. The tester’s
intuition, creative thinking, past experience, knowledge of the product is used in testing the product beyond its limits.

Unique Characteristics of Exploratory Testing:

• Simultaneous learning the application in and out; Designing test using heuristic approach; Executing the test cases and Running the
test cases
• Performed by “experienced and passionate testers” with divergent thinking capability
• Requires interpretive, logical thinking and knowledge in adjudging the paths that would lead to covering most functionality in a
short period of time

Exploratory Testing Myth – It does not require detailed preparation. You just start using the application and randomly look for any
issues

Objectives of Exploratory Testing

Exploratory Testing is about gaining an understanding of how the application works, its interfaces, the functionality it implements. All
this is done from an end user perspective, without a script and tests for a predetermined outcome. This approach ensures that the
application works its best.

Learn Design

Exploratory
Testing

Results Execute

3
Adapting Test Design Techniques

An Exploratory Tester needs to adorn the hat of a test planner, understand test procedures and methods. He/She should be versatile
in calling
different methods and functions, in real time and during the exploration.

Exploratory Testing is usually planned with Agile development process or as a final check before the software is released.

It’s ideally suited for the following instances:

• Releasing first minimum viable product in beta or a major new feature release
• There is not enough test documentation available
• Under critical time pressure to script and run tests
• Need for diversification of formal test plan and design techniques
• Lack of time to document all test scenarios, variations and test procedures
• There are risks that needs to be covered throughout the testing lifecycle

More of Experimentation
Exploratory testers have an eye for observation.
As an exploratory tester, you need to quickly spin out ideas, try and experiment them. Look out for unusual or unexpected behaviors
and view assumptions for correctness cautiously. Watch out for hidden software aspects or uncover patterns that drive the change
to test in real time. Another distinguishing aspect of being an exploratory tester, is that you view the application from a ‘user point
of view’, rather than the ‘developer’s point of view’.

It’s more of learner tester driven style rather than a test case driven style. Exploratory Tester experiments with the system and
identifies the vulnerabilities. It discovers the patterns in which it works fine and where it fails.

Exploratory testing’s experimental analysis goes way beyond functional specification, thereby providing comprehensive coverage.
Some of the key analyses are illustrated below:

• Identify the scope and vision of the product

• Identify the non-functional areas and its coverage
• Identify the intended end users who will be using the product.
• Identify the potential uncertainty functions.
• Test each functions and report defects.
• Relationship of a defect linked to other areas of the application is explored and researched

Exploratory Testers Are Creative and Critical Thinkers

It is important for exploratory testers to have good analytical skills and thinking power. It requires a unique genre of qualities like
meticulously question ideas, bring up assumptions, approaches, all while solving problems in a consistent and systematic manner.
They need to explain their logic of looking into defects and provide clear status of thinking. Exploratory Testers need to be ‘Critical
Thinkers’.

Exploratory Testers need to have these unique traits:

• Knowledge of different test design technique, usage of different tools

• Good Observation skills, uncovering any hidden defect
• Critical Thinkers who work with guidelines, checklists, rules of thumb

Exploratory testing helps in identifying defects early in testing lifecycle, when an application interacts with different networks, other
component of same system, with other software via APIs, with file systems, memory system, with multiple operating system and
physical devices.Critical thinking is required to analyze and identify the defects in areas that would help the product to be more
robust and reliable upon delivery

4
Innovative Solutions and Value Adds
Exploratory Testing has a set of unique value-ads like:
Record, Playback & Review: Exploratory testers often use tool like screen capture, video tools to record their exploratory findings
and results for later playback and review. Microsoft Team Foundation Server supports these features.
Findings Report and Charter Details: Report an exploratory finding, by sharing the test results to the customer in document. This
document might contain the features that you have tested including Charter details, short notes on how you performed testing,
identified defects and details
Re-testing made simple: We can save time on future regressions, by saving all actions as script of steps in test cases. These steps
can be followed by someone, instead of reproducing them.

Mechanics to structure your Exploration Testing

Exploratory Testing is most suited for modern web or mobile application development, where there will be a need for multi-platform
support, security and better user experience etc. It perfectly fits for projects developed using Agile methodologies, because of
constantly changing business requirements. Indeed, it supports other testing methodologies too. Exploratory Testing is more of an
unplanned activity. Identify the items to be included based on test scope and test charters.
To achieve maximum result, exploratory testing applies three techniques:
• Charters
• Timeboxing
• Mind Maps

Charters that guide scope of Testing

While carrying our Exploratory Testing, there is a high chance to get lost and move out of focus from what is important. It’s
important that you focus on one area at a time, write it down on a charter. It is good to know the below points about Test Charter
before planning your Exploratory testing:
• Helps to determine the goal or agenda, resource and workflow of a test session
• Guides the QA team in their exploration
• Test charter contains the detail description including:
- what to test?
- what approach to use?
- what are the documents available and refer to test?
- who would be testing the system?
- what data, test environment and configuration do we want to use?
- what are the defects identified?
- what are the potential risks involved in?
Testing can be concurrent with product development and test execution. Such testing is based on implicit and explicit specification
as well as the “as-built” product.

Timeboxing
Timeboxing helps to stay on track, focus on specific goals and avoid unexpected expeditions.
The next test that would be carried out will be based on the previous test results. This follows Inspect and Adapt Model.

Mind Maps
Mind Maps were earlier used by students to take notes using a visual approach, of noting down key words and images. Mind
mapping is being used as logging tool for exploratory testing.

A Mind Map is a graphical way of representing ideas and concepts. It’s a visual thinking tool that organizes information, structures
thoughts in a diagram instead of writing it in sentences.

Benefits and drawbacks

Exploratory Testing has its own share of benefits and challenges. Its unique capability brings out certain risks and vulnerabilities that
were never before discovered. Exploratory Testing is suited for Agile testing environments. The ability to attach user actions and
videos of recent activities has been invaluable. Exploring the application in-depth helps QA teams to reduce risk and gain
confidence.

But the flipside is, Testers risk a great amount of time on an application looking for things to test and trying to find bugs. At times,
lack of preparation, unplanned guidance can lead to many hours wasted in retesting the same functionality over and over again.

5
Conclusion –Let’s Explore
Although manual testing continues to be a popular method of validating application’s functionalities, exploratory testing can be
introduced to accelerate manual testing process, increase speed, coverage, and accuracy. Its incremental delivery will be definite
value add to your testing activities. Adopting all these techniques and processes might take some time during the initial stage. Once
the team understands and effectively implementing the above approach help them to deliver best quality product in the market,
thus maximizing the ROI.

Author’s Bio
Deepan Chakravarthy is a Test Lead of Digital Assurance Unit in Hexaware Technologies. He has over 9 years of IT experience,
responsible for delivering quality mobile & web applications for both enterprise and consumer base serving across different business
verticals includes Healthcare, BFSI and Insurance.

6
About Hexaware
Hexaware is the fastest growing next-generation provider of IT, BPO and consulting services. Our focus lies on taking a leadership position in helping our clients
attain customer intimacy as their competitive advantage. Our digital offerings have helped our clients achieve operational excellence and customer delight by
‘Powering Man Machine Collaboration.’ We are now on a journey of metamorphosing the experiences of our customer’s customers by leveraging our
industry-leading delivery and execution model, built around the strategy— ‘Automate Everything, Cloudify Everything, Transform Customer Experiences.’

We serve customers in Banking, Financial Services, Capital Markets, Healthcare, Insurance, Manufacturing, Retail, Education, Telecom, Professional Services
(Tax, Audit, Accounting and Legal), Travel, Transportation and Logistics. We deliver highly evolved services in Rapid Application prototyping, development and
deployment; Build, Migrate and Run cloud solutions; Automation-based Application support; Enterprise Solutions for digitizing the back-office; Customer
Experience Transformation; Business Intelligence & Analytics; Digital Assurance (Testing); Infrastructure Management Services; and Business Process Services.

Hexaware services customers in over two dozen languages, from every major time zone and every major regulatory zone. Our goal is to be the first IT services
company in the world to have a 50% digital workforce.

NA Headquarters India Headquarters EU Headquarters APAC Headquarters

Metro 101, Suite 600,101 Wood 152, Sector – 3 Level 19, 40 Bank Street, 180 Cecil Street,
Avenue South, Iselin, Millennium Business Park Canary Wharf, #11-02, Bangkok Bank Building,
New Jersey - 08830 ‘A’ Block, TTC Industrial Area London - E14 5NR Singapore 069546
Tel: +001-609-409-6950 Mahape, Navi Mumbai – 400 710 Tel: +44-020-77154100 Tel : +65-63253020
Fax: +001-609-409-6910 Tel : +91-22-67919595 Fax: +44-020-77154101 Fax : +65-6222728
Fax : +91-22-67919500

Safe Harbor Statement

Certain statements in this press release concerning our future growth prospects are forward-looking statements, which involve a number of risks, and uncertainties that could cause actual results to differ materially from those in
such forward-looking statements. The risks and uncertainties relating to these statements include, but are not limited to, risks and uncertainties regarding fluctuations in earnings, our ability to manage growth, intense
competition in IT services including those factors which may affect our cost advantage, wage increases in India, our ability to attract and retain highly skilled professionals, time and cost overruns on fixed-price, fixed-time frame
contracts, client concentration, restrictions on immigration, our ability to manage our international operations, reduced demand for technology in our key focus areas, disruptions in telecommunication networks, our ability to
successfully complete and integrate potential acquisitions, liability for damages on our service contracts, the success of the companies in which Hexaware has made strategic investments, withdrawal of governmental fiscal
incentives, political instability, legal restrictions on raising capital or acquiring companies outside India, and unauthorized use of our intellectual property and general economic conditions affecting our industry.

www.hexaware.com | marketing@hexaware.com 7 © 2019 Hexaware Technologies limited. All rights reserved.