While testing a search bar, you notice the results behave inconsistently when using special characters. How would you explore and identify all scenarios that could cause this behavior?

You are performing tests on the search bar available in a web or mobile application. During the tests, you find out that the search results tend to be unreliable when some special characters are included in the search query (such as @, #, %, $, or quotation marks). Sometimes it returns nothing, and in others, it provides wrong or incomplete matches. It might even crash or produce an error in the application when the user tries to search.

It raises a question as to how the application will manage the special characters in the user input; for it might include problems such as improper input validation, incorrect encoding/decoding, or, in general, does not support special characters in the logic with which search queries are processed.

3 Likes

If one or 2 special characters break the searchbar, I would just ask the developer what the restrictions are. There is no need to try out all special characters and list them when a developer can just say β€˜we only support ascii or letters/numbers’

Then you can make a ticket about it to fix it :slight_smile:

4 Likes