Imagine spending thousands of dollars on a specialized ad campaign to drive traffic to your website, only to find out after that your website’s call to action button wasn’t functioning properly, or that a specific page was taking too long to load, causing these costly website visitors to abandon your site before you could collect their contact information.
Imagine investing thousands of dollars on new software functionality. Your software engineering team believes the new code is (close enough to) bug-free, and ready to push it to production. The code contains, among other things, some minor UI changes, and once it’s pushed to production, it ‘breaks’ the overlaying onboarding workflows your customer facing teams took significant time to setup. Your team doesn’t catch this, as your customer facing team isn’t aware of the minor UI changes, and your engineering team isn’t aware of the overlay tooltips. No one on your team catches this as no one is assigned to proactively manually test the end user onboarding workflows. At best, your newly acquired customers or trial users see this and question the quality of your product; at worst, the onboarding workflow designed to quickly get users to value falters.
Both of these instances can be mitigated with Quality Assurance (QA) Exploratory Testing.
What is Quality Assurance Exploratory Testing?
The process of manual website and/or software testing conducted by a third party which is centered around:
1. The anticipated functionality of a software system
2. Further exploring the software system to reveal edge cases and weak or broken workflows
The Benefits of Quality Assurance Exploratory Testing
1. Unlike testing against specific acceptance criteria, testing independently provides findings that are often missed within such narrower lanes of focus. Non-obvious bugs or workflow issues almost always circumvent binary testing of acceptance criteria.
2. Exploratory software testing will pro-actively aim to break workflows so that your team can fix issues before your end-users discover them or are otherwise adversely impacted.
3. Discover what’s not intuitive within the User Experience through the eyes of independent exploratory testing. Use this information to improve UI/UX and ultimately, user success. Fresh eyes bring invaluable insight.
What’s the Cost of Quality Assurance Exploratory Testing?
All Quality Assurance Exploratory Testing is set at a fixed hourly price.
Have a more robust software product? Need 3rd party integrations tested? Want testing done on four different browsers? All of these can be accommodated.
You’ll receive a comprehensive report containing all encountered issues, including console and network errors as appropriate, as well as screenshots and videos as relevant for documentation.
Quotes for Quality Assurance Exploratory Testing
Each website and software needs are unique.
Book a call with me to discuss your website or software testing needs.