Exploratory Testing

Often times the development team will know where the development issues lie but haven’t had time to investigate or prioritise a solution to these problems.

This is done to find out which devices, geographies or particular pages are having problems, and how this impacts the user experience.

A broad range of tooling is used to look at how the website is structured and determining which changes would improve the delivery of the customer experience.

Business owners – improving the user experience will reduce bounce rate and increase session length, conversion rate and basket value. Whether you run an ad-driven website or an e-commerce website, we will help boost the bottom line.
Engineering teams – Gumoa will help front-end engineering managers better understand performance; to deliver features faster, rather than shipping features with no SLAs or performance metrics which can then degrade the user experience over time.

• Find and understand the root cause of user experience issues
• Find and use the tools and techniques to resolve them
• Prioritise which issues to resolve first

Exploratory Testing is usually done in conjunction with more formal, scripted testing and Test Automation. It should not be used as a substitute to other types of testing, rather as a complement. Some examples of when Exploratory Testing is typically done include:
• When a new system is developed and there is limited data on previous issues with the system.
• When you want to ensure the system performs optimally for its intended purpose, using human interaction and intuition on how it would typically be used.
• To get a better understanding of how a system works, and uncover any issues that deviate from those expectations.
• When it is absolutely critical that every precaution has been taken against potential issues, or when quality is the number one priority