Channels ▼
RSS

Web Development

Atlassian Lights A Bonfire Under QA Testing


Launched this month, Atlassian Bonfire 1.0 is a new Agile-focused testing tool positioned as a route towards testing web applications across all the "major" browser brands. Built to capture bug reports when analyzing web apps, this tool arms developers with an additional test mechanism over and above checks performed by QA engineers.

"Agile teams need a way to test early and often, to be able to easily submit bugs and issues as they arise, and to report on the status of the testing. That's where Bonfire comes into play," said Mike Cannon-Brookes, Atlassian CEO and cofounder. "Bonfire makes it easy for everyone on an Agile team to test their applications."

Developers can access Bonfire from the browser, test their applications, and then submit a JIRA bug report without leaving their screen.

Atlassian recounts the genesis of its new product as having come about after it began to run 20% time (modeled after Google's 20% time), in which developers can take one day per week (or spread their time out) to work on whatever project they want.

This time was open to free experimentation and research — provided that it was related somehow to Atlassian's products or markets. "As a result of 20% time, one of our developers wrote what would become our newest product, Bonfire," said the company.

Bonfire has four key features for allowing teams to test early and often: submitting bugs directly from the browser; adding annotated screenshots with each bug; establishing setup test sessions to track activity against a requirement or user story; and creating bug report templates to pre-populate meta-data and repetitive content.


Related Reading


More Insights






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
 
Dr. Dobb's TV