AGENDA

1. What is Test Management?

2. Various Industry Proven Test Management Tools
3. Life Cycle of Test Case
4. Explore Test Link
i. Create Project
ii. Create Requirement
iii. Create Test Case
iv. Add Test Steps
v. Create Test Suite/Plan
vi. Execute Test Case
vii. Execution Report
5. Requirement Traceability
6. Defect Linking Process
WHAT IS TEST MANAGEMENT

• Important part of software quality is the process of testing and validating the software
• Test management is the practice of organizing and controlling the process and artifacts required for the testing
effort.
• Test Management is a series of planning, execution, monitoring and control activities that help achieve project
goals
TEST MANAGEMENT STAGES

Test Execution

Test Plan
Dashboards
Management

Test
Management
Build
Management Tool Test Result
Monitoring

Test Case
Automation
Management
VARIOUS INDUSTRY PROVEN TEST MANAGEMENT TOOLS

• Qtest
• QACompete
• PractiTest
• Meliora Testlab
• Qmetry Test Management
• Test Flo
• Aqua
• TestLink
• Quality Centre / ALM
• TestLodge
• TestRail
• Zephyr
LIFE CYCLE OF TEST CASE
Requirement Analysis

Test Planning

Test Case Development Delete(if duplicate)

Test Case Review Deprecate(If not valid)

Update(review comments)
Ready to test

Ready to test

Test Execution

Test Closure

COPYRIGHT SAPIENTRAZORFISH | CONFIDENTIAL 5

HOW TO WORK WITH T ES T L I N K

• Create a Project

• Create Test Cases (Test Suites) for this Project

• Create Test Plan

• Specify Build of the Project you are going to test

• Add Test Cases to the Test Plan

• Assign Test Cases to Test Engineers

• Execute Test Cases (Test Engineers)

• See Reports and Charts

HOW TO WORK WITH T ES T L I N K

A d d i t i o n a l fa c i l i t i e s :

• Assigning Keywords (we may form a group of Test Cas e s for Regression tests)

• Specifying Re q u ire m e n ts (we m ay bind t h e m with Test Cas e s in t h e manytomany

relation a n d see if our Test Ca s e s cover o u r re q u ire me nts )

• Eve nts log (you ca n see h e re t h e history of all t h e changes)

S T E P 1. CREATE A P R O J E C T

• To cre ate a project go to t h e Test Project M a n a g e m e n t section:

S T E P 1. CREATE A P R O J E C T
S T E P 1. CREATE A P R O J E C T. IM PO RTA NT F I E L D S

• Name
• I D (used for forming a u n iq u e Test Ca s e s ID)
• Project D e s c r i p t i o n (wh at is t h e a i m of t h e Project, w h a t is t h e t a r g e t group, w h a t is t h e
b u s in e s s logic, w h a t is t h e Test Environment)

• E n h a n c e d fe a t u re s :
• R e q u i r e m e n t s f e a t u r e – we m ay specify re q u i re m e n t s a n d see if th ey a r e well-
covered by Test Ca s e s
• Te s t i n g p r i o r i t y – we m ay a s s ig n priority to Test Cas e s (high, me d iu m, low)
• Te st A u t o m a t i o n – we m ay specify w h e t h e r t h e t e s t should be performed m a n u a l l y
or automatically
S TE P2 : C R E A TE R E QU I R EM ENT

• Requirements Specification adding

 S T E P 3. C R EATE T E S T C A S E S

• Test Case Title

• Summary
• Precondition
• Execution type ( m a n u a l or a u to m a te d )
• Test importance (High, Me d iu m or Low)
S T E P 4: Add Test Steps
S T E P 5 : C re a t e Te st S u i t e / P l a n

• TestLink won’t allow you to execute Test S u ite s if you don’t cre ate a Test P l a n a n d specify
Test Build.
• Let’s begin from t h e P l a n
S T E P 5 : C re a t e Te st S u i t e / P l a n

• Unfortunately, only Test Cases, not Test S u ite s or t h e whole Test Specification can be
ad d e d to a Test plan. So, u n t i l you don’t select one s e p a ra t e TC t h e b u tt o n “Add to
Test Plans” will not appear.
S T E P 5 : C re a t e Te st S u i t e / P l a n

• T h e n you ca n choose w h a t Test P l a n s you w a n t to a d d t h e selected TC to.

S T E P 6: E X EC U T E T E S T S

• To s t a r t executing te s t s Test En g in e e r should go to t e s t Execution section:

• T h e n choose a TC a n d you will face:

S T E P 6: E X EC U T E T E S T S

• We m ay also connect Te s t L i n k with our bug tra ckin g syste m M a n t i s , t h e n

d u r i n g execution you will see:

• After click on “Create new bug”, creating the bug using Mantis user interface and reorganizing the
windows.

• QA engineer lin ks t h e defect ID on Testlink

S T E P 6 : E X EC U T E TESTS

• T h e n you ca n a s s ig n TC execution here:

• You ca n a s s ign t e s t cases to te s te rs a n d s e n d t h e m email notifiactions:

• Execution history is being saved:

STEP 7: Execution Report

• After t e s t case execution is finished you m ay see t h e re s u l t s of it

using Test Re p orts section

• O r here:
STEP 7: Execution Report

• After t e s t case execution is finished you m ay see t h e re s u l t s of it using Test Re p orts section
• You’ll face t h e following page:
STEP 7: Execution Report – sample Reports
R E QU I R EMENT TR A C E A BIL ITY M A TR I X

• Re q u i re m e n t t ra c e a b i l i t y i s a d o c u m e n t t h a t m a p s a n d t ra c e s u s e r re q u i re m e n t w i t h
te st ca s e s .
• The main purpose of Requirement Traceability Matrix is to see that all test cases are covered so that no
functionality should miss while doing Software testing.

Sample for Requirement traceability matrix

FSD ID Use case ID TestTHANK

case ID YOU
Req 1 UC -1 TC1
Req 2 UC -2 TC2
Req 3 UC -3 TC3
Req 4 UC -4 TC4
Req 5 UC -5 TC5
Req 6 UC -6 TC6
Req 7 UC -7 TC7