Bring requirements & test management process right inside ... · The red planet has two moons,...

Bring requirements& test management process right inside your Jira

deviniti.com/houston

http://deviniti.com/houston

Devinitiis 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.

About Deviniti

deviniti.com/houston ― 1

The process of testing in Jira brings to mind one of the most fascinating bodies of the solar system: Mars. The dynamic planet has much to explore, just like our test managements apps: TestFLO and Requirements and Test Management for Jira.

The red planet has two moons, Phobos and Deimos, which orbit around it. Likewise, RTM and TestFLO are Jira’s satellites when it comes to requirements documentation and testing. Mars is undoubtedly the most intriguing place for scientists, as many fly-bys and orbiters were sent to explore the planet’s surface. When it comes to tests, the teams are also always on the quest to find the perfect approach, and we never know what may come out. Last but not least, Mars is popularly considered a planet of war... and what is testing, if not a constant battle against bugs?

https://deviniti.com/houston

https://marketplace.atlassian.com/apps/1211393/testflo-test-management-for-jira?hosting=server&tab=overview

https://marketplace.atlassian.com/apps/1214235/testflo-automation-for-test-execution?hosting=server&tab=overview

https://marketplace.atlassian.com/apps/1220294/requirements-test-management-for-jira?hosting=server&tab=overview

2 ― deviniti.com/houston

While producing software, you need to use various tools and

technologies to plan your work cycle. We know that choosing the

best solutions requires a lot of time and experience. That’s why

we help companies to select the right tools, implement them and

run the Software Development Life Cycle (SDLC) to meet specific

requirements and needs. Proper SDLC implementation has

a crucial impact on the development process and the final results,

which include:

• Increasing work effectiveness

• Describing project’s vision and goals

• Creating understandable steps of the process

• Identifying potential issues and the ways to deal with them

• Identifying key metrics and performance indicators

• Limiting time waste and technical debt

Consulting

At Deviniti, we have

lots of experience

in implementing

complex IT solutions

in organizations of

various sizes and

industries.

Application Integration

We provide you with auto-

mated data and process

exchange by attaching

isolated applications or

data sources to already

existing environments.

License Management

We will optimize your

license costs considering

the expiring period of sup-

port by synchronizing

expiration dates of all your

licenses, and support you

with budget planning.

Services



Analytical workshops

We will visit you on-site, wherever you are, to help you clarify your

requirements, discover the goals and issues you need to address.

Together, we will craft a vision of the solution and identify:

• which requirements can be achieved simply through configuring

the Atlassian tools,

• which Atlassian Marketplace apps you will need,

• is there anything that requires custom development or scripting.

Training

You are using Atlassian tools in your company, but users find them too

complex and not very useful for their daily work? Deviniti is here to help

your users strengthen their knowledge and show them that Atlassian

tools are quite easy to use. Also, it may turn out that they are very helpful

in their daily work. Do not hesitate to contact with us in order to receive

more details about training services!

PMO

Our tailored project

management process

implementations have

helped our clients with

organizing their project

portfolios. Ask us about

our project manage-

ment approach.

ITSM

Deviniti experience

in ITSM consists

of implementing

complex IT solutions

to various organiza-

tions and companies

to handle all your

daily challenges.

Support

Deviniti provides

support service that

will help you with all

your needs, ques-

tions or doubts. This

will ensure that you

keep the highest lev-

el of work efficiency.



Software 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.

PERMISSIONS

• define who can create and edit requirements, and plan the testing process

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

AGILE

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

• improve collaboration between analysts, testers, and developers

ISSUE TYPES

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

• use sub-tasks or custom issue types to distinguish requirement types

• combine test cases into test plans and schedule the executions

Benefits of managingrequirements and testsin Jira



LINKING ISSUES

• link related requirements to each other

• use it to link other Jira issues (e.g. bugs) to requirements

• document requirements by linking issues to Confluence pages

DASHBOARDS

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

• personalize and create your own gadgets using JQL

WORKFLOW

• 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)

Jira Query Language (JQL)

• browse issues collected in different projects, defining the search in detail

• personalize and create your own reports

project = TEST AND assignee in (currentuser())



A transparent structure for your requirements is just

as 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.

• elict requirements from multiple sources

• organize and prioritize requirements

• prepare requirements for validation

• make sure all stakeholders are in agreement

• invest in change impact analysis

Requirements and test management are key to a successful software development project.



• verify which features generated most defects

• clearly report your test results to other stakeholders

• define your business goals

• define relationships between tests, bugs and other objects

• create a test repository as a Jira project

• write test cases with step-by-step instructions

• combine test cases into test plans and pass them on to your testing team

• execute tests, add comments, attach files and create defects from the failed steps



Requirements and Test Management for Jira adds Requirements, Test Cases, Test Plans,

Test Executions, and Defects modules to your software projects inside the Atlassian

suite Using Jira objects for managing requirements and tests allows to seamlessly link

requirements, test cases, and defects to development Epics and user stories. This solution

has many advantages for each team member involved in testing process.

Requirements and Test Management for Jira

For Test Managers:

• helps increase efficiency of the QA team,

• allows to monitor the project progress every step on the way,

• enables tracking coverage of Requirements and make sure

nothing was omitted.

For IT Analysts:

• supports working on Requirements-related tasks,

• provides with transparent, understandable test reports,

• simplifies verifying relations between the objects,

• makes it possible to keep track of all the changes.

For Testers:

• doesn’t require any additional training,

• speeds up the whole process by making it fully intuitive,

• clarifies what and how is to be tested,

• allows to clearly report Defects from the failed Test Steps.



Test Cases

All

1.2.1.3. Microgravity training

1

2

3

1.2.1.2. ¼r¹a²±i®® car²iac t¹»t»

1

2

3

1.2.1.1. Èo²y r¹»Ëon»¹» to »tr¹»» an² ¹Æ¹rtion

1

2

3

1.3.3. à×¹®ta ×ÝÕà ±¹a»Òr¹±¹nt»

1

2

3

1.3.2. ëttitÒ²¹ Ëointing

1

2

3

1.3.. �¹Ëaration öro± t�¹ crÒi»¹ »tag¹

1

2

3

1.3.�. �ara±¹t¹r ÒË²at¹»

1

2

3

1.3.1. 3ina® tra(¹ctory corr¹ction ±an¹Òv¹r»

1

2

3

1.3.B. �tart oö ¹ntryD ²¹»c¹ntD an² ®an²ing ;¹�avio...

1

2

3

1.2. ¼�¹ UrÒi»¹ ��a»¹

1. noyag¹ t�roÒg� »Ëac¹ to Mar»

1.1. �r¹�®aÒnc� t¹»t»

1.2.1. �¹a®t� c�¹c�»

1.3. ëËËroac� to Mar»

1.B.2. ¼¹»t co±±Ònication» �it� �art�

1

2

3

1.B.1. U�¹c� Martian t¹±Ë¹ratÒr¹»

1

2

3

1.B. �Òröac¹ ÝË¹ration»

1.2.2. Ua®i;ration oö t�¹ »Ëac¹craöt

1.2.3. ëttitÒ²¹ corr¹ction

1.2.B. ×¹t¹r±ining t�¹ ö®ig�t Ëat�

1.2.�. Uo±±Ònication t¹»t»

Create tree structures of requirements and tests

RTM for Jira allows you to structure Requirements,

Test Cases, Test Plans, Test Executions and Defects

into transparent tree folders.


Add folders per field value, like Assignee, Sprint, Component, Team, etc.

Drag and drop items organizing them as you see fit.

Quickly navigate and edit your objects.




RQ-11.2.1.3. Microgravity training

Test project / Requirements / Microgravity training

Test Cases RelationsDetails

Functional requirement

1

2

3

Type oÔ

requirement:

Status

Assignee:

Priority:

Labels:

Descripton

Created:

Reporter:

Last updated:

Components:

3/14/2019 9:08 AM

As an Astronaut I can eat, drink, and use various kinds of onboard shuttle equipment

in an antigravity capsule for 2 hours, so I could be sure that I'm able to survive in

spacecraft internal conditions.

Katherine Johnson

3/14/2019 9:08 AM

RTM

Alan jhepard

Low

Trainings |ealt~xc~ecvs

BACKLOG

Requirements


Plan your work better by creating user stories.

Prioritize Requirements and achieve your project’s main goals faster.

Creating Requirements is the first step in the software development

process. RTM for Jira makes it possible to manage this stage in the

same place as all the subsequent ones. Also, the app lets you display

your Requirements on your board, just like regular Jira issues.




New Test Case

Test project / Test Cases / New Test Case

StepsDetails Requirements

Steps

# Action

+ Add next step

Input Expected result

Secure the crew member

The crew member enters the code to

get into capsule

Check if the crew member is able to

control the cursor on the laptop screen

1969

Check time of response to visual

stimulation

Add above Add below Add group

1

2

3

4

5

Import from CSB

Check time of response to audio

stimulation

The crew member controls the cursor

on the laptop screen

The crew member responds to visual

stimulation

The crew member responds to audio

stimulation

Preconditions

• Create microgravity conditions

• Provide laptop computer in the capsule

• Provide headphones in the capsule

• \se a reaction time box

Remove Step

Add group

Clone Step

Test Cases


Editing Test Cases with one click and ordering their steps

by drag and drop makes the testing experience effortless

with this app. Moreover, you can link one Test Case with

several Test Plans so they can act like templates.

Set preconditions.

Create a step-by-step procedure.

Import the Test Steps from a .csv file.




Traceability Matrix

This is a special panel which lists issues of one type and verifies their associations with

another issue type. The report enables you to verify if all Test Cases are included in Test

Plans and Test Executions, see which issues generated Defects, and finally see the

coverage of Test Plans by Test Executions.


(TST) Test Cases / (RQ) Functional Requirements

Test Cases (X-axis)

49% 51%

Functional Requirements (Y-axis)

34% 66%

Is covered y / Covers

Export

1

2

3

T

S

T

-

1

1

2

3

T

S

T

-

f

1

2

3

T

S

T

-

3

1

2

3

T

S

T

-

4

1

2

3

T

S

T

-

5

1

2

3

T

S

T

-

6

1

2

3

T

S

T

-

m

1

2

3

T

S

T

-

q

1

2

3

T

S

T

-

9

1

2

3

T

S

T

-

1

1

2

3

T

S

T

-

1

1

1

2

3

T

S

T

-

1

f

1

2

3

T

S

T

-

1

3

1

2

3

T

S

T

-

1

4

1

2

3

T

S

T

-

1

5

1

2

3

T

S

T

-

1

6

RQ - 1

RQ - f

RQ - 3

RQ - 4

RQ - 5

RQ - 6

RQ - m

RQ - q

RQ - 9

RQ - 1

RQ - 11

RQ - 1f

RQ - 13

1 1 2 1 1 1 1 3 0 3 1 1 1 2 3

1

1

4

1

3

5

4

0

2

0

0

1

0

Check the percentage of cover-age for both X and Y axes.

Verify the number of relations for a given object.

Check rela-tions between testing objects at a glance.




Comfortably set up Test Execution of your Test Plan and execute them with just one click.

Approach to Mars TP-1

Test CasesDetails Executions Relations

Add Test Case

Test project / Test Plans / Sprint-June / Chrome / TP-1 Login

Key Summary

PRJ-71 Test communications æith Earth

PRJ-7� Final trajectory correction maneuvers

PRJ-7% Attitude pointin'

PRJ-73 "Delta DOR" measurements

PRJ-111 Start oQ entryY descentY and lanRRR

PRJ-73 Parameter updates

PRJ-111 Separation Qrom the cruise sta'e

PRJ-72 Check Martian temperatures

Execute Cancel

Execute

Are you sure you æant to execute PRJ-7x�

Issue Type

Test Execution

Same assi'nee Qor Test Case in execution

Assi'nee

Katherine Johnson

Environment

The Martian atmosphere

Start date

2019/09/11

End date

2019/09/2%


Test Plans and Test Executions

Test Plans include all related Test Cases and are linked to the appropriate

Requirements. Test Executions have the same structure as Test Plans -

they also contains a Test Cases list, where it’s possible to monitor the

current status of each Test Case Execution.

Easily include all related Test Cases into Test Plans.




Test project / Test Execution / Sprint 4 / The Martian atmosphere / TP-1 Approach to Mars

Summary Result Priority

TP-1 Approach to Mars

33%

Environment:

The Martian atmosphere

Cases executed:

5/9

Assignee: all Result: all

Search

IN PROGRESS

IN PROGRESS

PASSED WIT...

BLOCKED

TO DO

IN PROGRESS

FAILED

PASSED

PASSED

s Detail RelationsTest Cases

Space sickness occuredDFK-8

Upload attachment

Add comment

Test project / Test Execution / Sprint 2 / Free fall capsule / TP-3 dealth checks (#2 execution)

Steos Details Relations

Preconditions

Defects

Steps

• Create microgravity conditions

• Provide laptop computer in the capsule

• Provide headphones in the capsule

• Use a reaction time �ox

1.2.1.3. Microgravity training

Change steps status

# Action Input Expected result

To do

6 Turn the freefall experience on

30 seconds

7 Test the a�ility of para�olic flights

8 Verify medical check-ups

Failed

Pa¸¸ed

4

Check time of response to audio

stimulation

The crew mem�er responds

to audio stimulation

The astronaut lasts 30 seconds

experiencing a simulation of Martian

gravity

No space adaptation syndrome (space sickness)

Pa¸¸ed

1 Secure the crew mem�er

1969

Pa¸¸ed with..2

The crew mem�er enters the

code to get into capsule

The crew mem�er controls the

cursor on the laptop screen

5

Check time of response to visual

stimulation

The crew mem�er responds

to visual stimulation

Pa¸¸ed

3

Check if the crew mem�er is a�le to

control the cursor on the laptop screen

Remove

Screenshot_v01.png

Attachment.zip Remove

The astronaut can't control the cursor on the laptop screen. Remove

Failed

In Progress

Passed

Passed with restrictions

Blocked

To do

Test communications with Earth

Check Martian temperatures

Final trajectory correction maneuvers

Attitude pointing

"Delta DOR" measurements

Start of entry, descent, and lan...

Parameter updates

Separation from the cruise stage

Microgravity training

Test Case Executions


Test Case Execution is the process of executing Test Cases included in Test Plans and

monitoring the status of each Test Step. The transparent table enables complete

tracking and helps spot possible bugs and fix them right away.

Easily access the results of each Test Case Execution.

See the overall progress of a given Test Execution.

Add attachments and comments for failed steps.

Check which Test Case Executions generated Defects.





Test Cases Import

Upload File

File first line is header

Stop after first issue that could not be created

Create missing versions components

Test Cases Import

Demo

*Select £TM pro�ect

Test£ail

*Select tool from �hich «ou are importing Test Cases

Unicode �UTF��

*Select file encoding

;

*Select values separator

*Attach a file to import

Drop files to attach, or browse.

UploaB

file

Map

fields

Confirm Progress

Test Cases Import

Upload

file

Map

fields

Confirm Progress

Map fields

Column site from qcsc RTM Fields

ID (Not Mapped)

Title Summary

Description Description

Estimate Estimate

Preconditions (Not Mapped)

Priority (Not Mapped)

Steps (E�pected Result) Steps panel� column E�pected Result

Steps (Input data) Steps panel� column Input

Steps (Step) Steps panel� column #ction

Components (Not Mapped)

Labels (Not Mapped)

ReAuirements (Not Mapped)

E�ecute Cancel

Select a tool from the drop-down list or adjust your file to the required format.

Put a .csv file on the file dropzone.

Map your .csv file columns to Jira fields.

You can import your Test Cases from another testing app into

RTM. Thanks to this, you’ll be able to migrate from your legacy

external tool much faster and easier.




Reports from Executions


Customize your reports with flexible filters.

Export the results to a .pdf or a .csv file.

Test Execution

Test Execution Report faseª on DEM:-2�¬

Blocked

23 (16%)

Fail

8 (6%)1,4 (1%)

In progress

12,9 (9%)

Pass

5,7 (4%)

Passed �i� res�ric�ions

92 (64%)

To do

Demo

Project

T(E RTM En.ironment

Test p2an

T(E (reate Date

Execution

T(E Assi<nee

Generate

Export

A

p

p

r

o

a

c

h

t

o

M

a

r

s

(

#

1

e

x

e

c

u

t

i

o

n

)

A

p

p

r

o

a

c

h

t

o

M

a

r

s

(

#

2

e

x

e

c

u

t

i

o

n

)

A

p

p

r

o

a

c

h

t

o

M

a

r

s

(

#

3

e

x

e

c

u

t

i

o

n

)

A

p

p

r

o

a

c

h

t

o

M

a

r

s

(

#

4

e

x

e

c

u

t

i

o

n

)

A

p

p

r

o

a

c

h

t

o

M

a

r

s

(

#

5

e

x

e

c

u

t

i

o

n

)

A

p

p

r

o

a

c

h

t

o

M

a

r

s

(

#

6

e

x

e

c

u

t

i

o

n

)

A

p

p

r

o

a

c

h

t

o

M

a

r

s

(

#

7

e

x

e

c

u

t

i

o

n

)

A

p

p

r

o

a

c

h

t

o

M

a

r

s

(

#

8

e

x

e

c

u

t

i

o

n

)

A

p

p

r

o

a

c

h

t

o

M

a

r

s

(

#

9

e

x

e

c

u

t

i

o

n

)

A

p

p

r

o

a

c

h

t

o

M

a

r

s

(

#

1

0

e

x

e

c

u

t

i

o

n

)

100%

90%

80%

70%

60%

50%

40%

30%

20%

10%

0%

(RTM-3) Approach to Mars Execution

From 2018-05-22 to 2018-11-25The Martian atmosphere

(RTM-38) Approach to Mars (#1 execution)

Test Case Execution

Test Case Execution Report �aser on DEM�-2:/

Blocked Fail

23 (16%) 8 (6%) 1,4 (1%) 12,9 (9%) 5,7 (4%) 92 (64%)

In progress Pass Passed �i� resricions To do

Demo

Project

TCE RTM En.ironment

(RTM-3) Approach to Mars Execution

Test pMan

From 2018-05-22 to 2018-11-25The Martian atmosphere

TCE Create Date

(RTM-38) Approach to Mars (i1 execution)

Execution

TCE Assi�nee

From 2018-05-22 to 2018-11-25

(RTM-38) Approach to Mars (i1 execution)

Generate

Export

12,9 (9%)

Pass

Pass

Fail

To do

The Test Execution report displays the overall progress of testing for the succeeding

Executions. The Test Case Execution report, on the other hand, allows to check the status

of each Test Case. Both are fully customizable and generated on transparent charts with

tables below. In addition to reports from Executions, the app also provides you with two

relation tracking features: Traceability and Requirement Coverage reports.




TestFLOTest Management for Jira

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.

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 projects that store requirements.



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.

TestFLO - Test Management for Jira




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. Use the preconditions

repository. Share repositories between different projects.

Take advantage of the flexible Steps panel. Configure it according to your

needs - set columns and define statuses. Change statuses with one click.


Preconditions

Uploaded product data to the store’s website

View the search window

A user logged in as an Administrator

Steps

#

1

Action Input

Expected result Status

Enter the product name.

2

Select a product from the list.

3

Enter the price of the product in the “price to” box

Autocomplete list appears.

Product name is filled.

Price entered.

4 Click on search button

List of searched product

appears

There’s no “price to” label. Should it be on the screen?

Comment

no_search_list.png

Files

OSA-897

Defects

Passed

Passed

Passed

Failed

Export to CSV Edit

Edit

Add comment

Upload attachment

Create defect

Link defect

Add and reuse preconditions from the repository.

Bulk change statuses.

Perform actions directly on single steps.




Test Repository

Organizing tests is vital to keep the test management process transparent

and efficient. Test Repository is a custom multi-level structure of folders used

to categorize tests. Common operations like create Test Case Template, Add

to Test Plan and Create Test Plan are available directly from folders.


All

Version 1.2

Enter JQL to filter templates

T Key Summary Requirement Component/s Status

30 of 69

Version 1.2 / Basket

Uncategorized (5)

Version 1.1 0 (20)

Version 1.2 0 (�)

Regression tests 21 (21)

Basket 10 (10

Product 43 (43)

Order 1 (1)

Version 1.3 0 (0)

Version 2.0 0 (0)

Ot er 0 (0)

Select all 0 Selected

OSA(%5 OSA(10S opping >asket icon a=aila>le from any. ere on t e site BasketK Order ACTQVE

OSA(V0 OSA(3Alter quantity to zero in t e >asket Basket

Basket

Basket

Basket

Basket

Basket

Basket

Basket

Basket

ACTQVE

OSA(� OSA(3Alter quantity of products after adding to >asket

ACTQVE

OSA(% OSA(3Add t e same product to >asket after remo=ing it

ACTQVE

OSA(V OSA(3Remo=e a product from >asket

ACTQVE

OSA( OSA(2Add t e same product multiple times to >asket ACTQVE

OSA(5 OSA(2Vie. >asket ACTQVE

OSA(4 OSA(2Add multiple products to >asket from different searc results ACTQVE

OSA(3 OSA(2Add multiple products to >asket from same searc results ACTQVE

OSA(2 OSA(2Add a product to >asket ACTQVE

OSA(10 OSA(24Send a request for product a=aila>ility Ot erK Product ACTQVE

Version 1.2 / Product

Eipand folde^

Collapse folder

Create Test Case Templatv

Create Test Plaz

Add to Test Plan

Add su>(folde^

Rename folde^

Delete folder

Use common actions on folders.

Organize and reorder with drag and drop.

JQL search.




Requirements Testing

TestFLO doesn’t introduce any new issue types for requirements, but allows

to map any issue type to be a requirement. The view of requirement issue

displays all related testing objects - Test Case Templates, Test Cases, Test Plans

and Defects. It also provides common operations to create a new Test Case

Template or Test Plan with Test Cases.


CommentEdit Assign More AdminTo Do DoneIn Progress

Details

Des¾ription

As a fiance employee I want to view analytics about orders and revenue so I can see how we are tracking against our goals

Deäe¾ts

Tests înder Eêe¾ution

Atta¾�ments

Type:

Priority:

Affects Version/s

Status:

Resolution:

Fix Version/s:

Done

1.4.0

Component/s:

Labels:

Sprint:

Story Points:

OSA Sprint 3

10

High

None

Reports

Finance xmployee

DONE

Story

T Key Summary

1-1 of 1

P Assignee Reporter Status

OSA-622

T�e das�board tab does not display Julius Hibbert Jimbo Jones

IN PROGRESS

1 issues

T Key Summary TC Status

OSA-609 View das�boards wit� total order ¾ount and total dollar amountOSA-583 /

OSA-608

Adjust range wit� options od Today, T�is Mont�, Last 30 days, Last 90 days and T�is YearOSA-583 / Pass

Fail

2 issues

1-2 of 2

Configure columns. View details of related test objects.

Create tests and Test Plans related with a requirement from the More menu.




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.


All

Iteration Iteration progress Executions count

Comments Work Log History Acti�ity Steps Progress Test Plan Iterations

#2 2

Execution of Summary Ste�s �rogress Execution status Assignee Details

OSA-627

Generate VAT invoice

100%

Pass

OSA-629

Ad]ust range _ith o�tionU

of Today, This Month, Last

30 Days, Last 90 Days and

This Year

100%

Pass

#1 3

Execution of Summary Ste�s �rogress Execution status Assignee Details

OSA-627


100%

Fail

OSA-62i


100%

Pass

OSA-629

Ad]ust range _ith o�tionU

of Today, This Month, Last

30 Days, Last 90 Days and

This Year

100%

Fail

View test execution details.

View the progress of a single execution and whole iteration.




Test Plan Iterations Report

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.


Test Plan Test �ase Execution passed

Test Plan µnterations ¹eport

Summary

Test Execution Results - 98% completed

Quick filters TP for iöS

Switch report

Test Plans

1

Test �ases

1!

Executions

61

Fail

16

Pass

44

Open

1

#8 (0%) #7 (93%) #6 (100%)

26%

#5 (0%) #4 (87%) #3 (100%) #2 (78%)

Generating confirmation - E-mailSAs3-118SAs3-118 75%

N/A

Generating confirmation - P�� fileSAs3-116SAs3-118 43%

N/A

Three attempts to log in with incorrect dataSAs3-115SAs3-118 100%

N/A

�aunch the application on the iPA� 768x1024SAs3-113SAs3-118 100%

N/A

�aunch the application on the iPhone 6 375x667SAs3-112SAs3-118 40%

µnstalling the application on iöSSAs3-111SAs3-118 100%

N/A

�hanging the language of the application P�-ENSAs3-110SAs3-118 100%

N/A

�hanging the language of the application EN-�ESAs3-109SAs3-118 75%

N/A

�eleting an e-mail message from the User’s inboxSAs3-108SAs3-118 75%

N/A

Sending an e-mail message from the User’s e-mail accountSAs3-107SAs3-118 100%

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

Analyze aggregated status of all executions.

Sort Test Cases by passed execution ratio.

Click and view the execution details.




Requirement Test Execution Report

Verifying requirements is 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.


Requirement Key Summary Execution status Test Cases Defects

Requirement Test Execution Report

Summary

Test Executions Results - 20% executed

Quick filters 1.4.0

S�itc report

Requirements

10

Passed

2

Failed

5

Not executed

2

No tests

1

Product rating 0 0

OSA-624 NV TESTS

Comment a product 6 1

OSA-62X Fba`

Analytical reports 16 2

OSA-25 Fba`

Request for product availalility 9 0

OSA-24 NVT E�E��TE�

Revie� products 6 0

OSA-19 NVT E�E��TE�

Vat invoice 9 0

OSA-2X PbSS

Revie� orders 9 0

OSA-22 PbSS

Contact �it Administrator 9 1

OSA-21 Fba`

Loyality Points 12 2

OSA-20 Fba`

Receive e-ne�sletters 6 1

OSA-1£ Fba`

20% 50% 20%10%

Filter requirements by Fix Version or JQL filter.

Test execution status based on related Test Cases.

View related Test Cases and defects.




Advanced Workflows

Working with tests in TestFLO is closely related to workflows. Use new

conditions, validators and post functions to build an accurate and

efficient test management solution. Add Jira workflow properties

to statuses to get even more control over single steps of your testing

process.

Post function: Perform Approve transition on Test Case while making Approve transition on a Test Plan.

Condition: Tester cannot start executing a Test Case if the Test Plan is not on in progress status.

Validator: Creating a test without steps is forbidden.

Post function: Set all steps to Pass when performing the transition to the Pass status.





Test Automation

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.

TestFLO Automation for Test Execution

Executebuild plan

Run Build with TestsJenkins/BambooContinuous Integration (CI)

Build Plan

Test Results


https://marketplace.atlassian.com/apps/1214235/testflo-automation-for-test-execution?hosting=server&tab=overview


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

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

requirements and tests 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.

1

2

3


We always try to do our best to help teams create amazing things

whilst working with Jira Software. Apart from delivering services

and supportive, user-friendly apps, we like to share our knowledge

on our blog and with all kinds of tutorials and guides.

Go to deviniti.com/blog to learn more tips and tricks about

managing requirements and tests in Jira.

Easily tracing the path from your requirements to defects

through tests and development issues can prevent

possible bugs on the “left side” of the development

process.

Given its range of functionalities, Jira offers a cost-effective

entry to its platform. By comparing the pricing of jira

with a dedicated app to any external test management

tool, you’re bound to see that choosing Jira for your test

management makes much sense.

4

5

Get in touch with usto take full advantageof Atlassian products

1. Find our apps on the Atlassian Marketplace

2. Try our apps in a free 30-day trial

3. Book a demo session calendly.com/deviniti

deviniti.com/[email protected]

Deviniti Sp. z o.o. 2019 All Rights Reserved

https://marketplace.atlassian.com/vendors/39038/deviniti

http://calendly.com/deviniti

http://deviniti.com/houston

mailto:support%40deviniti.com%20?subject=

Bring requirements & test management process right inside ... · The red planet has two moons,...

Documents

Transcript of Bring requirements & test management process right inside ... · The red planet has two moons,...