> For the complete documentation index, see [llms.txt](https://vinayak-titti.gitbook.io/qa-space/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vinayak-titti.gitbook.io/qa-space/exploratory-testing-1/exploratory-testing.md).

# 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