A 25-user license runs at $600 including 12 months of maintenance. You can purchase Bonfire as a cloud service on demand, hosted by Atlassian, or you can download and install it on your own server. It’s also limited to testing of only web applications, thus, it is not suitable for testing of native Windows applications. If you use JIRA then it’s worth considering but if not, then you won’t want to look at Bonfire. It is also capable of capturing important system information of the test environment and even automatically capturing dynamic variables like the page URL.īonfire offers basic editing options for your screenshots but the output is directly to JIRA you can’t export separately. The focus here is clearly on improving QA and testers will welcome the inclusion of bug report templates, which can be set up in advance for individual projects to help to achieve consistency.
It’s designed to work with Atlassian’s bug tracking software JIRA. Using the browser extension a tester can also submit bugs directly from the web application being tested, with a record of the entire test session.
Bonfireīrought to you by Atlassian, Bonfire is a web plug-in that allows a tester to create an annotated screenshot based bug report directly from the browser. Let’s compare three of the best and find out how they measure up. There are several tools on the market for QA departments or software developers seeking to help capture detailed bug descriptions. browser version, OS version, memory, etc.) If you want to ensure that such bugs aren’t still lurking around then you need to record the precise steps to reproduce it and the easiest way to do that is to take screenshots, record videos, and capture all the vital details, including test environment (e.g. However, some of them eventually get found by the customer and at a much higher cost to the business. In most cases, the so called “can’t reproduce” bugs end up getting closed as due to no one being able to reproduce them. When the developer can’t reproduce the bug they’ll often just mark the issue as “can’t reproduce” and ask the QA manager to close it. A step-by-step written description of how to recreate a bug, no matter how detailed, leaves some room for error. In order to fix a bug the developer generally has to be able to reproduce it. Finding those elusive bugs is only the beginning, because the development team still has to fix them and they can’t be cleared until they’ve been retested.
Uncovering bugs in a software package is the easy part of the job in QA.
0 kommentar(er)
