Discover Simplified Test Case Execution with QARAJ Add-On for Jira

The QARA Enterprise test automation suite offers an array of features and functionalities to make it easy for the QA professionals of today. It is a comprehensive test automation platform that caters to every requirement of the QA teams today and helps them overcome challenges and simplify test automation in more ways than one. While you can explore the entire QARA Enterprise Suite, this blog focuses on QARAJ – an add-on for Jira that enhances the Jira test management capabilities with the help of the QARA Test – a Jira test management tool.


QARAJ is a Jira add on that connects Jira to QARA Enterprise and extends Jira test management capabilities. The Atlassian Marketplace has the Jira add on available for download. QARAJ allows test cases to be executed from both the test case and the test cycle pages. Test cases in the Jira add on can range from simple one-liners to exceedingly complicated issues with a great deal of data, processes, links, and files. In either instance, when you've written a test case, the next obvious step is to run it. Executing a test case entails providing a high-level status on what occurred when the test case was "run" or "executed" and taking action in response (like filing a new bug, linking an existing one, attaching screenshots, making notes, etc.).

Test executions can take a variety of forms in the QARAJ Jira add on. You can execute test cases in one of the following ways using the QARAJ Jira add on, depending on how your project's testing process is set up:

  • From the QARA Test Case Execution Section of a Test Case Page
  • From the Test Cycle Page
Test executions in the QARAJ Jira add on can start from the Test Cycles page, which displays a list of all test cases grouped together by the Test Cycle for a given Version. When you choose the right Version, you'll see a list of Test Cycles that have been developed for it. There's also a progress bar that gives you a brief overview of where you are in the test cycle. You can easily sort the data in the following fields: ID, Status, Summary, Defect, component, Label, Added / Executed On and Executed By.

Execution Details
The following are the fields showcased under Execution Details when executing test cases using the QARAJ Jira add-on.
Execution Status: (This field shows a drop-down list of options. The status options that are available by default are UNEXECUTED, PASS, FAIL, WIP (Work in Progress) and BLOCKED. These statuses can be customized by your JIRA Administrator.)

Executed by:
Executed on:
Comment: (Details about the test execution can be entered here.)
Defects:

When a new defect is established, a remote link is created under the Links section of that defect. It displays the test case with a link to this execution, the test cycle it was part of, and the current status of the test execution. Users can see faulty remote issue linking at the test case level as well as at the test step level.

QARAJ is a Jira add on that can also be used to test step-level executions. You can also give information at the step level, such as Comments, and link existing Defects at that level. After you've stored the execution information, you may choose whether to go back to the test case or the test cycle.

In addition to the techniques of executing test cases that we've seen so far, a mix of the two is also feasible. However, regardless of the approach you use to execute test cases, it's critical to pick a methodology and stick with it for the duration of the project or version to achieve efficiency in the execution and reporting process.

QARAJ is part of the QARA Enterprise Suite, a Jira test management tool which includes several products, each of which has a different functionality associated the QA of software products and applications. It offers the multiple benefits that a Jira test management tool has to offer when it comes to effective test automation.

Write a comment
Cancel Reply