From browser quirks to bugs caused by faulty lines of code, tracking down bugs can be difficult. BugReplay can help you debug user feedback quickly by providing video bug reports with developer console logs and all the data you need to diagnose and fix bugs.
The bug reporting process is quite complex: it includes several different people (QA, developers, product managers, customers/end-users, etc.) with varying levels of technical knowledge or expertise, and all the members involved must be able to provide just enough key information so that the developer can fix the issue. But it has to be the “right” information, and additional useless data can slow down the process. Obtaining both visual and critical data is hard to do in an efficient way.
Let’s take a look at how BugReplay can help developers debug user feedback quickly. We created a quick fictional website called OneTrip using Vue.js. This basic page is composed of two Vue components. The first component is the Vue Google Autocomplete component that is used to autocomplete valid addresses, and the second component is a date picker called vue-datepicker. The demo is not meant to focus on Vue.js but rather to be demonstrate BugReplay’s features. With that in mind, let’s take a look:
John is a QA agent at OneTrip. He is debugging the new homepage when he notices there is an issue when the user enters a destination address. After several attempts, he is able to confirm the bug as well as view the alert banner at the top of the page that notifies the user of an error. Prior to using BugReplay, John would’ve take a screenshot of the alert and document the steps he took to reproduce the error. Then he would send the report to the engineering team. The engineering team would use the report and try to follow his steps to see the issue. Sometimes the developers would be able to trigger the bug and other times they’d need additional info.
BugReplay for Customer Support Teams
When I clicked this button, it said thisReported by Tim
Feedback like this can often point a developer in the right direction, but usually developers require much more information in order to diagnose and fix the issue. It’s a very frustrating and time-consuming process for both the customer support teams who have to ask the most basic questions (like “are cookies enabled?”) and for the non-technical end-users who just want the website to work properly.
Tim is visiting the OneTrip website and would like to book a car rental. All is going well until he enters the destination info. A red alert box comes up and says there is an issue with the destination address. Confused and not sure what to do, he sends an email to the support team saying “When I clicked this button, it said this! Help!” And now the fun begins. Let’s see how BugReplay could help out the OneTrip team.
By reviewing Tim’s logs, we can see that the destination address field is causing the error with the console stating "Destination address not found.” The dev team is quickly able to track down the bug and push a quick fix. Problem solved in record time!