Browser Testing QA| Hitchhikers Platform
What You’ll Learn
In this section, you will learn:
- What is Browser Testing?
- Browser Testing Expectations
- Feature Testing Expectations
What is Browser Testing?
Browser testing requires you to test your search experience on a few different browser types and devices to ensure the experience performs consistently across each browser and device that you test. We recommend using an emulator like Browserstack to easily test different browsers and devices.
Generally speaking, you should test all search experiences on the following browsers and devices:
- Google Chrome (latest 2 versions)
- Firefox (latest 2 versions)
- Microsoft Edge
- Android (Both Chrome or IE11)
- iPhone (Chrome or Safari)
- Tablet (Chrome or Safari)
We suggest testing the latest two versions of Chrome and Firefox as they are some of the more commonly used browsers. For the other browsers listed above (Safari, Edge, and IE11), feel free to test only on the latest version.
You might be wondering, what if I don’t have access to a tool like Browserstack? That’s fine too! You can test the experience on each of the browsers you have downloaded on your devices.
Browser Testing Expectations
It’s important to standardize what’s being tested in each of the browsers and devices listed above. You want to ensure that the experience is functioning as expected across all browsers. You should click into all of the hardcoded prompts within your experience and ensure the following items are functioning properly for each browser or device you test.
- Ensure a map appears on both universal and vertical search (where applicable)
- Click all hyperlinked text to ensure CTAs are working correctly
- Move between Vertical Tabs and “View All” (Universal) Navigation
- Expand and collapse FAQs
Feature Testing Expectations
Below is a list of the individual components of a search experience that you should QA. Depending on the experience, you may not be using all of these features. However, if you’re using one of the features in the list below, be sure to QA and confirm it’s working correctly.
- Direct Answers
- Vertical Tab and “View All” Navigation
- Custom Backends
- Facets and Filter Components
- Configured No Results Behavior
- Spellcheck Component
- Location Bias Component
- Pagination Component
- Vertical Intents
- Target Behavior
- Pinned Results
- Configurable Sorting
- iFrame (/iframe_test) - This only applies if your client decides to move forward with the JS Snippet path. You’ll learn more about the integration options in ANS260: Integration Options and Getting Live.