Consider a scenario where an issue with your product happens 15% of the time on an order form or contact page or other critical piece of functionality. The gross revenue of the project could
easily be diminished by 15% or more, and because of the obscurity of the issue it may not even be discovered by the clients, developers, or even the overwhelming majority of the users while 15%
of the active users are experiencing it.
Active users are quite fickle, and it’s likely that even while 15% of the users are experiencing the issue none of them will actually report the issue to the client or developer, instead they
will simply choose a different option or competitor’s product. Additionally in the rare event that they do report their issues, it’s often reported with only untechnical and unspecific information. The report
“I tried your contact form and it didn’t work” does not convey enough information about what caused things to actually go wrong to find or fix the issue for a lot of major problems. The developer or client would go and try the contact form in their environment again,
only to discover that it continues to work in their environment and mark it off the list as a non-issue because most users aren’t reporting it.
Additionally that’s assuming the report of the issue actually makes its way to a developer, often times the person working the front desk or answering the office phone may be the only person to
hear a customer complaint about a bug and if they don’t see the issue they won’t pass it on. Meanwhile concurrently in this scenario the actual effectiveness of the client’s goals or revenue on the
project are reduced by a significant amount that could have been saved by a testing phase with good coverage.
Contact Code Authority online anytime or call our Dallas based office at 469-656-5036 for testing services.