Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

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,465,644
Community Members
 
Community Events
176
Community Groups

An Overview of the QARAJ Test Process

QARAJ is an add-on that integrates Jira with QARA Enterprise – a test automation tool developed by The Digital Group– and adds advanced test management capability to the Jira interface. The testing related functionality of QARAJ can be used in several ways, which includes using it for project teams with advanced test processes or even for teams that are new to the implementation of a test process. Given below are some examples of test processes that, if followed, can make it easy for you to incorporate testing into your project. In addition to the examples given below, you may also choose to create your own test processes based on the requirements of your test team.

1] Test Process with Basic Execution Planning

This is what you need to group your test executions into Test Cycles, which helps you keep a track of the testing that has been completed, and what all has already been tested. It also helps you keep a tab on the issues and failures in the test case execution process and how much of it is still left to be done. This is a step that requires meticulous planning to set up the Test Cycle(s) in a particular Version and then to ensure that each test execution is recorded against those Test Cycle(s).

2] Test Process with Structured Execution Planning

The next step is Test Process with structured execution planning and it is all about the setting up of the Test Cycle(s) and also includes getting involved in the process of the creation/modification of a large number of test cases. In addition to this, it also includes addition of test cases to the respective Test Cycle(s) for execution in future. You are also allowed to execute the test cases during the dedicated execution stages of the project.

A Structured Test Process, as the name implies, allows for distinct phases of organization, planning, execution and tracking of all your testing efforts.

3] Structured Test Process

Moving on to the last section, a Structured Test Process, just as its name suggests, allows for 4 distinct phases, as given below:

  1. Organization
  2. Planning
  3. Execution
  4. Tracking of all your testing efforts

Here we shall look into each of these phases.

i] Organization Phase:

The Organization phase involves import, reuse, modification, cloning and creation of test cases. This phase also involves linking the test cases to different issue types, including epics, stories, requirements, etc. This phase also involves organization of test cases on the basis of Versions, Labels and Components.

ii] Planning Phase:

The Planning phase involves setting up of different Test Cycles, and adding to these Test Cycles the test cases that require execution. The tasks performed during the planning phase, which basically involves grouping of the test cycles, helps in the easy tracking of the test cases.

 iii] Execution Phase:

The Execution phase basically involves the actual execution of the test cases within the many Test Cycles, and each execution is carried out methodically. This phase also involves linking to existing issues and bugs, along with filing new ones and tracking the progress of the test case execution.

 iv] Tracking Phase:

The Tracking phase is all about tracking the progress and other parameters associated with test case execution. There are metrics that keep track of the organized test case executions. You also have Test Cycle summaries that indicate progress as well as the quality of the application. The summary report is available in various formats.

So, that was about the Test Process of QARAJ. Have you tried QARAJ yet? To get add-on from the Atlassian Marketplace, click here.

0 comments

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events