📋
QASpace-CaseStudies
  • Home
  • Test Strategy
    • Vision of Quality
      • Good Test Coverage
      • ISO 29119 Certification
      • Date Internationalization Format
      • Localization Testing
      • Test Management
      • Creating TestCase
  • How to Test
    • How to write good TestCase?
      • Tips on Testing
      • Pair Testing
      • UserStory to TestCases
      • Optimising the development flow in a Scrum team
      • Rate/Prioritise bug tickets
  • Exploratory Testing
    • Exploratory Testing
      • Creating Test Charters
      • Test Charters
      • Velocity was too high
  • Agile
    • Implementing Scrumban
      • Breakdown Task
      • Common work across teams
      • Sustainable QA process in the organization
  • Philosophy of Testing
    • Brainstorming
  • Metrics
    • Risk Analysis
      • Testing Outsource
      • How to measure Quality?
  • Automation
    • AI-Automation
      • Software through the lens of AI
      • SAP/Salesforce Automation
      • Mobile Automation
      • Solve by automating the GUI?
      • Improve Skill-sets
      • Coding Skills
      • Working in BDD
      • Value of Test Automation
      • UI/API automation asset
      • TDD VS BDD
      • Selenium vs Cypress
      • An important consideration of Test Automation journey
      • Balance Test Automation Development
      • Automation is no longer providing value
      • Define AI in test automation
      • Unique Locators
      • Best Practices as QA, QA Lead, and Automation Engineer
      • Making friends with Imposters
  • Survey/Polls
    • Is QA really a Gatekeeper?
  • Performance
    • Performance Testing
      • Client-Side Performace
Powered by GitBook
On this page

Was this helpful?

  1. Exploratory Testing

Exploratory Testing

Ministry of Testing

Suggestions:

We should drastically reduce the use of the term "user error," replacing it most of the time with "unexpected user behavior" - Exploratory testing can help us reduce the amount of unexpected user behavior because we will have anticipated it and made sure the system doesn't break when they do it - To limit redundant testing, we are going to think together to come up with a list of "off the happy path" user behaviours. - Helps to think about the way the user feels when they are working in the system. -- If a user is facing a deadline, and has an issue, they might be anxious. --- Anxious users may click buttons multiple times in a row, ignore instructions in warning modals, etc. -- If a user is new to the system and doesn't want to use it, they may be frustrated. --- Frustrated users may quit in the middle of a task, delete files or drafts in order to "start over," etc. -- If a user is new to the system and is excited about using it, they may be curious. --- Curious users may try to use features for different purposes than they were designed for.

--- by Deb Collins

PreviousRate/Prioritise bug ticketsNextCreating Test Charters

Last updated 4 years ago

Was this helpful?