Our goal with Bonfire is to help you deliver quality working software to your customers. Agile defect prevention is an approach whereby you find and address bugs before your customers experience them. Bonfire facilitates agile defect prevention and provides confidence that you are delivering quality working software to your customers. Bonfire helps you deliver quality working software.
Atlassian Bonfire 2.1, available today, makes everyone a professional when it comes to reporting bugs. Further, the test sessions and traceability in Bonfire 2.1 allow you to monitor the quality of your product over time. Now, let’s take a look at these features in detail.
Annotate Screenshots Like a Pro
Bonfire 2.1 has a completely redesigned and rewritten annotation tool – we call it Charcoal… get it? The new annotation tool kicks ass, making it quick and painless for anyone to annotate a screenshot with the detail required to enable an engineer to reproduce a bug. Annotations are amazing because you can now:
- Move, resize and delete annotations
- Add colour, and lots of it
- Blur with perfection
- Have wonderful text
No point in reading about it though, take a look for yourself:
Multiple Related Issues in a Test Session
It is important to ensure that the team has tested the high risk issues on the backlog. Even if the team doesn’t have time to QA every story in the sprint they can at least create a test session which links to multiple issues that are considered high risk. You are now focusing the limited QA time on a test session for the high risk issues.
Of course linking a test session to multiple issues means you’ll also want to raise bugs as sub-tasks under one of these parent issues. You can do that too.
Everyone in an Agile team is responsible for quality, not simply the QA Engineers. Bonfire provides visibility into the manual testing that the team performs (see Atlassian Bamboo for automated testing). The Test Session captures all the relevant information including activity, participants, raised issues and time spent: In Bonfire 2.1 a team can quickly jump from the test session screen to the Issue Navigator to triage the issues raised in the session. We made this easier so that you can get those bugs on the backlog, and get them addressed ASAP.
When everyone in the team participates in the testing we expect to have a very high quality product. To make sure that is the case we can report on the bugs raised during a release, and how they were raised. For instance, we may want to know how many bugs were raised prior to release and how many were raised by our customers once the product was released.
In the left hand pie chart below we have “Raised During Test Session” and on the right hand pie chart we have “Raised During is Empty”. We are using a new JQL clause “Raised During” for this report.
We can see that there were more escaped bugs in 1.1 (44 bugs) compared with those we caught during a 1.1 test session (22 bugs). The real power comes when we start adding this to our Dashboard to track the quality of each release: There is a ton of awesome functionality in Bonfire 2.1 to make your testing team more Agile, and more efficient.