Channels ▼


Zephyr for JIRA 2.0 Blows In

Test management software company Zephyr has released Zephyr for JIRA 2.0 and a new add-on product ZAPI 1.0. These new products work as automation and continuous integration tools inside the JIRA issue-tracking product from Atlassian.

Zephyr for JIRA 2.features the introduction of a new Execution Navigator and advanced searching using the Zephyr Query Language (ZQL). New features now allow the searching of test executions using a variety of simple clauses with auto-completion built in. Results can now be saved as favorite, private, or global filters and can be reused in a variety of ways.

The Execution Navigator allows for rapid searching and execution of tests with performance enhancing capabilities such as bulk status updates and copy/move tests between test cycles. Test execution reports are now available directly from the Execution Navigator in five different formats.

The developers behind Zephyr for JIRA 2.0 say that it "is all about opening up" its testing data to be accessed, viewed, and updated in a variety of different ways, be it via the easy-to-use user interface that is integrated right into JIRA, or programmatically via the addition of the newly announced Add-on ZAPI 1.0.

ZAPI is a Zephyr for JIRA Add-on that allows access to Zephyr's testing data, including the ability to view and upload data programmatically. ZAPI allows access to Zephyr for JIRA to read-write testing-related data via REST APIs. This can be used to query test cycles, fetch tests and test cycles, update test results, and create new tests. Integration to automation and continuous integration tools are now possible with well-documented and supported REST APIs.

"We take our leadership role very seriously, closely listening to our customers, and are committed to delivering the best testing products that compliment Atlassian tools," said Shailesh Mangal, CTO for Zephyr. "The combination of these two products creates endless testing possibilities for project teams. ZAPI 1.0 and Zephyr for JIRA 2.0 give users enhanced abilities to execute tests in a free form way and leverage the REST APIs to unify testing data across multiple systems."

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.