In order for a developer to fix a bug they have to identify its underlying cause. The gold standard for a bug report is reproducibility: if the developer can reproduce it then they can determine its cause and fix it.
Recording a bug with Web Replay gives developers an exact reproduction of that bug. Developers analyzing a saved recording will see the same DOM, CSS, JS, and other behavior that originally occurred, and which they would see when debugging a tab on their own machine.
Bug reports can come from a variety of sources. All of these will be improved by using Web Replay recordings, as outlined below.
Good bug reports are hard to produce, even for professional QA staff. Many bugs only reproduce in certain situations, and writing down enough instructions to reproduce them is tricky or impossible. QA staff can include console logs, screenshots, or videos showing the bug, but these usually aren't enough to determine the underlying cause.
Creating a Web Replay recording removes all this guesswork. We have designed Web Replay to make it easy for QA staff to create recordings and send them to developers. No account or payment is necessary to create recordings.
Bug reports from users are even harder to handle than reports from QA. The user’s profile can have quirks which make reproduction difficult, and users generally lack the technical skills to write down instructions for reproducing bugs.
Web Replay is designed to be accessible to users in the same way it is for QA staff. Users simply need to download the Web Replay browser, record the bug they are seeing, and send a link to that recording to the developers.
Test failures in CI can usually be reproduced by developers, but several steps might be required to see the failure on their own machine. Web Replay can be launched from the command line and automatically submit recordings (well, not quite yet, but soon). Links to these recordings can be sent to developers so that they do not need to reproduce the problem locally.
The benefits of using Web Replay recordings are especially apparent for bugs that only occur intermittently. Reliable bug reports can’t be created for these problems and they can be extremely difficult for developers to figure out, often lingering for months or years. Any intermittent bug captured in a recording can be thoroughly analyzed and have its underlying cause determined.