You are on page 1of 52

User Manual

TestLink version 1.9


Version: 1.18
Status: Updated for TL 1.9
2004 - 2010 TestLink Communit
!ermission is "ranted to #op$ distri%ute and&or modif t'is do#ument under t'e terms of t'e ()U *ree +o#umentation
Li#ense$ Version 1.2 pu%,is'ed % t'e *ree Soft-are *oundation. -it' no /n0ariant Se#tions$ no *ront-Co0er Te1ts$ and
no 2a#k-Co0er Te1ts. T'e ,i#ense is a0ai,a%,e in 3()U *ree +o#umentation Li#ense3 'omepa"e.
Revision History
# Description Date Author
0.1 +o#uments for TL 1.4 and update for TL 1.5 2004 6. 7a0,8t
9. 6orsin"
*. 6an#ardi
1.0 Con0erted to ::2 format. 2004&0;&12 6. 7a0,8t
1.1 6inor update. */< ;=2$ ;42 2005&02&14 6. 7a0,8t
1.2 Updated as draft for TL 1.= 2005&11&1= 6. 7a0,8t
1.; >emo0ed TL 1.5 terms
9dded initia, information a%out Custom *ie,ds
200=&0;&01 *. 6an#ardi
1.4 9dded #ontent and updated *ran#is#o?s @AumpstartBmanua,C and
t,Bfi,eBformat.
(enera, st,e #,ean-up and update.
200=&09&05 6. 7a0,8t
1.4 (enera, update and restru#turin". added Test Suite #'apter.
reDuirements report
200=&12&1= 6. 7a0,8t
1.5 :0era,, ,an"ua"e re0ie- 2008&01&24 E. !o,,ans
1.= 6inor update. 9dded se#tion /mport Test Cases from F1#e, 0ia <6L
Gprepared % !remH
2008&02&02 6. 7a0,at
1.8 Update to TL 1.8 draft 2008&04&15 6. 7a0,at
1.9 Update some ne- features 2008&0=&21
2008&08&18
6. 7a0,8t
1.10 Update for 1.8 >C; 01&14&09 6. 7a0,8t
1.11 Update for 1.8 >C4 02&14&09 6. 7a0,8t
1.12 Update for 1.8.0. /mport&F1port 0;&14&09 6. 7a0,8t
1.1; Update a##ordin" to issues 04&01&09 6. 7a0,8t
1.14 Update a##ordin" to issues GTL 1.8.2H 04&;0&09 6. 7a0,8t
1.14 Updated #'apter @Custom fie,ds: Fstimated and 9#tua, e1e#ution timeC
% D0ii
9dded pa"e num%ers
04&05&09 6. 7a0,8t
1.15 6inor updates a##ordin" to User feed%a#k 2;&05&09
09&12&09
6. 7a0,8t
1.1= Update for 1.9. !,atforms. /n0entor 08&01&10 6. 7a0,at
1.18 >emo0ed /mport&F1port as t'is information is dup,i#ated in e1terna,
do#ument
04&0;&10 6. 7a0,at
- 2 -
Table of Contents
1 (enera, information 4
1.1 :0era,, stru#ture 4
1.2 2asi# Termino,o" 4
1.; F1amp,e of TestLink simp,e -ork-f,o- 5
1.4 S'ort-#uts =
2 Test !roAe#ts 9
2.1 Creatin" ne- Test !roAe#ts 9
2.2 Fdit and de,ete Test !roAe#ts 9
2.; /n0entor 10
; Test Spe#ifi#ation 12
;.1 Test Suites 12
;.2 Test Cases 1;
;.; Ie-ords 15
;.4 (enerate Test Spe#ifi#ation do#ument 1=
4 >eDuirement %ased testin" 18
4.1 90ai,a%i,it 18
4.2 >eDuirements Spe#ifi#ation +o#ument 18
4.; >eDuirements 19
4 Test !,ans 21
4.1 Create and de,ete Test !,an 21
4.2 2ui,ds 21
4.; Test Set - addin" Test Cases to Test !,an 22
4.4 >emo0in" Test Cases from Test Set 2;
4.4 Test e1e#ution assi"nment 24
4.5 !,atforms 29
4.= !rioritiJe testin" ;;
4.8 6i,estones ;4
5 Test F1e#ution ;5
5.1 (enera, ;5
5.2 )a0i"ation and settin"s ;5
5.; Test e1e#ution ;=
= Test >eports and 6etri#s 40
=.1 (enera, Test !,an 6etri#s 40
=.2 Kuer 6etri#s 41
=.; 2,o#ked$ *ai,ed$ and )ot >un Test Case >eports 44
=.4 Test >eport 44
=.4 C'arts 44
=.5 Tota, 2u"s *or Fa#' Test Case 44
=.= >eDuirements %ased report 44
=.8 7o- to add a ne- report 44
8 9dministration 45
8.1 User a##ount settin"s 45
8.2 >o,e !ermissions 45
8.; Test !,an assi"nment to users 4=
8.4 Custom *ie,ds 4=
9 /mport and F1port data 44
- ; -
1 General information
TestLink is -e% %ased Test Management sstem. T'is manua, s'ou,d ser0e as sour#e for
users to understand pro#esses$ terms and or"aniJation of -ork -it' TestLink. See t'e
Installation manual for more information a%out sstem reDuirements$ insta,,ation steps and
#onfi"uration. T'e ,atest do#umentation is a0ai,a%,e on ---.teamst.or" or
test,ink.sour#efor"e.net.
!,ease use our forum if ou 'a0e Duestions t'at t'e manua, doesn?t ans-er.
TestLink code is often faster than documentation and some contribution missed
appropriate description. Some enhancement are not described for this reason here.
Thank you for notify us via tracker.
11 !verall structure
T'ere are t'ree #ornerstones: Test Project$ Test Plan and User. 9,, ot'er data are re,ations
or attri%utes of t'is %ase. *irst$ -e -i,, define terms t'at are used t'rou"'out t'e
do#umentation and testin" -or,d.
1" #asic Terminology
Test Case des#ri%es a testin" task 0ia steps Ga#tions$ s#enarioH and e1pe#ted resu,ts. Test
Cases are t'e fundamenta, pie#e of TestLink.
- 4 -
Illustration 1: Test Project is the basic component in TestLink
Test Suite GTest Case SuiteH or"aniJes Test Cases to units. /t stru#tures Test Spe#ifi#ation into
,o"i#a, parts.
Test Suite replaces the components and categories in TL 1.6 and earlier.
Test Plan is #reated -'en ou?d ,ike to e1e#ute Test Cases. Test !,ans #an %e made up of t'e
Test Cases from t'e #urrent Test !roAe#t. Test !,an in#,udes 2ui,ds$ 6i,estones$ user
assi"nment and Test >esu,ts.
Test Project is somet'in" t'at -i,, e1ist fore0er in TestLink. Test !roAe#t -i,, under"o man
different 0ersions t'rou"'out its ,ifetime. Test !roAe#t in#,udes Test Spe#ifi#ation -it' Test
Cases$ >eDuirements and Ie-ords. Users -it'in t'e proAe#t 'a0e defined ro,es.
Test Project as called Product in TL 1.6 and earlier.
User: ea#' TestLink user 'as a >o,e t'at defines a0ai,a%,e TestLink features. See more in
#'apter @User 9dministrationC. /,,ustration 2 s'o-s #ommon a#ti0ities a##ordin" to user ro,es.
1$ %&ample of Test'in( simple )or(*flo)
1. 9dministrator #reates a Test +ro,ect @*ast *oodC and t-o users$ 9dam -it' ri"'ts
@LeaderC and 2e,a -it' ri"'ts @Senior TesterC.
2. Leader 9dam imports -oft)are Re.uirements and for part of t'ese reDuirements
"enerates empt Test Cases. 7e reor"aniJe t'em into t-o Test Suites: @*is'C and
@C'ipsC.
;. Tester 2e,a des#ri%es a test s#enario G#reate a #ontent of empt Test CasesH usin"
t'ese Test -pecification t'at is or"aniJed into Test Suites.
4. 9dam #reates ke-ord @>e"ression testin"C and assi"ns t'is ke-ord to ten of t'ese
Test Cases.
4. 9dam #reates a Test +lan @*is' L C'ips 1C$ #uil/ @*is' 0.1C and ,inks a,, Test Cases in
Test Suite @*is'C to t'is Test !,an. 7e assi"ns 'imse,f and 2e,a as resour#es to t'is Test
!,an too.
5. )o- de0e,opers produ#e a first %ui,d. 9dam and 2e,a e1e#ute and re#ord t'e testin"
-it' t'e resu,t: 4 passed$ 1 fai,ed and 4 are %,o#ked.
=. +e0e,opers make a ne- 2ui,d @*is' 0.2C and 2e,a tests t'e fai,ed and %,o#ked Test
Cases on,. T'is time t'ese a,, %,o#ked and fai,ed Test Cases passed. T'e retest a,so
a,, Test Cases -it' ke-ords @>e"ression testin"C in addition.
8. 9 manager of t'is team -ou,d ,ike to see t'e resu,ts. 9dministrator e1p,ains to 'im
t'at 'e #an #reate an a##ount 'imse,f on t'e ,o"in pa"e. 6ana"er does it. 7e 'as
defau,t @(uestC ri"'ts and #an see Test Results and Test Cases. 7e #an see t'at
e0ert'in" passed in t'e o0era,, report .-H and pro%,ems in 2ui,d @*is' 0.1C in a report
for t'at parti#u,ar 2ui,d.
1
9. Later$ de0e,opers fina,, add a,so @C'ipsC fun#tiona,it. 9dam #reates a Test +lan @*is'
L C'ips 2C. 7e #an reuse t'e first Test !,an as temp,ate. 9,, @*is'C Test Cases and ro,es
-i,, %e automati#a,, added. 7e #reate a ne- 2ui,d @*is' 1.1C and ,inks a,, @C'ipsC Test
Cases to t'is Test !,an too.
10. )o- testin" starts as usua,.
11. Later$ 9dmin #reates a ne- Test +ro,ect for anot'er produ#t @7ot +o"C. 2ut t'is is
anot'er test team and a different stor.
1 7e$ 'o-e0er$ #an edit not'in". .-H
- 4 -
10 -hort*cuts
TestLink 'as s'ort-#uts to speed up a na0i"ation. Use 9LT GM s'iftH M ke.
2
List ",o%a, a0ai,a%,e s'ort-#uts:
N'O 7ome
NsO Test Spe#ifi#ation
NeO Test e1e#ution
NrO >eports
NiO !ersona,
NDO Lo"out&Duit
NuO 9dministration Gadmin on,H
Create Test Case s'ort-#ut NtO is a0ai,a%,e in Vie- Test Suite pa"e.
!roser support: The used accesskey attribute is currently supported by the folloin"
2 /F on, se,e#ts t'e ,ink. Fnter ke must fo,,o-.
- 5 -
Illustration #: $unctionality overvie
eb brosers:
$irefo%
Internet &%plorer '( )*indos+ ,( )-ac+
-o.illa )*indos ( Linu%+
/etscape 6.1( )*indos+
0pera 1( )*indos ( Linu%+
1C2e/itor shortcuts
T'e ne1t s'ort-#uts are supported in edit te1t mode:
-hortcut Action
Ctr, M 9 Se,e#t 9,,
Ctr, M C$ Ctr, M /ns Cop to #,ip%oard
Ctr, M V$ S'ift M /ns !aste from #,ip%oard
Ctr, M <$ S'ift M +e, Cut
Ctr, M P Undo
Ctr, M Q >edo
Ctr, M I /nsert Link
Ctr, M E /nsert Link -itout popup of t'e dia,o"
Ctr, M 2 2o,d
Ctr, M / /ta,i#
Ctr, M U Under,ine
Ctr, M S'ift M S Sa0e
Ctr, M 9,t M Fnter *it Eindo-
Ctr, M L Rustif Left
Ctr, M > Rustif >i"'t
Ctr, M F Rustif Center
Ctr, M R Rustif 2,o#k
Ctr, M N1-4O 7eader 1-4 *ormat
Ctr, M 0$ Ctr, M ) !ara"rap' *ormat
Ctr, M S'ift M L To"",es %et-een 2u,,eted List$ )um%ered List and !ara"rap'
Ta%$ S'ift M Ta%
/n#reases and +e#reases G-it' S'iftH /ndent. /f #ursor is inside t'e te1t and
*CIConfi".+ekiTa%Spa#es S 0$ inserts t'e spa#es. /nside t'e ta%,es #ursor Aumps to
t'e ne1t&pre0ious #e,, or inserts t'e ne- ,ine if t'ere is no ne1t #e,,. /f #ursor is in
tit,e or 'eader$ Aump to t'e ne1t para"rap'.
S'ift M Spa#e )on-%reak spa#e GLn%sp.H
- = -
" Test +ro,ects
Test !roAe#ts are t'e %asi# or"anisationa, unit of TestLink. Test !roAe#ts #ou,d %e produ#ts or
so,utions of our #ompan t'at ma #'an"e t'eir features and fun#tiona,it o0er time %ut for
t'e most part remains t'e same. Test !roAe#t in#,udes reDuirements do#umentation$ Test
Spe#ifi#ation$ Test !,ans and spe#ifi# user ri"'ts.
Test !roAe#ts are independent and do not s'are data. Consider usin" Aust one Test !roAe#t for
one Test team and&or one produ#t.
$or e%ample: there are to test teams for one product: system testin" and inte"ration
testin". These teams ill share some test cases. 2ou should create one project for the
product. The ork of both teams ill be structured in to or more trees in Test
Specification and testin" results ill be collected to different Test Plans.
"1 Creating ne) Test +ro,ects
Creatin" a ne- Test !roAe#t reDuires 3admin3 ri"'ts. Se,e#t @ Test !roAe#t 6ana"ementC ,ink on
main pa"e and press @CreateC %utton.
Fa#' Test !roAe#t must 'a0e an uniDue name. T'ere is te1t area to #'ara#teriJe t'e o%Ae#t of
proAe#t. T'ere are se0era, features t'at are ena%,ed&disa%,ed on Test !roAe#t ,e0e,:
1. 9dmin #an ena%,e re.uirements re,ated fun#tiona,it.
2. 2a#k"round #o,ours #an %e assi"ned to Test !roAe#t temp,ates to 0isua,, distin"uis'
t'em.
/ote: The feature must be enabled in confi" at first.
;. Test prioriti3ation #ou,d %e ena%,ed to se,e#t appropriate testin" set in ,imited time.
4. Test automation support #ou,d %e ena%,ed as -e,,.
T'in"s to note -'en #reatin" a ne- Test !roAe#t:
+e,etin" Test !roAe#ts from t'e sstem is not re#ommended as t'is eit'er orp'ans a
,ar"e num%er of Test Cases or de,etes t'e Test Cases from t'e sstem.
Test !,ans represent t'e testin" of a Test !roAe#t at a #ertain point in time.
ConseDuent,$ Test !,ans are #reated from Test !roAe#t Test Cases. Ee do not
re#ommend to #reate separate Test !roAe#ts for 0ersions of one !rodu#t.
TestLink supports importin" <6L or CSV data into a Test !roAe#t. T'is is e1p,ained
furt'er in t'e /mport se#tion$ %e,o-.
"" %/it an/ /elete Test +ro,ects
Fditin" Test !roAe#ts reDuires 3admin3 ri"'ts. User #an #'an"e Test !roAe#t name$ #o,our of
%a#k"round and a0ai,a%i,it of reDuirements fun#tiona,it$ test prioritiJation and test
automation.
User #an inactivate t'e Test !roAe#t if it?s o%so,ete. T'is -i,, mean t'at t'e Test !roAe#t is not
0isi%,e in t'e ,ist -it'in t'e top na0i"ation %ar for #ommon users.
3dmin ill see this Test Project in the list marked by 454.
User #an a,so /elete a Test !roAe#t. T'is a#tion -i,, a,so de,ete a,, re,ated data from data%ase.
This action is not reversible Ee stron", re#ommend usin" ina#ti0ate instead of de,ete.
- 8 -
"$ Inventory
Users #an ,ist t'eir 'ard-are in ta%,e per proAe#t. T'e feature s'ou,d %e ena%,e on @Fdit
!roAe#tC pa"e. Leaders #an edit t'is pa"e % defau,t and testers #an %ro-se it on,.
;
/n0entor
,ink is a0ai,a%,e on 6ain !roAe#t pa"e in @Test !roAe#tC menu.
/n0entor pa"e offers t'ree a#tions: #reate$ update and de,ete.
Ta%,e s'o-s a,, de0i#es and a,,o-s sortin" on an fie,d.
Se,e#t @CreateC %utton to define a de0i#e. T'e ne1t parameters are supported:
7ost name GuniDue mandator 0a,ueH
/! address
!urpose Gsimp,e te1t -it' ma1ima,, 2000 #'ara#tersH
7ard-are Gsimp,e te1t -it' ma1ima,, 2000 #'ara#tersH
)otes Gsimp,e te1t -it' ma1ima,, 2000 #'ara#tersH
:-ner Goptiona,H #ou,d %e an%od -'o 'as at ,east 0ie- a%i,it
; 9dmin #an modif ro,es ri"'ts to e1tend t'ese ri"'ts.
- 9 -
Illustration ,: Inventory table ith sortin"
Illustration ': 3ctions on Inventory table
Illustration 6: /avi"ation to Inventory
Update and de,ete a#tion reDuires a se,e#ted ro-.
- 10 -
Illustration 6: 7reate a ne device into Inventory table
$ Test -pecification
TestLink %reaks do-n t'e Test Spe#ifi#ation stru#ture into Test Suites and Test Cases. T'ese
,e0e,s are persisted t'rou"'out t'e app,i#ation. :ne Test !roAe#t 'as Aust one Test
Spe#ifi#ation.
$uture consideration: e plan to implement the ne%t abilities: Test patterns8 revie
process and status of Test case8 variable Test case structure )for e%ample step by step
desi"n+.
$1 Test -uites
Users or"aniJe Test Cases into Test GCaseH Suites. Fa#' Test Suite #onsists of a tit,e$ formatted
des#ription Test Cases and possi%, ot'er Test Suites. TestLink uses tree stru#ture for Test
Suites. T'e #ommon pra#tise is t'at t'e des#ription 'o,ds information 0a,id for most of
in#,uded data.
*or e1amp,e$ t'e fo,,o-in" #ou,d %e spe#ified: s#ope of in#,uded tests$ defau,t #onfi"uration$
pre#onditions$ ,inks to re,ated do#umentation$ ,ist of too,s$ infrastru#ture o0er0ie-$ et#.
Creatin" one or more Test Suites is one of t'e first steps -'en #reatin" our Test !roAe#t.
Users G-it' edit ri"'tH #an #reate$ de,ete$ #op$ mo0e$ e1port and import %ot' nested Test
Suites and Test Cases. Tit,e and des#ription #an %e modified too.
Qou #an reor/er %ot' Test #ases and #'i,d Test Suites 0ia +ra" L +rop items on t'e na0i"ation
tree.
4

Practice: 7onsider structure of your test specification. 2ou could divide tests by
functional9non functional testin"8 particular features8 components. 2ou can chan"e the
structure later of course : move test suites ithout lost of any information.
Practice: Later versions of your product could have some features obsolete. 2ou can
create a special Test suite 40bsolete4 or 42our product ;.14 and move test cases there.
<eletin" of test case causes that earlier test results ill be deleted too.
9tta#'ments -it' e1terna, do#uments or pi#tures #ou,d %e added into parti#u,ar Test Suites.
4 /t reDuires F<T-RS #omponent Gdefau,tH.
- 11 -
Illustration 1: Test Specification is structured by Test Suites
/ote: The functionality must be alloed via TestLink confi"uration.
6ore information a%out import and e1port are in appendi1.
$3=: 7ould I copy9move Test suites beteen projects> 2ou cannot directly in this
version. *e desi"ned Test projects fully independent each from other. ?se import9e%port
as orkaround.
$" Test Cases
Test 7ase is a set of inputs$ e1e#ution pre#onditions$ and e1pe#ted resu,ts Gout#omesH
de0e,oped for a parti#u,ar o%Ae#ti0e$ su#' as to e1er#ise a parti#u,ar pro"ram pat' or to 0erif
#omp,ian#e -it' a spe#ifi# reDuirement.
Test Cases 'a0e t'e fo,,o-in" parts:
I/entifier of a Test Case is assi"ned automati#a,, % TestLink$ and #an not %e #'an"ed % users.
T'is /+ #omposes from Test !roAe#t prefi1 and a #ounter re,ated to t'e Test !roAe#t in -'i#' t'e
Test Case is #reated.
4
Title: #ou,d in#,ude eit'er s'ort des#ription or a%%re0iation Ge.". TL-USF>-L:(/)H
-ummary: s'ou,d %e rea,, s'ort. Aust for o0er0ie-$ introdu#tion and referen#es.
-teps: des#ri%e test s#enario Ginput a#tionsH. #an a,so in#,ude pre#ondition and #,ean-
up information 'ere.
$3=: 0ur test steps are pretty detailed are use a lot of formattin" comin" from
*ord. ?se @Paste from msord@ feature of $7Aeditor. It cleans "arba"e. )7onfi"ure
toolbar if not available.+
%&pecte/ results: des#ri%e #'e#kpoints and e1pe#ted %e'a0iour of a tested produ#t or
sstem.
Attachments: #ou,d %e added if #onfi"uration a,,o-s it.
Importance4 Test desi"ner #ou,d set importan#e of t'e test N7/(7$ 6F+/U6 and L:EO. T'e 0a,ue
is used to #ompute priorit in Test !,an.
5
%&ecution type4 Test desi"ner #ou,d set automation support of t'e test N69)U9L&9UT:69TF+O.
5
Custom fiel/s: 9dministrator #ou,d define o-n parameters to en'an#e Test Case des#ription or
#ate"oriJation. See 8.4 for more.
Lar"e #ustom fie,ds Gmore t'an 240 #'ara#tersH are not possi%,e. 2ut information #ou,d %e added
into parent Test Suite and referred 0ia #ustom fie,ds. *or e1amp,e ou #an des#ri%e Confi"uration
?standard?$ ?performan#e?$ ?standardB2? and refer 0ia C* to t'is ,a%e,s.
/ote: The development is planned to make a T7 structure more fle%ible in future.
Test Case * Active Attribute
/f se0era, 0ersions of a Test Case e1ist$ it -ou,d %e usefu, to 'a0e a ne- attri%ute$
9#ti0e&/na#ti0e$ to use in t'is -a:
F0er Test Case 0ersion is #reated 9CT/VF
9n /na#ti0e Test Case Version -i,, not %e a0ai,a%,e in 39dd Test Cases to Test !,an3.
T'is #an %e usefu, for Test +esi"ners. T'e #an edit or #'an"e t'e Test Case Version
and on, -'en 'e&s'e de#ides it is #omp,eted$ #'an"e Status to 9CT/VF so it -i,, %e
a0ai,a%,e to %e used in a Test !,an.
:n#e a Test Case Version 'as %een ,inked to a Test !,an$ and 'as resu,ts$ it #an?t %e
4 TestLink 1.= and ear,ier 0ersions 'a0e 'ad t'is /+ as a ",o%a, #ounter independent of t'e
Test !roAe#t. TestLink 1.8 sti,, uses t'is uniDue /+ for 9!/ #a,,s.
5 T'e feature must %e ena%,ed on Test proAe#t mana"ement.
- 12 -
turned /)9CT/VF.
-pell chec(er
Qou #an use -e% %ro-ser a%i,it. *irefo1 'as add-on for e1amp,e @2ritis' Fn",is' +i#tionarC or
amount di#tionaries for ot'er ,an"ua"es.
*CIeditor supports o-n so,ution. See t'eir +e0e,opers (uide for more.
9s ou #an note$ t'e num%er near Test !roAe#t name Gin t'is e1amp,e: toaster5&l6H is 2$ %ut
t'e Test !roAe#t 'as ; Test Cases. Test Case TC1 is not #ounted$ %e#ause is ina#ti0e.
Removing Test Cases
Test Cases and Test Suites ma %e remo0ed from a Test !,an % users -it' @,eadC permissions.
T'is operation ma %e usefu, -'en first #reatin" a Test !,an sin#e t'ere are no resu,ts.
7o-e0er$ remo0in" Test Cases -i,, #ause t'e ,oss of a,, resu,ts asso#iated -it' t'em.
T'erefore$ e1treme #aution is re#ommended -'en usin" t'is fun#tiona,it.
- 1; -
Illustration B: *hat you see in Test 7ase specification
Illustration C: *hat you see hen tryin" to add Test 7ases to a Test Plan
Re.uirements relation
Test Cases #ou,d %e re,ated to soft-are&sstem reDuirements as n to n. T'e @reDuirementsC
fun#tiona,it must %e ena%,ed for a Test !roAe#t. User #an assi"n Test Cases and >eDuirements
0ia t'e @9ssi"n >eDuirementsC ,ink in t'e main s#reen.
Test +lan relation
Test Cases #an %e assi"ned to parti#u,ar Test Plans for e1e#ution. Test Leader use @9dd &
>emo0e Test CasesC ,ink in main pa"e to se,e#t appropriate Test set. T'e ,ist of re,ated Test
!,ans are ,isted on t'e Vie- Test 7ase pa"e under tit,e @Test !,an usa"eC. See t'e s#reens'ot
%e,o-.
-earch Test cases
Se,e#t a ,ink @Sear#' Test CasesC in main pa"e Gse#tion: Test Spe#ifi#ationH. User #an use t'e
ne1t items to #ompose reDuired Duer:
Test #ase identifier
- 14 -
Illustration 1;: List of related Test Plans is listed on the @Die Test 7ase@ pa"e
Version of Test #ase
Ie-ord in tit,e
Ie-ord in Summar$ Steps and&or F1pe#ted resu,ts GEarnin": t'is sear#' simp,
parse te1ts in#,udin" 7T6L ta"s. *or e1amp,e ke-ord @'e,,o -ordC doesn?t find a te1t
@TpS'e,,o T%S -ordT&%ST&pSCH.
9ssi"ned ke-ord.
9ssi"ned reDuirement /+.
T'e resu,ted ,ist of in#,udes for ea#' Test #ase: re,ated parenta, Test SuiteGsH and a ,ink to a
Test #ase pa"e.
$$ 2ey)or/s
Ie-ords -ere #reated to "i0e users anot'er ,e0e, of dept' -'en #ate"oriJin" Test Cases.
Ie-ords are idea, for fi,terin". Ie-ords ser0e as a means of "roupin" Test Cases -it' some
attri%ute -it'in a Test Spe#ifi#ation. *or e1amp,e$ ou #an use it to define:
>e"ression set )or Sanity for ability to filter mandatory tests+
>e0ie-ed Test Cases )to indicate formal status+
So,aris )set of Test 7ases valid for one platform+
C'an"e reDuest 12;44 )related to ne features in specific release+
QourBprodu#t ;.2.1 )related to certain version of product+
/ote: 2ou could use also 7ustom $ields if you need more sophisticated usin".
Create a 2ey)or/
9t t'is time ke-ords #an on, %e #reated % users -it' t'e m"tEmodifyEkey ri"'ts. T'ese
ri"'ts are #urrent, 'e,d % ro,e Leader. :n#e a ke-ord or "roupin" of ke-ords 'as %een
#reated users ma assi"n t'em to Test Cases.
Fa#' proAe#t 'as o-n set of ke-ords.
Assigning 2ey)or/s
Ie-ords ma %e assi"ned to Test Cases eit'er from t'e assi"n ke-ord s#reen Gin %at#'H or
0ia t'e Test Case mana"ement Gindi0idua,,H.
1ilter by 2ey)or/
Users 'a0e t'e a%i,it to fi,ter % Ie-ords in:
)a0i"ation tree of Test spe#ifi#ation.
Sear#' Test Cases in Test Spe#ifi#ation.
9dd Test Cases in a Testin" Set GTest !,anH.
@F1e#ute testC pa"e.
Some reports a,so "i0e resu,ts -it' respe#t to ke-ords.
- 14 -
$0 Generate Test -pecification /ocument
Users #an "enerate t'e #urrent Test Specification as a do#ument. Use a ,ink from t'e main
pa"e. T'ere is stru#tura, options and possi%i,it to se,e#t a reDuired Test Suite or "et a,,
#ontent.
User #an #'oose do#ument format G7T6L$ :pen:ffi#e te1t do#ument or ms-ord do#umentH$
T:C$ Test suite data$ Test Case summar$ steps M e1pe#ted resu,ts$ and ,ist of re,ated
ke-ords and&or reDuirements.
- 15 -
Illustration 11: 0ptions for "enerated Test
Specification
0 Re.uirement base/ testing
To pro0e t'at a sstem is %ui,t as spe#ified$ testers use reDuirement %ased testin". *or e0er
reDuirement$ t'e desi"n one or more Test Cases. 9t t'e end of t'e test e1e#ution a test
mana"er reports on t'e tests t'at are e1e#uted and t'e reDuirements t'at are #o0ered. 2ased
on t'is information t'e #,ient and t'e 0arious stake'o,ders de#ide -'et'er a sstem #an %e
transferred to t'e ne1t test p'ase or #an "o ,i0e. Test mana"ers use a #om%ination of risk and
reDuirement-%ased testin" to ensure t'at a sstem is %ui,t as spe#ified from t'e #ustomer and
stake'o,ders perspe#ti0e. 9s a resu,t$ t'is #omp,ete testin" de,i0ers t'e fo,,o-in" ad0anta"es:
Linkin" risks and reDuirements -i,, re0ea, 0a"ue or missin" reDuirements. T'is is
espe#ia,, interestin" for risks -it' a 'i"' priorit.
Testin" #an %e fo#used on t'e most important parts of an information sstem first:
#o0erin" t'e risks -it' t'e 'i"'est priorit.
Communi#atin" in t'e same ,an"ua"e as t'e #,ient and t'e stake'o,ders. T'is makes it
easier to report on t'e status of t'e Test !roAe#t. T'en a %etter founded de#ision #an %e
made -'et'er to in0est more in testin" or take t'e risk.
T'e risks and t'eir priorit make ne"otiatin" on t'e Test !roAe#t in times of pressure
easier. E'at risks 'a0e to %e #o0ered -it'in t'is Test !roAe#t and -'i#' ones #an %e
postponed. >isk and reDuirement-%ased testin" resu,ts in a %etter #ontro,,ed Test
!roAe#t. T'e #ommuni#ation -it' t'e #,ient and t'e stake'o,ders is impro0ed. T'e test
mana"er %e"ins testin" -it' risks -it' t'e 'i"'est priorit. T'e pro#ess is stream,ined
and t'e end resu,t is 'i"'er Dua,it.
01 Availability
T'e fun#tiona,it is a0ai,a%,e at t'e Test !roAe#t ,e0e,. /.e. 9dministrator s'ou,d ena%,e it for a
spe#ified Test !roAe#t GFdit Test !roAe#t ,ink in 6ain -indo-H. :t'er-ise ,inks are not s'o-n.
T'ere are t-o user ,e0e,s for t'is feature. 6ost ro,es #an 0ie- reDuirements$ %ut not modif
t'em. >efer to User se#tion for more detai,s.
0" Re.uirements -pecification Document
>eDuirements are "rouped to one or more Sstem&Soft-are&User >eDuirement Spe#ifi#ations.
- 1= -
Illustration 1#: <ependencies beteen reFuirement related objects
Create a do#ument -it' >eDuirements:
1. C,i#k >eDuirements Spe#ifi#ation in 6ain -indo-. T'e ,ist of >eDuirement Spe#ifi#ations
is s'o-n.
2. !ress Create %utton to #reate a do#ument.
;. 9dAust Title$ Scope and e0entua,, Count of Test Cases. T'e ,ast parameter is used
for statisti#s. Use on, if ou 'a0e a 0a,id >eDuirement do#ument %ut not a,,
reDuirements are a0ai,a%,e at t'e moment in TestLink. +efau,t 0a,ue ?0? means t'at t'e
#urrent #ount of reDuirements in a spe#ifi#ation is used.
4. !ress Create %utton to add data to data%ase. Qou #an see t'e tit,e of our ne- #reated
do#ument in t'e ta%,e of ,ist of >eDuirement Spe#ifi#ations.
4. C,i#k t'e tit,e of do#ument for ne1t -ork. T'e >eDuirement Spe#ifi#ation -indo- is
s'o-n.
Fa#' >eDuirement Spe#ifi#ation 'as o-n statisti#s and report re,ated to in#,uded data.
9,, Spe#ifi#ations #an %e printed usin" t'e 3!rint3 %utton in t'e 3>eDuirement Spe#ifi#ation3
-indo-. 9dministrator #an define #ompan$ #opri"'t and #onfident te1t 0ia #onfi"uration fi,es.
*arnin": TestLink 1.B brin"s support of nGdepth tree structure for reFuirements )should
be enabled by confi"uration+. Hoever some related features )for e%ample
import9e%port8 document "eneration+ aren4t compliant ith this settin"s yet. These
features behaves like only direct child reFuirements e%ists and all inner sub folders are
i"nored.
0$ Re.uirements
Fa#' reDuirement 'as Tit,e$ S#ope G'tm, formatH and Status. Title must %e uniDue and 'as
ma1. 100 #'ara#ters. Scope parameter is te1t in 7T6L format. Status #an 'a0e t'e 0a,ues
V9L/+ or ):TBTFST92LF. 9 ):TBTFST92LF reDuirement is not #ounted in metri#s.
>eDuirements #ou,d %e #reated&modified or de,eted manua,, 0ia TestLink interfa#e or imported
as CSV fi,e.
- 18 -
Illustration 16: -ana"e a IeFuirements Specification
Import re.uirements
TestLink supports t-o tpes of CSV. T'e first ?simp,e? is #omposed from tit,e and s#ope in ea#'
ro-. T'e se#ond ?F1port from +oors? tries to dete#t t'e 'eader and #'oose t'e #orre#t fie,ds.
/mport #ompares tit,es and tries to reso,0e #onf,i#ts. T'ere are t'ree -as to do t'is: update$
#reate reDuirements -it' same tit,e and skip addin" t'e #onf,i#ted ones.
Re.uirements to Test Case relation
Test Cases are re,ated -it' soft-are&sstem reDuirements as U to U. /.e. ou #an assi"n one or
more Test Cases to one >eDuirement and one or more reDuirements #ou,d %e #o0ered % one
Test Case. User #an assi"n >eDuirements to Test Cases 0ia t'e 9ssi"n >eDuirements ,ink in t'e
6ain -indo-.
T'e #o0era"e of t'e Test Spe#ifi#ation #ou,d %e 0ie-ed 0ia pressin" t'e 9na,se %utton in t'e
>eDuirement Spe#ifi#ation -indo-.
Re.uirement base/ Report
)a0i"ate to >eports and 6etri#s menu. T'ere is a >eDuirements %ased >eport ,ink.
>eDuirements in t'e #urrent >eDuirement Spe#ifi#ation and Test !,an are ana,sed for t'is
report. T'e ,atest resu,ts of Test Cases Ga0ai,a%,e in Test !,anH are pro#essed for ea#'
reDuirement. T'e resu,t -it' t'e 'i"'est priorit is app,ied for t'e reDuirement. !riorities$ from
t'e 'i"'est to ,o-est$ are: *ai,ed$ 2,o#ked$ )ot >un and !assed.
Example of requirement coverage
3 reFuirement is covered by three Test 7ases. To of them are included in the current
Test Suite. 0ne passed and one as not tested for the !uild 1. /o IeFuirement has
overall result of /ot Iun. Second Test 7ase as tested ith !uild # and passed. So
IeFuirement passed too.
- 19 -
6 Test +lans
J3 record of the test plannin" process detailin" the de"ree of tester involvement8 the test
environment8 the Test 7ase desi"n techniFues and test measurement techniFues to be
used8 and the rationale for their choice.K
Test Plans are t'e %asis for test e1e#ution a#ti0it. 9 Test Plan #ontains name$ des#ription$
#o,,e#tion of #'osen Test Cases$ 2ui,ds$ Test >esu,ts$ mi,estones$ tester assi"nment and
priorit definition. Fa#' Test Plan is re,ated to t'e #urrent Test Project.
61 Create an/ /elete Test +lan
Test !,ans ma %e #reated from t'e Test Plan management pa"e % users -it' ,ead
pri0i,e"es for t'e #urrent Test !roAe#t. !ress @CreateC %utton and enter data.
Test !,an definition #onsists from title$ /escription G'tm, formatH and status @9#ti0eC #'e#k-
%o1. +es#ription s'ou,d in#,ude t'e ne1t information -it' respe#t to #ompan pro#esses:
Summar&S#ope
*eatures to %e tested
*eatures to not %e tested
Test #riteria Gto pass tested produ#tH
Test en0ironment$ /nfrastru#ture
Test too,s
>isks
>eferen#es G!rodu#t p,an or C'an"e reDuest$ Kua,it do#umentGsH$ et#.H
Test !,ans are made up of Test Cases imported from a Test Spe#ifi#ation at a spe#ifi# point of
time. Test !,ans ma %e #reated from ot'er Test !,ans. T'is a,,o-s users to #reate Test !,ans
from Test Cases t'at e1ist at a desired point in time. T'is ma %e ne#essar -'en #reatin" a
Test !,an for a pat#'. /n order for a user to see a Test !,an t'e must 'a0e t'e proper ri"'ts.
>i"'ts ma %e assi"ned G% ,eadsH in t'e define User&!roAe#t >i"'ts se#tion. T'is is an
important t'in" to remem%er -'en users te,, ou t'e #an?t see t'e proAe#t t'e are -orkin"
on.
Test !,ans ma %e de,eted % users -it' ,ead pri0i,e"es. +e,etin" Test !,ans permanent,
de,etes %ot' t'e Test !,an and a,, of its #orrespondin" data$ in#,udin" Test Cases Gnot in Test
Spe#ifi#ationH$ resu,ts$ et#. T'is s'ou,d %e reser0ed on, for spe#ia, #ases. 9,ternati0e,$ Test
!,ans ma %e dea#ti0ated on t'e same pa"e$ -'i#' suppresses disp,a on se,e#tion menus in
t'e @mainC and @F1e#uteC pa"es.
6" #uil/s
9n user -it' ,ead pri0i,e"es #ou,d fo,,o- t'e ,ink Build management in t'e main pa"e.
2ui,ds are a spe#ifi# re,ease of soft-are. Fa#' proAe#t in a #ompan is most ,ike, made up of
man different 2ui,ds. /n TestLink$ e1e#ution is made up of %ot' 2ui,ds and Test Cases. /f
t'ere are no 2ui,ds #reated for a proAe#t t'e e1e#ution s#reen -i,, not a,,o- ou to e1e#ute.
T'e metri#s s#reen -i,, a,so %e #omp,ete, %,ank.
- 20 -
Fa#' 2ui,d is identified 0ia tit,e. /t in#,udes des#ription G'tm, formatH and t-o states:
Active & Inactive V defines -'et'er t'e 2ui,d is a0ai,a%,e for TestLink fun#tiona,it. /na#ti0e
2ui,d is not ,isted in eit'er e1e#ution or reports pa"es.
!pene/ & Close/ V defines if Test Iesults #an %e modified for t'e 2ui,d.
2ui,ds #an %e edited G0ia ,ink under a 2ui,d tit,eH and de,eted G% #,i#k on t'e appropriate @%inC
i#onH in t'e ta%,e of e1istin" 2ui,ds.
6$ Test -et * a//ing Test Cases to Test +lan
Test !,an #ontent is defined % addin" a Testin" set Gof Test CasesH from Test Spe#ifi#ation.
Use a ,ink @9dd & >emo0e Test CasesC on t'e 7ome pa"e. Test Spe#ifi#ation data #an %e
fi,tered % ke-ords GadAusted in t'e na0i"ation paneH. :n#e data 'as %een ,inked into a Test
!,an it -i,, %e marked -it' #'e#k-mark.
- 21 -
Illustration 1,: Test 7ase navi"ation: Select an
appropriate Test Suite
Illustration 1': !uild mana"ement
User #an #'oose Test #ases 0ia #'e#k-%o1 and 'it @9dd se,e#tedC %utton to define Test Set.
C,i#k on t'e ?#'e#k? i#on to se,e#t a,, Test Cases in ea#' Test Suite. 9,, Test #ases #ou,d %e
added % #,i#k on ,a%e, under Test suite tit,e.
T'e #ertain 0ersion of Test Case is assi"ned to a Test !,an. User #ou,d update 0ersion for ,ater
testin" if t'e Test Case is updated. T'e #ontent of e1e#uted Test #ase 0ersion #ou,d not %e
modified.
/ote: There is basic rule: 0ne Test Plan has just one set of Test cases. So you can add
durin" testin" more ne Test cases. 3nd this affect metrics of older builds. In the most
of case this is not important difference. 2ou can to possibilities if you care about:
G 7reate a ne Test Plan for the second round.
G ?se Aeyords to reco"ni.e phases of testin" in one Test Plan.
User #an reor/er Test #ases -it'in Test Set. T'is modifi#ation 'as no inf,uen#e to Test
Spe#ifi#ation. 6odif num%ers in #o,umn @F1e#ution orderC and pus' @Sa0e orderC %utton.
60 Removing Test Cases from Test -et
Test Cases and Test Suites #an %e remo0ed from a Test !,an % users -it' ,ead permissions
from t'e 39dd & >emo0e Test Cases3 pa"e. >emo0in" data ma %e usefu, -'en first #reatin" a
Test !,an sin#e t'ere are no resu,ts. 7o-e0er$ remo0in" Test Cases -i,, #ause t'e ,oss of a,,
resu,ts asso#iated -it' t'em. T'erefore$ e1treme #aution is re#ommended -'en usin" t'is
fun#tiona,it.
- 22 -
Illustration 16: $rame for 3ddin" Test 7ases into Test Plan
66 Test e&ecution assignment
Qou #an assi"n Test 7ase for e1e#ution to different users. Test e1e#ution assi"nment affe#ts
%ot' t'e e1e#ution and reports. /n t'e e1e#ution s#reen users 'a0e t'e a%i,it to sort t'e
e1e#uta%,e Test 7ases to see t'e ones t'e 'a0e %een assi"ned. /n t'e reports t'ere is a ta%,e
t'at s'o-s t'e remainin" Test 7ases % tester. /f t'ere are no Test Case tester assi"ned it
defau,ts to none. 9 Tester #an a,so see t'e metri#s of 'is&'er o-n e1e#uted tests in main pa"e if t'ese
metri#s are ena%,ed Gsee /nsta,,ation manua,H.
)a0i"ate from t'e 'ome pa"e:
Usin" tree menu on ,eft frame$ ou #an #'oose a -'o,e test suite$ t'at -i,, %e disp,aed on
detai, on ri"'t frame.
- 2; -
Illustration 11: $rame for modifyin" content of test cases ithin Test Plan
/n t'is e1amp,e$ #,i#kin" on Transportation -i,, produ#e:
To assi"n a test #ase to an user$ fo,,o-in" steps must %e fo,,o-ed:
1. se,e#t test #ase$ usin" #'e#k %o1 on t'e ,eft of test #ase /+.
- 24 -
2. #'oose user$ usin" #om%o %o1 p,a#e on #o,umn -it' ,a%e, ?9ssi"n to?.
;. Use ?Sa0e? %utton to -rite se,e#tion on data%ase
To simp,if t'is task -'en ou need to assi"n a -'o,e test suite to an user$ %u,k user
assi"nment feature 'as %een de0e,oped.
User #an notif assi"ned testers V se,e#t #'e#k-%o1 @Send mail notification to testerC.
#ul( user assignment
2u,k user assi"nment is not rea,, different$ t'at norma, assi"nment. Usin" #,i#ka%,e ima"es
ou #an to"",e state of mu,tip,e #'e#k %o1es -it' one #,i#k. /n t'e ima"e disp,aed a%o0e$ ou
#an see fo,,o-in" 'e,p$ -'en ou put #ursor o0er ima"e present on t'e ,eft of test suite name.
C,i#kin" on t'is ima"e -i,, resu,t on a,, test #ases present on @TransportationC test suite and it?s
#'i,dren test suites$ %e se,e#ted as disp,aed on fo,,o-in" ima"e:
- 24 -
)e1t step is to #'oose user$ t'is -i,, %e done usin" %u,k assi"nment se#tion under test suite
name. T'en usin" ?<o? %utton$ #om%o %o1es of a,, #'e#ked #'e#k %o1es -i,, %e setted to
?admin?.
- 25 -
Last step$ to sa0e t'is -ork is #,i#k on ?-ave? %utton
9fter s#reen refres'$ ou -i,, see:
- 2= -
2u,k assi"nment$ #an %e a,so done Aust on test #ases %e,on"in" to a test suite -it'out affe#tin"
#'i,dren test suites.
9s an e1amp,e if ou -ant to #'an"e assi"nment$ on, on test #ases #'i,dren of @Hyper-paceC
test suite $ instead of usin" ima"e on t'e ,eft of test suite name:
67 +latforms
Platform des#ri%es a @unitC t'at test #ases #ou,d %e e1e#uted on. *or e1amp,e a p,atform
#an %e a -e% %ro-ser$ :S$ spa#es'ip$ 'ard-are de0i#e or #onfi"uration. 9 test p,an #an
'a0e asso#iated p,atforms -'i#' are #'osen -'en a test #ase is e1e#uted.
9 Test project mi"'t 'a0e se0era, platforms t'at needs testin". *or e1amp,e a -e%site needs
to %e tested in different %ro-sers$ or a soft-are needs to run on different operatin" sstems or
'ard-are de0i#es. TestLink #a,,s t'is #on#ept Platforms. Platforms are a -a of #onne#tin" Test
- 28 -
Illustration 1B: 7lick on suite checkGbo%
picture to select all include Test 7ases
cases in a Test plan to a spe#ifi# soft-are p,atform$ de0i#e or #onfi"uration.
To use t'e p,atforms feature$ some p,atforms must first %e #reated under 8Platform
Management Ga##essi%,e from t'e !roAe#t pa"eH. /t reDuires @p,atform mana"ementC ri"'t
Gon, admin #an % defau,tH. Created platforms #an %e assi"ned to parti#u,ar Test plans. G/f
ou 'a0en?t #reated a Test p,an et$ do t'is first.H
Se,e#t a Test p,an and #,i#k 8dd ! "emove Platforms. 9ssi"n p,atforms to a Test p,an %
mo0in" t'em to t'e ri"'t pane, and Sa0e.
)o- Test cases ma %e added to t'e Test plan. T'is is done in t'e same -a as norma,$ -it'
t'e e1#eption t'at a Test case must %e #'e#ked on#e for e0er platform it s'ou,d %e e1e#uted
on. *or e1amp,e: a Test #ase is to %e e1e#uted on %ot' p,atforms ?SS &nterprise and ?SS
Doya"er$ it must %e #'e#ked for a,, of t'ose p,atforms. See /,,ustration 20 %e,o-.
- 29 -
Illustration #;: 3ssi"n platforms to testplan
Illustration 1C: 7reate platforms in Platform -ana"ement
)e1t step is to assi"n users to e1e#ute t'e test #ases. Qou are free to asso#iate users as ou
-is'. :ne possi%i,it is to 'a0e a user to e1e#ute one test #ase on a,, p,atforms. 9not'er -a is
to ,et a user e1e#ute a,, test #ases on one p,atform$ or a mi1 of t'e t-o.
- ;0 -
Illustration #1: 3dd test case to test plan
Illustration ##: 3ssi"n users
E'en mu,tip,e p,atforms are used t'e e1e#ution step of TestLink "ets one additiona, fi,ter
option. 6ake sure t'e p,atform se,e#tion is set to t'e p,atform ou are "oin" to e1e#ute test
#ases on. 9s seen in /,,ustration 19 t'e tree %e,o- on, s'o-s t'e test #ases for t'e #urrent,
se,e#ted p,atform.
9fter e1e#ution t'e resu,ts uses t'e p,atform metri#s in t'e reports. )oti#e: a test #ase t'at is
,inked to t'ree p,atforms -i,, #ount as t'ree different test #ases in reports. T'e reason to t'is is
t'at it 'a0e to %e e1e#uted on#e per p,atform for fu,, test #o0era"e and t'is is ref,e#ted in t'e
resu,ts.
69 +rioriti3e testing
Test priorit is optiona, feature. (enera,,$ some features are ne- or 'ea0 de0e,opment -as
done. /t s'ou,d re#ei0e more attention. :n t'e ot'er side some features -as near, untou#'ed
in de0e,opment p'ase and on, test -it' t'e 'i"'est importan#e make sense to e1e#ute.
7onfi"uration: This feature must be alloed on Test Project level by administrator )JTest
project mana"ementK link on main pa"e+.
!arameter Test priority is defined as #om%ination Test Case Importance and -uite urgency
in a Test +lan. Test priorit is usa%,e as fi,ter settin"s for test e1e#ution and a,so reported in
metri#s.
TestLink "i0es users t'e a%i,it to assi"n Importance to Test Cases. T'ere are t'ree ,e0e,s:
Lo-$ 6edium Gdefau,tH and 7i"'. T'is 0a,ue is adAusta%,e durin" a test desi"n in Test
Specification.
- ;1 -
Illustration #6: $ilter on platform in e%ecution navi"ator
:rgency is se#ond parameter t'at affe#ts resu,ted Test Priority. Ur"en# is defined for a
#ertain Test Plan and is not depended on Test Importance. *o,,o- t'e ,ink @Set Ur"en#C at t'e
Test p,an menu Gri"'t side of proAe#t pa"eH. T'ere are a,so t'ree ,e0e,s: Lo-$ 6edium Gdefau,tH
and 7i"'.
?r"ency is not copied if you copy a Test Plan. 3 different set of ur"ency is e%pected.
TestLink #om%ines %ot' t'ese attri%utes into +riority ,e0e,s 7i"'$ 6edium and Lo-. !riorit
s'ou,d 'e,p to #'oose ri"'t set of e1e#ution to test at first. Test report @Test !,an metri#sC
in#,udes prioritiJed resu,ts t'en. 6i,estones a,,o-s to define "oa,s for t'ese t'ree ,e0e,s as -e,,.
Example# 3 serverGclient product JTamGtamK has to interfaces L?I and ebGL?I. &ach
user interface allos lo"in and8 press button J!umK and set colour of interface
back"round. Testers desi"n three Test 7ase for both interfaces )each interface has on
Test Suite+:
Lo"in )medium Importance+
!um action )hi"h Importance+
!ack"round colour )lo Importance+
3 TamGtam 1.; release has bu" in eb interface and hotGfi% is created. Testers needs to
test the product in really short time delivered. 3 mana"er decide to test only tests ith
Hi"h priority before deliver and others later. Test Plan for hotGfi% is copied from Test plan
for release 1.;. Testers has the same set of tests but Test leader set Test ur"ency of Test
Suite J*eb L?IK to Hi"h and J3pplication L?IK to Lo )because there is no chan"e+.
/o8 To tests have hi"h priority: Lo"in and J!umK action via eb interfaces. !um
action via application L?I receive -edium priority )Hi"h Importance8 but lo ur"ency+.
6; Milestones
Test ,eader #an define a mi,estone for #ertain date -it' a "oa, of e1pe#ted per#enta"e of
finis'ed tests. T'is "oa, #ou,d %e defined for t'ree ,e0e,s of priorit in t'e #ase t'at test
prioritiJation is a,,o-ed.
See @Test !,an metri#sC report to #'e#k a satisfa#tion of t'ese "oa,s.
- ;2 -
- ;; -
Illustration #': Test leader can define one or more milestones for a Test Plan
7 Test %&ecution
71 General
Test e1e#ution is a0ai,a%,e after:
1. 9 Test Spe#ifi#ation is -ritten.
2. 9 Test !,an is #reated.
;. Test Cases are added into Test !,an.
4. 9t ,east one 2ui,d is #reated.
4. Testers 'a0e appropriate ri"'ts for e1e#ution to -ork -it' t'e t'is Test !,an.
Se,e#t t'e @F1e#uteC ,ink in top menu or @F1e#ute TestsC ,ink in t'e -ain pa"e to na0i"ate to
t'e @Test F1e#utionC -indo-. T'e ,eft pane a,,o-s na0i"ation in Test Cases 0ia a tree menu$
and set-up settin"s and fi,ters. T'e e1e#ution -indo- s'o-s re,e0ant information and a,,o- to
add test resu,ts.
7" <avigation an/ settings
T'e na0i"ation pane #onsists of a ?*i,ter L Settin"s? %o1 and a tree menu -it' Test Case Suite.
Define a teste/ #uil/
Users s'ou,d spe#if one from a,, a#ti0e 2ui,ds to add resu,ts. T'e ,atest %ui,d is set % defau,t.
2ui,d ,a%e, spe#ified e1a#t pa#ka"e of produ#t under test for tra#kin" purpose. Fa#' Test Case
ma %e run more times per a 2ui,d. 7o-e0er it?s #ommon pra#tise t'at Aust one testin" round
is e1e#uted a"ainst a 2ui,d for a test #ase.
!uilds can be created by Test Leader usin" the 7reate /e !uild pa"e.
- ;4 -
-earch a Test Case
Users #an spe#if e1a#t t'e Test Case identifier to faster na0i"ation.
1iltering Test Cases
T'is ta%,e a,,o-s t'e user to fi,ter Test Cases for smart na0i"ation %efore t'e are e1e#uted.
Qou must 'it t'e @3pply filterC %utton to propa"ate a ne- fi,ter settin"s.
Tester: Users #an fi,ter Test Cases % t'eir tester. T'ere is a,so #'e#k-%o1 to see %ot'
t'e #'osen tester and unassi"ned Test Cases.
2ey)or/: Users #an fi,ter Test Cases % ke-ord. See ;.; Ie-ords.
Result: Users #an fi,ter Test Cases % resu,ts. >esu,ts are -'at 'appened to t'at Test
Case durin" a parti#u,ar 2ui,d. Test Cases #an pass$ fai,$ %e %,o#ked$ or not %e run.
Test priority: Users #an prioritiJe Test Cases.
Tree menu
T'e tree menu in na0i"ation pane s'o-s t'e #'osen ,ist of Test Cases in t'e Test !,an. /t
a,,o-s to open appropriate Test CaseGsH for test e1e#ution in t'e ri"'t frame. Test Suites in t'e
menu are en'an#ed % s'ort test status o0er0ie- %e'ind a tit,e G#ount of test #ases$ passed$
fai,ed$ %,o#ked and not-e1e#uted #ounterH #o,oured % resu,ts.
T'e tree menu #ou,d %e #o,oured for some tpes of used menu #omponent on,. 2 defau,t t'e
tree -i,, %e sorted % t'e resu,ts for t'e defined 2ui,d t'at is #'osen from t'e drop-do-n %o1.
&%ample T7 coloured accordin" to the !uild:
?ser selects !uild # from the dropGdon bo% and doesn4t check the @most current@ check
bo%. 3ll Test 7ases ill be shon ith their status from !uild #. So8 if Test 7ase 1 passed
in !uild # it ill be coloured "reen.
9 se#ond possi%i,it is t'at t'e menu is #o,oured a##ordin" to t'e ,atest Test >esu,t.
&%ample T7 coloured accordin" to the latest result
?ser selects !uild # from the dropGdon bo% and this time checks the @most current@
check bo%. 3ll Test 7ases ill be shon ith most current status. So8 if Test 7ase 1
passed in !uild 68 even thou"h the user has also selected !uild #8 it ill be coloured
"reen.
7$ Test e&ecution
Test -tatus
F1e#ution is t'e pro#ess of assi"nin" a resu,t Gpass$ fai,$ %,o#kedH to a Test Case for a spe#ifi#
2ui,d. 9 ?2,o#ked? Test Case is not possi%,e to test for some reason Ge.". a pro%,em in
#onfi"uration disa,,o-s to run a tested fun#tiona,itH.
Insert Test Results
Test >esu,ts s#reen is s'o-n 0ia #,i#k on an appropriate Test Suite or Test Case in na0i"ation
pane. T'e tit,e s'o-s t'e #urrent 2ui,d and o-ner. T'e #o,oured %ar indi#ate status of t'e Test
Case. Qe,,o- %o1 in#,udes test s#enario of t'e Test Case.
- ;4 -
The indication that the Test 7ase as updated or deleted in test Specification is not
supported after 1., version.
Updated Test Cases: TL 1.;.' version has indication by fla"8 that is missin" from 1.6
version. If users have the proper ri"hts they can "o to the J?pdate modified test caseK
- ;5 -
Illustration #,: $rame ith several results of one Test 7ase
Illustration #6: ?ser can select to
print only the last result
Illustration #1: The last result could be printed only
pa"e throu"h the link on main pa"e. It is not necessary for users to update Test 7ases if
there has been a chan"e )neer version or deleted+.
- ;= -
9 Test Reports an/ Metrics
Test >eports and 6etri#s are a##essed % #,i#kin" t'e @>esu,tsC or @Test reports and 6etri#sC
,inks on t'e main pa"e. >eports and 6etri#s are %ased on t'e se,e#ted Test !,an Gfrom #om%o
%o1 menuH. T'e pa"e t'at is disp,aed to t'e user in#,udes:
T'e rig$t pane -i,, %e popu,ated -it' instru#tions on 'o- to use t'e #ontro,s and 'o- ea#'
report is produ#ed.
T'e left pane is used for na0i"atin" to ea#' report and operatin" #ontro,s -'i#' effe#t 'o-
reports %e'a0e and are disp,aed. T'e %utton @!rintC initia,iJes printin" of t'e ri"'t pane Gno
na0i"ation -i,, %e printedH.
9,, test reports Ge1#ept #'artsH #an %e "enerated in 1 of ; format :
1. )orma, - report is disp,aed in a -e% pa"e G'tm,H
2. :pen:ffi#e Eriter V #a,,s :: Eriter to s'o- a report
;. :pen:ffi#e Ca,# - #a,,s :: Ca,# to s'o- a ta%,e %ased report
4. 6S F1#e, V#a,,s mi#rosoft F1#e, to s'o- a ta%,e %ased report
4. 6S Eord - #a,,s mi#rosoft -ord to s'o- a report
5. 7T6L Fmai, V send report to user?s emai, address
T'ere are #urrent, 11 separate reports to #'oose from$ t'eir purpose and fun#tion are
e1p,ained %e,o-. Current,$ t'ere are no reports -'i#' #ompi,e resu,ts a#ross mu,tip,e Test
!,ans.
91 General Test +lan Metrics
T'is pa"e s'o-s ou on, t'e most #urrent status of a Test !,an % test suite$ o-ner$
mi,estone$ priorit and ke-ord. /n addition t'ere are a,so %asi# metri#s for a,, ena%,ed %ui,ds.
T'e most @#urrent statusC is determined % t'e most re#ent 2ui,d Test Cases -ere e1e#uted
on. *or instan#e$ if a Test Case -as e1e#uted o0er mu,tip,e 2ui,ds$ on, t'e ,atest resu,t is
taken into a##ount. 8'ast Test Result= is a #on#ept used in man reports$ and is determined
as fo,,o-s :
1H T'e order in -'i#' 2ui,ds are added to a Test !,an determines -'i#' 2ui,d is most
re#ent. T'e resu,ts from t'e most re#ent 2ui,d -i,, take pre#eden#e o0er o,der 2ui,ds.
*or e1amp,e$ if ou mark a test as @fai,C in 2ui,d 1$ and mark it as @passC in 2ui,d 2$ it?s
,atest resu,t -i,, %e @passC.
2H /f a Test Case is e1e#uted mu,tip,e times on t'e same 2ui,d$ t'e most re#ent e1e#ution
-i,, take pre#eden#e. *or e1amp,e$ if 2ui,d ; is re,eased to our team and tester 1
marks it as @passC at 2!6$ and tester 2 marks it as @fai,C at ;!6 V it -i,, appear as
@fai,C.
;H Test Cases ,isted as @not runC a"ainst a 2ui,d are not taken into a##ount. *or e1amp,e$ if
ou mark a #ase as @passC in 2ui,d 1$ and don?t e1e#ute it in 2ui,d 2$ it?s ,ast resu,t -i,,
%e #onsidered as @passC.
T'e fo,,o-in" ta%,es are disp,aed :
- ;8 -
Results by top level Test -uites
Lists t'e resu,ts of ea#' top ,e0e, suite. Tota, #ases -it' status are ,isted: passed$
fai,ed$ %,o#ked$ not run$ and per#ent #omp,eted. 9 @#omp,etedC Test Case is one t'at 'as %een
marked pass$ fai,$ or %,o#k. >esu,ts for top ,e0e, suites in#,ude a,, #'i,dren suites.
Results by #uil/
Lists t'e e1e#ution resu,ts for e0er 2ui,d. *or ea#' 2ui,d$ t'e tota, Test Cases$ tota, pass$ W
pass$ tota, fai,$ W fai,$ %,o#ked$ W %,o#ked$ not run$ and Wnot run are disp,aed. /f a Test
Case 'as %een e1e#uted t-i#e on t'e same 2ui,d$ t'e most re#ent e1e#ution -i,, %e taken into
a##ount.
Results #y 2ey)or/
Lists a,, ke-ords t'at are assi"ned to #ases in t'e #urrent Test !,an$ and t'e resu,ts
asso#iated -it' t'em.
&%ample :
2ey)or/ Total +asse/ 1aile/ #loc(e/ <ot run Complete/ >?@
!; 1128 ;45 4= 44 580 ;9.=2
!2 484 ;=2 24 ;1 14= =;.15
!1 ;28 24= 5 41 14 94.=;
Results by o)ner
Lists ea#' o-ner t'at 'as Test Cases assi"ned to t'em in t'e #urrent Test !,an. Test
#ases -'i#' are not assi"ned are ta,,ied under t'e @unassi"nedC 'eadin".
&%ample:
Tester Total +asse/ 1aile/ #loc(e/ <ot run Complete/ >?@
+ominika 4=9 21= ;4 4= 281 41.4=
6o'ammad 245 82 9 2 14; ;=.80
unassi"ned ;4 19 0 1 14 4=.14
Ien 289 110 1 21 14= 44.5=
6a,,ik 4;0 259 4 18 1;8 5=.91
9,i 22= 12; 28 1; 5; =2.24
6ike 24 22 0 0 2 91.5=
9,e1 2=2 144 1 ;5 80 =0.49
9" Auery Metrics
T'is report #onsists of a Duer form pa"e$ and a Duer resu,ts pa"e -'i#' #ontains t'e Dueried
data.
Auery 1orm +age4
User is presented -it' a Duer pa"e -it' 4 #ontro,s. Fa#' #ontro, is set to a defau,t -'i#'
ma1imiJes t'e num%er of Test Cases and 2ui,ds t'e Duer s'ou,d %e performed a"ainst.
- ;9 -
9,terin" t'e #ontro,s a,,o-s t'e user to fi,ter t'e resu,ts and "enerate spe#ifi# reports for
spe#ifi# o-ner$ ke-ord$ suite$ and 2ui,d #om%inations.
ke-ord V 0-S1 ke-ords #an %e se,e#ted. 2 defau,t V no ke-ord is se,e#ted. /f a ke-ord
is not se,e#ted$ t'en a,, Test Cases -i,, %e #onsidered re"ard,ess of ke-ord assi"nments.
Ie-ords are assi"ned in t'e Test Spe#ifi#ation or Ie-ord 6ana"ement pa"es. Ie-ords
assi"ned to Test Cases span a,, Test !,ans$ and span a#ross a,, 0ersions of a Test Case. /f ou
are interested in t'e resu,ts for a spe#ifi# ke-ord ou -ou,d a,ter t'is #ontro,.
o-ner V 0-S1 o-ners #an %e se,e#ted. 2 defau,t V no o-ner is se,e#ted. /f an o-ner is not
se,e#ted$ t'en a,, Test Cases -i,, %e #onsidered re"ard,ess of o-ner assi"nment. Current,
t'ere is no fun#tiona,it to sear#' for @unassi"nedC Test Cases. :-ners'ip is assi"ned t'rou"'
t'e @9ssi"n Test Case e1e#utionC pa"e$ and is done on a per Test !,an %asis. /f ou are
interested in t'e -ork done % a spe#ifi# tester ou -ou,d a,ter t'is #ontro,.
top ,e0e, suite - 0-S n top ,e0e, suites #an %e se,e#ted. 2 defau,t V a,, suites are se,e#ted.
:n, suites t'at are se,e#ted -i,, %e Dueried for resu,t metri#s. /f ou are on, interested in t'e
resu,ts for a spe#ifi# suite ou -ou,d a,ter t'is #ontro,.
2ui,ds V 1-Sn 2ui,ds #an %e se,e#ted. 2 defau,t V a,, 2ui,ds are se,e#ted. :n, e1e#utions
performed on 2ui,ds ou se,e#t -i,, %e taken into a##ount -'en produ#in" metri#s. *or
e1amp,e V if ou -anted to see 'o- man Test Cases -ere e1e#uted on t'e ,ast ; 2ui,ds V ou
-ou,d a,ter t'is #ontro,.
Ie-ord$ o-ner$ and top ,e0e, suite se,e#tions -i,, di#tate t'e num%er of Test Cases from our
Test !,an t'at are used to #ompute per suite and per Test !,an metri#s. *or e1amp,e$ if ou
se,e#t o-nerX@(re"C$ Ie-ordXC!riorit 1C$ and a,, a0ai,a%,e test suites V on, !riorit 1 Test
Cases assi"ned to (re" -i,, %e #onsidered. T'e @Y of Test CasesC tota,s ou -i,, see on t'e
report -i,, %e inf,uen#ed % t'ese ; #ontro,s.
2ui,d se,e#tions -i,, inf,uen#e -'et'er a #ase is #onsidered @passC$ @fai,C$ @%,o#kedC$ or @not
runC. !,ease refer to 8'ast Test Result= ru,es as t'e appear a%o0e.
!ress t'e @su%mitC %utton to pro#eed -it' t'e Duer and disp,a t'e output pa"e.
- 40 -
Auery Report +age4
T'e report pa"e -i,, disp,a:
1. t'e Duer parameters used to #reate t'e report
2. tota,s for t'e entire Test !,an
;. a per suite %reakdo-n of tota,s Gsum & pass & fai, & %,o#ked & not runH and all e1e#utions
performed on t'at suite. /f a Test Case 'as %een e1e#uted more t'an on#e on mu,tip,e
2ui,ds V a,, e1e#utions -i,, %e disp,aed t'at -ere re#orded a"ainst t'e se,e#ted 2ui,ds.
7o-e0er$ t'e summar for t'at suite -i,, on, in#,ude t'e @Last Test >esu,tC for t'e
se,e#ted 2ui,ds.
- 41 -
Illustration #B: =uery metrics G Input parameters
9$ #loc(e/B 1aile/B an/ <ot Run Test Case Reports
T'ese reports s'o- a,, of t'e #urrent, %,o#ked$ fai,in"$ or not run Test Cases. 8'ast Test
Result= ,o"i# G-'i#' is des#ri%ed a%o0e under (enera, Test !,an 6etri#sH is a"ain emp,oed to
determine if a Test Case s'ou,d %e #onsidered %,o#ked$ fai,ed$ or not run. 2,o#ked and fai,ed
Test Case reports -i,, disp,a t'e asso#iated %u"s if t'e user is usin" an inte"rated %u"
tra#kin" sstem.
90 Test Report
Vie- status of e0er Test Case on e0er 2ui,d. /f a Test Case -as e1e#uted mu,tip,e times on
t'e same 2ui,d V t'e most re#ent e1e#ution resu,t -i,, %e used. /t is re#ommend to e1port t'is
report to F1#e, format for easier %ro-sin" if a ,ar"e data set is %ein" used.
96 Charts
T'is report pa"e reDuires "rap'i# ,i%rar insta,,ed on our -e% ser0er. @Last Test >esu,tC ,o"i#
is used for a,, 4 #'arts t'at ou -i,, see.
T'e four #'arts pro0ide are :
1. !ie #'art of o0era,, pass & fai, & %,o#ked & and not run Test Cases
2. 2ar #'art of >esu,ts % Ie-ord
;. 2ar #'art of >esu,ts 2 :-ner
4. 2ar #'art of >esu,ts 2 Top Le0e, Suite
T'e %ars in t'e %ar #'arts are #o,oured su#' t'at t'e user #an identif t'e appro1imate
- 42 -
Illustration #C: =uery metrics G results
num%er of pass$ fai,$ %,o#ked$ and not run #ases.
97 Total #ugs 1or %ach Test Case
T'is report s'o-s ea#' Test Case -it' a,, of t'e %u"s fi,ed a"ainst it for t'e entire proAe#t. T'is
report is on, a0ai,a%,e if a 2u" Tra#kin" Sstem is #onne#ted.
99 Re.uirements base/ report
T'is report is a0ai,a%,e if reDuirements are a,,o-ed for t'e #urrent Test !roAe#t. >eport is
"enerated a"ainst one >eDuirement Spe#ifi#ation do#ument #'osen from #om%o %o1 menu.
T'ere are t-o se#tions: metri#s and resu,ts o0er0ie-.
T'e fo,,o-in" metri#s are a0ai,a%,e:
Tota, num%er of reDuirements
>eDuirements -it'in TestLink
>eDuirements #o0ered % Test Cases
>eDuirements not #o0ered % Test Cases
>eDuirements not #o0ered or not tested
>eDuirements not tested
>eDuirements are di0ided into four se#tions. Fa#' reDuirement is ,isted to"et'er -it' a,, re,ated
Test Cases G#o,oured a##ordin" to Test Case resu,tH:
!assed >eDuirements
*ai,ed >eDuirements
2,o#ked >eDuirements
)ot-e1e#uted >eDuirements
9; Ho) to a// a ne) report
Cop one of t'e #urrent reports and modif it a##ordin" to our need. +on?t for"et t'at -e use
temp,ates for renderin" G<testlink_root>/gui/templates/<report_name>.tplH and ,o"i#
G<testlink_root>/lib/results/<report_name>.phpH. Ee re#ommend reusin" e1istin"
fun#tions to #o,,e#t data for report instead of #reatin" ne- ones.
Fdit <testlink_root>/lib/results/resultsNavigator.php to add a ,ink to our ne- report.
T'ere is an arra$ t'at #ou,d %e easi, en'an#ed. Qou must add a ne- U>L and @name
ke-ordC
=
of report.
Qou #an modif CSS st,e for a report. Ee su""est #reatin" ne- #,asses instead of modifin"
#urrent ones Gto a0oid un-anted #'an"es in ot'er pa"esH.

If you contribute your ne report)s+ via our tracker8 you can find it also in the ne%t
versions ... otherise you risk that it ill not ork for the ne%t main release.
= T'e strin" must %e defined in ,o#a,e&enB"%&strin".t1t
- 4; -
; A/ministration
;1 :ser account settings
F0er "uest #an #reate o-n a##ount on ,o"in pa"e.
The autoGcreate feature can be disabled by confi"uration. There is also confi"urable
default role parameter )4"uest4 by default+.
F0er user on t'e sstem -i,, %e a%,e to edit t'eir o-n information 0ia t'e 9##ount settin"s
-indo- G?Personal? ,ink in menu %arH. 7e #an modif o-n )ame$ emai, address$ pass-ord and
"enerate 9!/ ke Gif ena%,edH.
TestLink a,,o-s users -it' administrator ri"'ts to #reate$ edit$ and de,ete users -it'in t'e
sstem. 7o-e0er$ TestLink does not a,,o- administrators to 0ie- or edit user?s pass-ords. /f
users for"et t'eir pass-ords t'ere is ,ink on t'e ,o"in s#reen$ t'at -i,, mai, t'e user t'eir
pass-ord %ased upon t'eir user name and t'e emai, address t'e entered.
;" Role +ermissions
User #an see t'e #urrent ro,e in top ,ine of TestLink -indo-. Fa#' users 'as ?"eneri# ro,e? t'at
app,ies on a,, proAe#ts. 9dministrator #an assi"n spe#ifi# proAe#t ro,e for a parti#u,ar proAe#t.
Users #an 'a0e modified ro,e for parti#u,ar Test !,an as -e,,.
$or e%ample Mack could be "uest by default )can see all test cases and reports+ and Test
leader on project 4N2O4 to lead this project testin".
TestLink is %ui,t -it' 5 different defau,t permission ,e0e,s %ui,t in. T'ese permission ,e0e,s are
as fo,,o-s:
Guest: 9 "uest on, 'as permission to 0ie- Test Cases$ reports and metri#s. 7e #annot
modif ant'in".
Test %&ecutor: 9 tester 'as permissions to see and run tests a,,o#ated to t'em.
Test Designer: 9 user #an fu,, -ork G0ie- and modifH -it' Test Spe#ifi#ation and
>eDuirements.
Test Analyst: 9 tester #an 0ie-$ #reate$ edit$ and de,ete Test Cases as -e,, as e1e#ute
t'em. Testers ,a#k t'e permissions to mana"e Test !,ans$ mana"e Test !roAe#ts$ #reate
mi,estones$ or assi"n ri"'ts. Ginitia,, Senior testerH.
Test 'ea/er: 9 ,ead 'as a,, of t'e same permissions as a Tester %ut a,so "ains t'e
a%i,it to mana"e Test !,ans$ assi"n ri"'ts$ #reate mi,estones$ and mana"e ke-ords.
A/ministrator: 9n admin 'as a,, possi%,e permissions G,eader p,us t'e a%i,it to
mana"e Test !roAe#ts and usersH.
C'an"in" of t'ese ri"'ts is 'and,ed % t'e user administration ,ink -'i#' is a##essi%,e %
administrators. 9dmin #an add a ne- #ustom ro,es and modif e1istin" ones 0ia (U/.
See <eveloper4s Luide to understand more.
/f ou 0ie- t'e ta%,e ou -i,, see ro-s for ea#' of t'e permissions ,e0e,s G"uest $tester$ senior
tester$ ,eader$ adminH. T'e se#ond #o,umn 'o,ds a,, of t'e different ri"'ts ,e0e,s -'i#' -i,, %e
defined %e,o-. T'ese ,e0e,s 'a0e %een determined as standard for use %ut t'e #an %e edited
to define ne- ro,es Gfor e1perien#ed administratorH. T'e user ta%,e #ontains a forei"n ke t'at
points to t'e appropriate permission ,e0e, in t'e ri"'ts ta%,e.
- 44 -
/ote: Test Plan related features needs also assi"n a Test Plan to be available. See Test
Plan 3ssi"nment.
Case stu/y C restrict access by /efault
-ituation
/n our or"aniJation -e -ou,d ,ike to restri#t a##ess to proAe#ts un,ess it is spe#ifi#a,, "ranted.
Ee #urrent, 'a0e a%out 140 users -it' Aust o0er 90 different proAe#t. 6an of t'e users are
not K9$ %ut are %usiness ana,sts$ and in some #ases end users doin" U9T. *rom -'at / #an
te,,$ a,, ri"'ts are in'erited %ased on 'o- t'e user -as set-up.
2ut -e don?t -ant a 2usiness 9na,st -'o is -orkin" on on, one proAe#t 'a0e a##ess to a,, 90.
-olution
Set t'ese users -it' t'e ",o%a, ro,e P/o ri"htsQ and "ranted an appropriate ro,e on a Test
proAe#t or Test p,an %ase. /n #ustomB#onfi".in#.p'p ou #an a,so set t'e defau,t ro,e id to T)o
ri"'tsS:
$tlCfg->default_roleid = T_!"#S_N"_!$%&TS'
2ou can also ould like to rename a role J/o ri"htsK to somethin" more polite.
;$ Test +lan assignment to users
Users #an e1e#ute on, assi"ned Test !,ans. /n order to "ain Test !,an permissions a user -it'
,ead or admin status must "i0e t'em ri"'ts t'rou"' t'e @+efine user&proAe#t ri"'tsC ,ink under
@Test !,an 6ana"ementC.
9,, users in t'e sstem -i,, % defau,t not 'a0e permissions to 0ie- ne-, #reated Test !,ans
Ge1#ept for t'e Test !,an #reators -'o #an "i0e t'emse,0es permissions at #reationH. Pero Test
!,an permissions means t'at users -i,, not see an Test !,ans in t'e Test !,an drop-do-n %o1
on main s#reen.
Hoever he can brose reports.
;0 Custom 1iel/s
Users #an e1tend t'e most important o%Ae#ts GTest #ases$ suites$ p,ansH in TestLink -it'
#ustomiJed fie,ds. 9fter ou 'a0e #reated a Custom *ie,d$ ou need to assi"n it to t'e Test
!roAe#t in -'i#' do ou -ant to use it. So ea#' proAe#t 'a0e o-n set of additiona, fie,ds.
7ommon practice: Test case 7$ could be: revie notes or status8 estimated or real
e%ecution time8 platform )0S8 H*8 ...+8 test script name or oner8 etc.
)a0i"ate to J7ustom field mana"ementK ,ink on main pa"e. T'is pa"e is t'e %ase point for
mana"in" #ustom fie,ds poo,. /t ,ists t'e #ustom fie,ds defined in t'e sstem. Custom fie,d
definitions are sstem -ide$ i.e.$ ou #an not define t-o #ustom fie,ds -it' same fie,d /+.
T'e @7reate@ %utton take ou to a pa"e -'ere ou #an define t'e detai,s of a #ustom fie,d.
T'ese in#,ude it?s name$ tpe$ 0a,ue and a0ai,a%i,it&disp,a information. :n t'e edit pa"e$ t'e
fo,,o-in" information is defined to #ontro, t'e #ustom fie,d:
name
type - possi%,e 0a,ues are ,isted %e,o-.
Dalue constraints G!ossi%,e 0a,ues$ defau,t 0a,ue$ re"u,ar e1pression$ minimum ,en"t'$
ma1imum ,en"t'H.
AvailabilityEDisplay control G-'ere t'e fie,d -i,, s'o- up and must %e fi,,ed in
- 44 -
9,, fie,ds are #ompared in ,en"t' to %e "reater t'an or eDua, to t'e minimum ,en"t'$ and ,ess
t'an or eDua, to t'e ma1imum ,en"t'$ un,ess t'ese 0a,ues are 0. /f t'e 0a,ues are 0$ t'e #'e#k
is skipped. 9,, fie,ds are a,so #ompared a"ainst t'e re"u,ar e1pression. /f t'e 0a,ue mat#'es
t'e e1pression$ t'en t'e 0a,ue is stored. *or e1amp,e$ t'e e1pression 3&Z-[GN0-9OHU\&3 #an %e
used to #onstrain an inte"er.
T'ere is data format 0erifi#ation for tpes numeri#$ f,oat and emai,. :n su%mit G-'en #reated a
Test #ase or -'i,e e1e#utin"H C* of t'is tpe are #ontro,,ed. Fmpt 0a,ue :I$ %ut if 0a,ue )oT
empt %ut do not #onform a re"u,ar e1pression G):T USF> +F*/)F+ %ut #oded H su%mit -i,,
%e %,o#ked -it' messa"e on s#reen.
T'e ta%,e %e,o- des#ri%es t'e fie,d tpes and t'e 0a,ue #onstraints.
Type 1iel/ Contents Dalue Constraints
Strin" te1t strin" up to 244
#'ara#ters
)umeri# an inte"er
*,oat a f,oatin" point
num%er
Fmai, an emai, address
strin" up to 244
#'ara#ters
E'en disp,aed$ t'e 0a,ue -i,, a,so %e en#apsu,ated in a mai,to: referen#e.
C'e#k%o1 Jero or more of a ,ist
of te1t strin"s
Fnter t'e ,ist of te1t strin"s separated % 3]3 Gpipe #'ara#terH in t'e !ossi%,e
Va,ues fie,d. T'e +efau,t 0a,ue s'ou,d mat#' one of t'ese strin"s as -e,,.
T'is -i,, %e disp,aed as a ,ist of te1t strin"s -it' a #'e#k%o1 %eside t'em.
List one of a ,ist of te1t
strin"s
Fnter t'e ,ist of te1t strin"s separated % 3]3 Gpipe #'ara#terH in t'e !ossi%,e
Va,ues fie,d. T'e +efau,t 0a,ue s'ou,d mat#' one of t'ese strin"s as -e,,.
T'is -i,, %e disp,aed as a mu,ti-,ine dropdo-n menu.
6u,tise,e#tion List Jero or more of a ,ist
of te1t strin"s
Fnter t'e ,ist of te1t strin"s separated % 3]3 Gpipe #'ara#terH in t'e !ossi%,e
Va,ues fie,d. T'e +efau,t 0a,ue s'ou,d mat#' one of t'ese strin"s as -e,,.
T'is -i,, %e disp,aed as a mu,ti-,ine dropdo-n menu.
+ate te1t strin" definin" a
date
T'is is disp,aed as a set of dropdo-n menus for da$ mont'$ and ear.
+efau,ts s'ou,d %e defined in -mm-dd format.
Te1t 9rea >i#' te1t
Table 1: 7ustom field types
T'e disp,a entries are used as fo,,o-s:
%ntry Meaning
+isp,a on
test spe#ifi#ation
/f #'e#ked$ t'e fie,d -i,, %e s'o-n on Test Spe#ifi#ation tree
Fna%,e on
test spe#ifi#ation
/f #'e#ked$ t'e fie,d -i,, %e edita%,e Gassi"n&#'an"eH on Test Spe#ifi#ation
+isp,a on
test e1e#ution
/f #'e#ked$ t'e fie,d -i,, %e s'o-n on Test F1e#ution
Fna%,e on
test e1e#ution
/f #'e#ked$ t'e fie,d -i,, %e edita%,e on Test F1e#ution
90ai,a%,e for Test #ase$ Test p,an or Test suite
Table #: 7ustom fields: 3vailability9<isplay 3ttributes
Example %&
7ustom $ield : 3dditional /otes
- 45 -
Type : strin"
applicable to test suites8 to be edited 0/L2 durin"
Test 7ase specification8 but useful to be seen durin" test e%ecution.
sho on desi"n R 2&S
enable on desi"n R 2&S
sho on e%ecution R 2&S
enable on e%ecution R /0
Example '&
7ustom $ield : 0peratin" System
Type : list
applicable to Test 7ases8 to be edited 0/L2 durin"
Test 7ase &N&7?TI0/8 unused durin" Test 7ase <&SIL/.
sho on desi"n R /0
enable on desi"n R /0
sho on e%ecution R 2&S
enable on e%ecution R /0
7ustom field feature has been implemented usin" a mi% functionality from -antis
)http:99.mantisbt.or"9+ and dotproject )http:99.dotproject.net9+ models.
Custom fiel/s4 %stimate/ an/ Actual e&ecution time
@Fstimated F1e#ution TimeC and @9#tua, F1e#ution TimeC #ustom fie,ds #an %e added to an
proAe#t and TestLink -i,, automati#a,, summariJe t'ose fie,ds durin" t'e reportin" pro#ess.
Step 1 V Create t'e #ustom fie,ds
/0T&: The user must have permissions )i.e. J7ustom $ield -ana"ementK must be
enabled for the user4s role+ to define and assi"n custom fields.
*irst se,e#t @+efine #ustom fie,dsC from t'e Test
+ro,ect "roup as seen %e,o-.
)e1t se,e#t t'e @CreateC %utton.
/t is most important t'at t'e <ame fie,d is e1a#t,
C*BFST/69TF+BF<FCBT/6F due to t'e %ui,t in
Dueries desi"ned to t'is fie,d. T'e Type fie,d must
%e eit'er <umeric$ -tring or 1loat$ as t'e %ui,t Dueries -i,, on, -ork on numeri#a, data. /t is
su""ested t'at 1loat tpe as it a,,o-s more f,e1i%i,it.
- 4= -
:n#e #omp,eted$ #,i#k @9ddC to #reate t'e ne- #ustom fie,d to t'e sstem.
)e1t repeat t'e pro#ess for C*BF<FCBT/6F as seen %e,o-.
- 48 -
T'e ne- #ustom fie,ds -i,, %e a0ai,a%,e for assi"nment to 9)Q proAe#t in TestLink. 6ake sure
t'e Test !roAe#t is set to t'e proAe#t t'at ou -ant %efore assi"nin" t'e #ustom fie,ds.
Step 2 V 9ssi"n #ustom fie,ds
Se,e#t @9ssi"n #ustom fie,dsC from t'e Test
+ro,ect "roup as seen %e,o-.
Se,e#t ea#' of t'e #ustom fie,ds and #,i#k
@9ssi"nC.
)o- ea#' of t'e #ustom fie,ds 'a0e %een
assi"ned to t'e current proAe#t.
E'en ou #reate a ne- test #ase Gor edit a pre0ious entered test #aseH$ a%o0e t'e Ie-ords
se#tion ou -i,, noti#e t'e #ustom fie,ds.
- 49 -
9dd t'e estimated time and #,i#k @CreateC Gor @Sa0eC on an editH.
Locali.ations: ?se J . J )dot+ as decimal separator or sum ill be ron".
Step ; V 9dd t'e test #ases to t'e Test !,an
See #'apter 4.; for detai,s.
Step 4 V Summation of t'e Fstimations
Se,e#t @Test reports and 6etri#sC from t'e Test
%&ecution "roup as seen %e,o-.
Se,e#t
@Test
>eportC
from t'e
menu$ t'en
#'e#k t'e @6etri#sC option
*ina,, se,e#t t'e Test Suite or Test Case t'at ou -is' to
#reate t'e report.
9t t'e %ottom of t'e report -i,, %e a summar of t'e
estimated e1e#ution time for a,, of t'e test #ases.
- 40 -
/0T&: The time entered into the custom fields doesn4t have to be in units of minutes8
hours can also be used. The STLSEestimatedEtimeEhours and STLSEestimatedEtimeEmin
strin"s are predefined strin"s can be selected based on your preference.
- 41 -
F Import an/ %&port /ata
TestLink supports se0era, -as to s'are data. +ata *ormat is des#ri%ed in e1tra do#ument
Ttestlin(>/docs/tl-file-format.pdf. /n addition ou #an #onsider to use TestLink 9!/ to
de,i0er data from s#ript or e1terna, too,.
T'ere is amount of fi,e e1amp,es in dire#tor Ttestlin(>/docs/file_e)amples/.
- 42 -

You might also like