A new version of Qualitia Automation Studio for Web and Mobile 7.2.x is now available. We highly recommend you upgrade. Find more details here.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »

Qualitia Automation Studio integrates with JIRA in two ways.

  1. Import requirements from Qualitia Design Studio
  2. Create issues in JIRA from Qualitia Automation Studio 

Importing Requirements from Qualitia Design Studio

Qualitia Design Studio is developed for effective communication between business analysts and test management personnel. Using Design Studio, a business analyst, who gathers all the product requirements from the end users, can design requirements in JIRA and test analyst can import these requirements in Qualitia Automation Studio.

The requirements may include Stories, Epics, Acceptance Criteria (also known as Business Rules), and Activities.

After importing requirements into Qualitia Automation Studio, test professionals may proceed with developing test automation associated with business rules.

Throughout the release, business analysts may update the requirements in Design Studio and testers can synchronize changes from Design Studio to Automation Studio with a single click.

For more information about this, refer to the Qualitia Design Studio documentation.

Creating Issues in JIRA from Qualitia Automation Studio 

You can create issues in JIRA (Atlassian's issue and project tracking tool) from the Reports section of Qualitia Automation Studio. This saves tester's efforts to manually report issues for the test cases with defect.

You can also attach the report generated after the test case execution with or without the screenshots of the steps.

The issues can be created for those reports which are generated in the Report tab after Suite/Scheduler execution. It cannot be created for the Dry run.

You can create an issue at the Test Case Iteration level. An issue can be logged in JIRA for test case iteration with any status (except not executed).

Prerequisites

  • In order to use these features, you must have a valid JIRA account.
  • No labels