Why Use BugMuse, the Broken Button Detector?
Expensive Broken Buttons Happen All The Time, Even to Billion Dollar Companies
Broken Buttons just happen way too frequently. And every time they happen, that's at least $100s if not $1000s of dollars and time wasted.
And it happens to billion dollar companies too.
1) Upwork ($6 billion dollar company) has a long-standing bug where clicking "Request Exception" doesn't do anything, due to a 500 backend error.
2) SmartFinancial.com has a bug where adblocker is breaking their insurance questionnaire (causing thousands in damages, at minimum)
3) Retool ($1 billion dollar company) launched a bug one time where their "Sign-In" button didn't do anything.
It's impossible to detect every bug, but we figured out a way to at least automate detection of a Broken Button. If we detect a user clicks on the same element 3-5 times in a row with no visible change, we report that as a bug.
It only takes 1 line of code to install, and you can start detecting these broken buttons.
A really cool feature is "click highlight" -- we highlight exactly where the click happened, so you can easily debug what broken button exactly is causing the issue.
1 line installation. Copy-paste, 5 minutes, done!
Once installed, new bug reports will show up instantly. There is no lag time between the time a bug is reported, and when it shows up in the dashboard.
Rapidly Debug Broken Buttons: "Click Highlight" of Screenshots
In one glance, understand exactly what the bug is with the screenshot of the exact moment the user clicked the broken button.
What's more, the click is highlighted! How insanely cool is that? So you can see exactly where the user click was that caused the broken button.
I think this is the coolest feature and I'm excited to show it to you.
Frequently Asked Questions
Since this just operates on the DOM, this is compatible with React and every other PWA/SPA
Answer: BugMuse is performant -- extremely performant. BugMuse just keeps track of the HTML state at the time a click on a button-like element was performed. Note that MutationObserver is not sufficient. The method I described even handles cases where a button click "adds" elements to the DOM, but for some reason they were not visible. In a real-life test case, smartfinancial broken questionnaire was actually adding DOM elements, but they were not visible. That test case was also why we could not use MutationObserver, since there WERE mutations. We needed to detect that there was no visible change.
This sends back maximum 1 bug report per session. Just a JPG screenshot and x,y coordinates of the broken button.
Currently no option to deploy on-prem. That is in the roadmap.
At first glance, you might think it's as simple as starting a MutationObserver and then checking whether clicking the button would change the DOM. This is not true.
In a real life test case, SmartFinancial.com had a broken questionnaire where clicking a broken button would indeed add DOM elements, but none of them were visible. So the button was broken, and MutationObserver was not sufficient.
BugMuse calculates the visible elements every time a button is clicked. So this handles the SmartFinancial test case of DOM elements being added but not visible.
Test it out for free
Get Bug Reports Every Day
© Bug Muse. All rights Reserved