Elevate Exploratory Testing with Thinking hat and Persona-based Strategies

A software developer using macbook for testing purposes
Photo by Christina @ wocintechchat.com on Unsplash
  • Does it the quickest way possible.
  • Uses shortcuts like copy and paste, tab to navigate through fields.
  • Don’t fill in fields that aren’t mandatory.
  • Makes mistakes in the type of data that each field accepts, enters already registered details again.
  • Expects fast responses.
  • Often leaves the form filled halfway through because he gets called up for another meeting, comes back later, and checks the state of the form.
  • Enters invalid inputs, leaves mandatory fields empty, enters huge sets of characters, and checks how the form reacts.
  • Uses multiple tabs to process simultaneous registrations with the same credentials.
  • Accesses the registration form from an unusual browser or device.
  • Interrupts by disconnecting the internet connection or by refreshing or by clicking the back browser after having clicked the registration button with valid inputs.
  • Performs all the negative scenarios that come to his mind and evaluates how the system behaves.
  • Works with the parts of the application that others rarely do.
  • Tries out different workflows and button/key actions to achieve the same result.
  • Tries out any new feature to its fullest extent.
  • Takes a different approach when entering values in the registration form — borderline values, decimals, negative values, etc. to see how the application responds.
  • Registers with an email address that is already registered.
  • Uses the most popular features of the application.
  • Is watchful and notices even a small change in the routine workflow he uses, be it functional or UI.
  • Tolerates slow response times.
  • Enters data in all the fields, be it optional or mandatory.
  • Do not test the negative scenarios, enter valid data always.
  • Manipulates authorization by modifying URLs and tries to access pages that shouldn’t be viewable for a particular user role.
  • Uses SQL, LDAP, and JS tag injection to hack the system using the input fields.
  • Tries invalid values and makes the system show multiple errors at the same time.
  • Checks if passwords are encrypted during transmission.
  • Tries to hijack the session. Checks if inactivity timeouts are properly implemented.
  • Checks if the URL contains session id.
  • Tries to synthetically load the application server and observes its impact.
  • Checks to see if directory listing is enabled on the server
  • Checks to see if the application reveals error handling information such as stack trace to the end-user.
  • He accesses the application outside the local business hours where it’s hosted.
  • Uses different network providers, very often has poor network connectivity.
  • Uses a variety of browsers, machines, keyboard layouts, and devices.
  • Accesses the application from different time zones.
  • Slow response times do not bother him.
  • Accesses applications from an old browser version or a browser that isn’t used by many.
  • Reads through each page looking for instructions or visual cues. If the application isn’t intuitive, he gets stuck.
  • His operating system and machine are outdated.
  • Very often clicks on the back button to refer to the information entered on the previous page.
  • Zooms in on the webpage if he cannot see things clearly.
  • Has very little patience and gets frustrated if the app isn’t fast enough.
  • Switches back and forth between several different applications.
  • Receives several interruptions such as voice calls, video calls & message pop-ups while using the mobile app.
  • Expect the data entered during her last interaction in the mobile app to be intact when she returns from another app.
  • Expects uploaded images to be of great quality, expects uploads to be quick.
  • Switches to other competing apps or is quick to provide a scathing review if the UI or UX isn’t great with subsequent upgrades.




Your Digital Transformation partner. We are here to share knowledge on varied technologies, updates; and to stay in touch with the tech-space.

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

How to sell YOU online (fast)

Food for Agile Thought #149

Containers And Docker In Plain English For App Developers (1 of 3)

16 deadly code smells — Part 2

I will not write any more bad code

Fintech in practice: how Quadcode develops technology for trading and banking

Application Level Throttling with WSO2 Microgateway and WSO2 API Manager

Text-to-Speech espeak-ng

Building Real World Event-Driven System #1: Introduction

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Payoda Technology Inc

Payoda Technology Inc

Your Digital Transformation partner. We are here to share knowledge on varied technologies, updates; and to stay in touch with the tech-space.

More from Medium

Why You Should Automated Regression Testing?

Automated Testing with Robot Framework: Here Are The Things You Need To Know

In Dev we trust; But QA brings The Data !!

How to spot an SDET professional training that is a sham