Hot on the heels of the Bonfire 2.4 release, which allows you to attach any file to an issue created via the browser extension, we are thrilled to announce Bonfire 2.5 with Test Sessions. This latest release elevates Test Sessions to a whole new level. Prior to this release Test Sessions were available via the Project page, or on an individual issue page; there was no single place to see all Test Sessions.
Today, Test Sessions have found a new home in the JIRA header:
Using the ‘Get Bonfire Extension’ new users can quickly install Bonfire browser extensions for Chrome, Safari, Firefox and Internet Explorer. They also have access to documentation and tutorials via ‘Getting Started’, helping new team members raise bugs from day one.
The most important aspect of the new Test Session menu is ‘Browse Test Sessions‘.
Through this page QA Engineers or Managers can see, at a glance, all the open, in progress and completed test sessions. It’s also possible to filter by project, assignee, status or via test session name. Any search you perform can be bookmarked using a permanent link.
But wait, there’s more!
You can easily create a team dashboard incorporating everything from a ‘created vs resolved bugs’ graph to an ‘escaped vs captured‘ pie chart, or a list of open Test Sessions – all of these metrics can be at your fingertips in moments. Bonfire 2.5 allows you to add a dashboard gadget to select and show the team’s Test Sessions, similar to the filter above.
This feature is brilliant for providing visibility to the whole team – the developers, the product owners…and yes…the testers, too!
But wait, that’s not all folks!
By popular demand it’s now possible to create a Test Session within the browser extension. Testers and developers can quickly create a new session while conducting exploratory testing on their application. Testing sessions can be started immediately, or you can return to it later.
You’ve probably been in a situation where you forgot to add an issue to a test session, or perhaps raised a bug for a different product while testing the current application. This latest update means you can now add issues to – or remove them from – a test session if you find yourself in this awkward position. Technically speaking, under the guidelines of Session-Based Test Management, such activity should stand as-is. Seemingly unrelated issues should still be recorded in the activity log even if they were created during an exploratory test session. Now you can have your cake and eat it too.
One improvement I want to highlight is the ability to disable the auto-collection of environment details such as the URL, browser version, etc in a template. You can also turn off environment deails for the creation of a single issue:
This is a huge release for Bonfire – it incorporates fantastic improvements for QA Managers, QA Engineers and their counterparts in Development who are also responsible for quality. …Your developers participate in test sessions, right?
Bonfire 2.5 is available for download today. If you’re using OnDemand you will be upgraded to Bonfire 2.5 in early October.