Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,362,193
Community Members
 
Community Events
168
Community Groups

Understanding the Test Approach of QARAJ Add On

Understanding the Test Approach of QARAJ Add On (1).png

 

QARAJ is a Jira add-on that combines Jira with The Digital Group's QARA Enterprise test automation platform and offers comprehensive test management capabilities to the Jira interface. QARAJ's testing feature can be utilised in a variety of ways, including by project teams with extensive test procedures or by teams that are brand new to implementing an approach to testing.

Following are some examples of the testing approach of the QARAJ Add-on.

1] Basic Execution Planning

This is what you'll need to organise your test executions into Test Cycles, which will allow you to keep track of what has been tested and what hasn't. It also allows you to keep track of the difficulties and failures encountered during the test case execution process, as well as how much work remains. Setting up the Test Cycle(s) in a given Version and then ensuring that each test execution is recorded against those Test Cycles is a step that requires thorough planning (s).

2] Structured Execution Planning

Structured Execution Planning entails setting up the Test Cycle(s) as well as participating in the creation/modification of a significant number of test cases. In addition, it comprises the addition of test cases to the relevant Test Cycle(s) for future execution. You are also permitted to run the test cases throughout the project's allocated execution stages.

As the name implies, a Structured Test Approach divides your testing activities into discrete phases of organisation, planning, execution, and tracking.

3] Structured Approach to Testing

Moving on to the final element, a Structured Test Approach allows for four separate phases, as the name implies:

  • Organization
  • Planning
  • Execution
  • Tracking

Given below is a quick look at the many phases.

a] Organization Phase

Import, reuse, modification, cloning, and development of test cases are all part of the Organization step. This phase also entails connecting the test cases to various issue categories, such as epics, tales, and requirements. This step also entails arranging test cases according to Versions, Labels, and Components.

b] Planning Phase

The Planning step entails creating various Test Cycles and adding the test cases that must be executed to these Test Cycles. The tasks completed during the planning phase, which primarily consist of grouping test cycles, aid in the easy tracking of test cases.

 c] Execution Phase

The Execution phase entails the actual execution of test cases across multiple Test Cycles, with each execution carried out in a methodical manner. This step also entails linking to existing issues and bugs, filing new ones, and tracking the test case execution progress.

 d] Tracking Phase

The Tracking phase is all about keeping track of the test case's progress and other metrics. Metrics are used to track the execution of organised test cases. You also have Test Cycle reports, which show progress as well as the application's quality. The executive summary report is offered in a number of different versions.

So, that was about the Test Approach of the QARAJ ad-on. Have you tried QARAJ yet? Download the QARAJ add-on from the Atlassian Marketplace.

Read more on QARAJ: Explore an Add-On for Enhanced Test Management in Jira

0 comments

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events