DEVINITI.COM 01 · Our Certified Experts are ready to apply their experience and support your efforts with the Atlassian Stack and digital transformation in your company. Training

DE VINITI .COM 01

DE VINITI .COM DE VINITI .COM02 03

Bring requirements & test management process right inside

your Jira

d e v i n i t i . c o m / a t l a s s i a n

About Deviniti 4

Benefits of managing requirements and tests in Jira 6

Key to successful software development 8

Requirements and Test Management for Jira 10

TestFLO - Jira Test Management & QA Tool 18

Bring your whole software project inside Jira 26


Consulting

Our Certified Experts are ready to apply their experience and support your efforts with the Atlassian Stack and digital transformation in your company.

Training

We have 14 years of experience in sharing knowledge to Atlassian software users and administrators - online and offline, worldwide including onsite in your company.

Implementation

We realize your concept of how you

want to work as software tools in no time.

License management

We will optimize your technology stack cost by helping choose the best Atlassian products and apps set, remembering about the expiring period of support, periods synchronization or support with budget planning.

Custom development

Do you have requirements which can not be fulfilled by Atlassian products out of the box or by any app on Atlassian marketplace? We extend Atlassian products for more that 10 years providing dedicated solutions.

Migrations

We know all the ins and outs of migrating Atlassian tools between server and cloud hostings, migrating between environments or databases.

Find out how you can increase the teamwork effectiveness in your company with

the help of Atlassian tools and our apps: deviniti.com/atlassian

About Deviniti

Deviniti is an IT company based in

Wroclaw, Poland.

Established in 2004, we continuously develop

our business and build expertise to provide

state of the art software services.

More than 5000 companies in 103 countries have trusted our resolutions and implemented them

successfully for ~5 million end users.

We became an Atlassian Solution Partner of

Platinum and Enterprise status, as well as a

Gold Top Vendor in the Ecosystem.


• create special types for different types of requirements and test objects

• use sub-tasks to add and manage requirements

• add test cases to the test plan by creating them as sub-tasks

• define who can create and edit requirements, and plan

the testing process

• create groups in line with the team roles (managers,

analysts, testers)

• browse issues collected in different projects, defining the

search in detail

• personalize and create your own reports

• link related requirements to each otheruse it to link other Jira issues (e.g. bugs) to

requirements

• document requirements by linking issues to Confluence pages

• track work progress in defining requirements and performing tests

• create statuses that are consistent with the workflow in your team

• mark requirements as "done" in Jira when they are met (and related issues

have been resolved)

ISSUE TYPES

• plan your backlog, sprints, and track your team progress

• improve collaboration betweenanalysts, testers, and developers

PERMISSIONS

AGILE

WORKFLOW

LINKING ISSUES

Jira Query Language(JQL)

• follow the progress of work in projects, analyzing statuses and generating useful charts

• personalize and create your own gadgets using JQL

DASHBOARDS

MANAGERS

TESTERS

ANALYSTS

project = TEST AND assignee in (currentuser())

Benefits of managing requirements and tests in JiraSoftware testing process doesn’t need to be excluded from the software you use to organize

all your work and documents. With how flexible Jira is when it comes to extending its

possibilities, you can have all the necessary tools and objects in one place, without the

need to integrate it with external software. Make yourself comfortable by managing your

requirements and tests in Jira.


Requirement and test management processes are key to a successful software development project. A transparent structure for your requirements is justas important as an accurate method for testing them. The two processes are closely related with each other because they focus on the quality of your product.


Requirements and Test Management for Jira

Requirements and Test Management for Jira is a brand new app which

adds Requirements, Test Plans, Test Cases and Test Executions panels to

your software project in Jira. This allows you to track the whole development

process from collecting requirements to going to production in a single

place, while your teams get a single place to work in. If you’re stuck with

legacy heavyweight test management tools or just starting the testing

journey with your team, the app wil provide you with a single repository

for your requirements and tests – even for multiple projects at a time.

Using Jira objects for managing requirements and tests allows to

seamlessly link requirements, test cases and defects to development

Epics and user stories, and search for them like for regular Jira issues. This

approach also ensures end-to-end traceability of your requirements, which

can prevent possible bugs on the “left side” of the development process.

The Test Plans created inside the app are reusable, and you can create Test

Executions and Defects quickly from the parent views.

ANALYZERequirements

WRITETest Cases for Requirements

DESIGNTest Plans which

contain Test Cases

EXECUTETest Plans in one

or more Test Executions

SETstatuses of Test Case Executions

REPORTDefects

CHECKtraceability

TRY THIS FEATURE IN A FREE 30-DAY TRIAL TRY THIS FEATURE IN A FREE 30-DAY TRIAL

Available on Atlassian Marketplace marketplace.atlassian.com Available on Atlassian Marketplace marketplace.atlassian.com


Tree-structured folders Requirements

1.1. Functional requirements

1. Requirements

Requirements

All

1.1.1 Way of logging into app

1.1.1.1. Login & password

1.1.1.2. PIN code

1.1.1.3. Touch ID

1.1.1.4. Face ID

1.1.3.1. Via E-mail

1.1.3.2. Via SMS

1.1.2. Blocking app due to login

1.1.3. Sharing account number

1.1.4. Payment confirmation

1.1.5. Accessibility for ederlu p

1.1.6. Mailbox in the app

1.1.7. Notifications

1.2. UI requirements

1.2.1 Responsive design

1.3.1 Using localization

1.4.1 mobile payments / digital

1.3. Non-functional requirements

1.4. Business requirements

Details Test Cases Relations

Comments History

There are no comments yet on this issue.

The user can log in using the email and password

Type of requirement:

Status:

Functional requirement

Low

None

3/14/2019 9:08 AM

3/14/2019 9:08 AM

RTM

John Langford

Lisa Bravo

BACKLOG

Assignee:

Priority:

Labels:

Created:

Last updated:

Components::

Reporter:

Test project / Requirements / Login & password

1.1.1.1. RQ-1 Login & password

Attachments

Activity

Comment

Description

Drop files to attach, or Browse

With Requirements and Test

Management for Jira , you can

structure Requirements, Test Plans,

and Test Cases into transparent tree

folders. Such a structure is clear and

understandable for everyone, easy to

navigate, and enables you to drag and

drop items organizing them as you see fit.

Beside that, you can add folders per field

value, like Assignee, Sprint, Component,

Team, etc.

Requirements are your first step in the software development process. They help you with

planning your work, creating user stories and Test Cases, and give you insight into what

needs to be done to achieve your project’s goal. To make managing and tracing the progress

easier for you and your team, you can create requirements as regular Jira issues that are

displayed on your Scrum or Kanban board. Moreover, you can easily navigate in-between

the requirements and track their correct implementation.

Requirements and Test Management for Jira Requirements and Test Management for Jira




Test Cases Traceability

Expected result

Test project / Test Cases / New Test Case

Details

Open Google Chrome (Version 72.0) browser.

Open https://deviniti.com/login Login page is open

Above “login” field is hint for user “please fill your login”

Under “login”field is label“login”

Check hint above “login” field

Check hint above “password” field

Check label under “login” field

Add next step+

Fill the “login” field

[email protected]

Login & password group

Create another Create Cancel

Action# Input

Add above

1

Preconditions

Steps

Steps Requirements

New Test Case

Add below Add group

Import from CSV

...

2

3

4

5

Add step above

Add step below

Add group above

Upload attachment

Copy step

Remove step

Test Cases determine actions you should take to cover Requirements. It’s a step-by-step

procedure that will help you with executing Test Plans later on in the process. Editing Test

Cases with one click and ordering their steps with drag and drop makes the whole experience

effortless. Moreover, you can not only include Test Cases in Test Plans, but also easily link

one Test Case with several Test Plans.

Traceability panel enables you to choose types of relations that will be displayed on the

Traceability Matrix. In this section, you can check which requirements are linked with which

Test Cases or which Test Plans include which Test Cases.





Test Plans and Test Executions Test Case Executions


After a Test Case Execution is finished, you can easily access its result. The report from the

Test Case Execution is clear and understandable, enabling you to track progress of executing

each step of the Test Plan, as well as to see where the process failed and why.

Each testing process needs a Test Plan where you include all related Test Cases and their

linked Requirements. By linking different Test Cases to your Test Plans, you can effortlessly

prepare various scenarios for them. After creating Test Plans, you can easily execute them

with only one click. Test Executions have the same structure as Test Plans - there is a Test

Case list, where you can monitor the current status of the Test Case Execution. Also, you can

check the Test Plan Details, check and set Relations between the elements, as well as assign

a Test Execution to a certain person.


Keep your test repository, test execution and requirements in separate Jira projects or manage everything

inside a single project. You can also combine those elements according to your needs.

1. Simple solution

One of the easiest concepts for implementation.

Everything is part of a single Jira project. You can

manage tests, requirements and create bugs in one

place. This approach works well in projects with small

teams.

2. General test management

This approach aggregates all test management issues

into a separate project. The test repository and test

executions can be located in a single project and used

in many other development projects. To combine the

test management project with others, just select the

project/s that store requirements.

Jira project

Testmanagement

Requirements project


3. Many applications

In this concept, every development

project has a corresponding test

management project. TestFLO’s project

configuration allows to indicate project/s

with requirements for every test

management project individually, as well

as to point the project where you will be

creating defects.

4. Separate test repository

This approach gives you the opportunity to create a test repository in a dedicated project. TestFLO

configuration allows to enable each Test Management module separately. With an individual test

repository, you can decide which groups of users can design test cases and which will execute them in

other projects.

You can scale this solution to

one central test repository for

all projects or define many test

repositories - one per project.

Test management

Test management



Test repository

Development project

Another app of ours, TestFLO, represents a slightly different approach to testing in

Jira. This one is highly integrated into the Jira issue view and uses custom fields and

workflows to manage and execute tests. This approach makes TestFLO the most

customizable testing tool which can be adjusted to the most excessive demands of

the team. If you have a mature and complex software testing process which you’d

like to have the most control of, it will become your favorite tool ever.

TestFLO- Jira Test Management & QA Tool




Preconditions and Steps

The Preconditions panel lets you define a transparent bullet-point list that informs what

has to be done prior to test execution. You can add common preconditions to a repository

directly or from the issue view and reuse them afterwards. To avoid making repetitive work, you

can also share precondition repositories between different projects.

Writing test steps is one of the most basic yet most important activities, which is covered by

the flexible Steps panel. You can decide about the number of columns and define your own

statuses. Take advantage of adding comments, attachments and defects to single steps to make

your process more accurate. Speed up test execution using bulk status change.

TestFLO for Jira TestFLO for Jira

Test Plan Iterations

Performing multiple test cycles is a common practice in the software testing process.

Thanks to Test Plan Iterations, you can reuse the same set or subset of Test Cases for

retesting based on the selected strategy. Create a new iteration for all Test Cases, only failed

ones, those that didn’t pass or simply select them by hand. Analyze the history of Test Plan

Iterations on a Test Plan tab, or go to a Test Case and evaluate its executions.




Test Plan Iterations Report

TestFLO for Jira TestFLO for Jira

Using Test Plan Iterations not only gives you the benefit of having the execution history of

your Test Plan and Test Cases. Take advantage of the Test Plan Iterations report to dive

deeper and analyze the test execution matrix with all iterations from one or multiple Test

Plans. Evaluate metrics of passed executions for iterations and single Test Cases for better

overview of testing. Filter Test Plans by Fix Version or a saved JQL filter to report your work

in given context.

Requirement Test Execution Report

Verifying requirements in one of the most important aspects of software testing. When you

are releasing a version, you always want to be sure, that all of the Test Cases linked with

requirements included in this version scope are tested and passed. Requirements Test

Execution Report lets you analyze requirement included in a certain version in terms of

testing. View the aggregated state of testing with quantitative metrics and a transparent

progress bar, but also validate single requirements listed in the report.

Test Plan Execution Report

Summary

Test Case execution progress - 77% completed

Test Plans Test Cases Pass Fail Execution Not executed

3Blocked

2Retest

14 35 20 445

Quick filters 1.4.0

Switch report

Test Case Key Summary Status Requirements Defects

60% 14% 11% 8% 5% 2%

Print report for all open orders since the last time I printed the report

0

0

0

0

0

0

0

1

Print all packing lebels for open orders since the lasttime I printed labels

Electronically integrate with shipper’s system togenerate tracking numbers

See the status of the order

View a list of open and completed orders

Navigate to the details of the order

Email with latest products

Add reviews to a purchased products

OSA-637

OSA-636

OSA-635

OSA-632

OSA-631

OSA-630

OSA-620

OSA-619

OSA-16

OSA-17

OSA-17

OSA-22

OSA-22

OSA-22

OSA-18

OSA-19

Blocked

Retest

Execution

Execution

Pass

Pass

Fail

Not executed




Agile ready testing Test Automation

Execute build plan

Run Build with TestsJenkins/Bamboo

Continuous Integration (CI)

The concept of TestFLO is heavily based on Jira and allows to make use of various Jira

built-in functionalities. One of them are agile boards. These boards can be easily adjusted to

software testing with the configuration of status columns and custom fields brought by the

app. Using Jira agile boards makes your testing process transparent as you can easily track

Test Plans and Test Cases along with the most important data.

Automated tests are playing a major role in modern software testing processes. TestFLO

can be extended with an app called TestFLO Automation which lets you trigger a build plan

in Jenkins or Bamboo directly from Jira. Results of automated tests run with the build are

automatically imported to a Test Plan and created as Test Cases. The Test Plan can be reused

multiple times, and the Test Cases will be updated with latest results, which makes TestFLO

Automation great for smoke and regression testing.

To Do

QUICK FILTERS

OSA Testing

OSA Sprint 3

In Progress Blocked Failed Passed

Board

13 sub-tasks

0 days remaining Complete Sprint

0%

Version 1.4.0 - Build 3.0. - Safari

Navigate to the details of theorder

OSA-584

OSA-630

IN PROGRESS

Not executed

7 sub-tasks Version 1.4.0 - Build 3.0. - Internet ExplorerOSA-583 IN PROGRESS

8 sub-tasks Version 1.4.0 - Build 3.0. - FirefoxOSA-583 CLOSED

7 sub-tasks Version 1.4.0 - Build 3.0. - ChromeOSA-581 CLOSED

100%

Print all packing labels for open orders since the last time Iprinted labels

OSA-636

Retest

0%

Print a report for all open orderssince the last time I printed thereport

OSA-637

Blocked 100%

View a list of open andcompleted orders

OSA-631

OSA-634

Fail

0%

Use loyalty pointsOSA-615

Blocked

33%

Electronically integrate withshipper’s system to generatetracking numbers

OSA-635

Execution

25%

Add reviews to a purchasedproducts

OSA-619

Execution

100%

Contact with AdministratorOSA-610

Execution

0%

See the status of the orderOSA-632

Pass

0%

Email with latest productsOSA-630

Pass

100%

Display loyalty pointsOSA-616

Pass

100%

Generate VAT invoiceOSA-612

Pass

100%

Adjust range with options ofToday. This Month. Last 300 days.Last 90 Days and This Year.

OSA-631

OSA-638

Fail

TestFLO for Jira TestFLO Automation for Test Execution


As a manager, you can track the complete

software development process in Jira from start

to finish, which also gives all your teams a single

place to work in.

If your teams are already using Jira for development

tasks, it makes sense to adapt the tool to cover

test management as well. You can be sure that

your team knows how to make the most of Jira, so

there’s no need to invest in any extra training.

Using Jira objects for managing requirements and

tests allows to seamlessly link requirements, test

cases and defects to development Epics and user

stories, and search for them like for regular Jira

issues.

Here are 5 reasons why moving your requirements and test

management into Jira is highly beneficial for your team:

Bring your whole software project inside Jira

1

2

3

DE VINITI .COM028

Documents

DEVINITI.COM 01 · Our Certified Experts are ready to apply their experience and support your efforts with the Atlassian Stack and digital transformation in your company. Training