Using the Zephyr Add-on in Quality Assurance

Zephyr is a test management add-on for Atlasssian. It allows project teams to add testing to agile creation processes (and to planning, coding, and collaborating on software releases). Using this tool, you will be able to create test cases that could be used in further stages of development process to demonstrate the progress made on a given piece of software. It also helps with organization of work and allows us to work better and more efficiently.


Benefits of Using Zephyr as a Test Management Tool

Why Zephyr and not other test management tools?

Well, Test Cases created using this particular tool are done straight in JIRA – as it is an add-on – and that means that you do not need any third-party software to use it. Here, you have everything in one place. If an issue is found in the course of executing a Test Case, the tool immediately creates an issue in JIRA (if it is not already in there).

Creating Test Cases Using the Zephyr Add-on

When we start to work on new designs and developing a new application for our client, one of first things we do is create Test Cases based on User Stories prepared earlier.

Each User Story has at least one Test Case related to its Acceptance Criteria:

Zephyr 1

Creating Test Cases using Zephyr is pretty easy – JIRA allows adding Tests to every project.

Later on, they may find their place in the backlog in a separate sprint called Test Cases, so that the client is able to see them whenever they want.

Tests in Jira

Once a test is created, at first we are only able to add a summary and a short description. Afterwards, in Test view, we can add specifics steps with the test data and expected behaviour.

Zephyr 2

Finished Test Cycles

When all Test Cases are finished, we can start creating a Test Cycle which can cover, for example, one iteration / sprint of User Stories or all functionalities tested at the end of project. We can also establish result available for test cases and their individual stages, such as : “PASS”, “BLOCKED”, “IN PROGRESS”, “FAIL” etc. Here is what a sample Test Cycles look like:

Zephyr 3

Failed Test Case

If a Test Case fails with an issue number, the issue becomes linked as “relates to” and proper information will be displayed for the issue under the Issue Links section:

Zephyr 4

Additionally, we write Automation Test Cases with Zephyr which helps us to manage our automation tests. That way, we can keep all necessary Test Data and required steps in one place. We are also planning on connecting Jenkins with Zephyr in the near future, a setup which will mark test results in JIRA/Zephyr for us! The project is still undergoing extensive testing.

Zephyr’s Benefits for Software House Clients

Using a tool like Zephyr enables us to cover 100% of the functionalities with Test Cases, which, in turn, allows us to keep track of everything and make sure that we do not forget about anything.

Moreover, our Test Cases cover a 100% of our clients’ business requirements. It is like book on software design written especially for people uninvolved with the software development process.

Having Test Cases directly in a project gives us the ability to easily share the progress of our work. The client can see at any time how their product is growing, what’s being done at that particular moment and what the plans are for the upcoming days.

Got inspired? E-mail us and we’ll get in touch to find out how our design, development and Quality Assurance services can drive business value for you.

Use Kotlin Anko DSL and Say No to Android Layouts Written in XML
7 Tools to Use When Outsourcing App Development