Test Management by Vladimir Arutin

The Secret
Ingredient
Of Test
Management

ABOUT MYSELF
VLADIMIR ARUTIN
QA ENGINEER
at HYS ENTERPRISE
ISTQB CERTIFIED TEST MANAGER
ISTQB Training Instructor
Quality Assurance Training Instructor
Speaker

TEST MANAGEMENT – planning, scheduling,
estimating, monitoring, reporting, control and
completion of test activities.
*Ref: ISO 29119
WHAT IS TEST MANAGEMENT?

WHY DO WE NEED TEST MANAGEMENT?
“Тестирование - это искусство
сравнивания невидимого с
противоречивым, чтобы
предотвратить немыслимое,
случившееся с неизвестным.”

TEST MANAGER’S RESPONSIBILITIES
• BULDING UP AND LEADING THE TESTING TEAM
• DEFINING THE SCOPE OF TESTING
• DEPLOYING AND MANAGING RECOURCES FOR TESTING
• APPLYING THE APPROPRIATE TEST MEASUREMENTS AND METRICS
• PLANNING, DEPLOYING AND MANGING
• ASSESSING THE PROGRESS AND EFFECTIVENESS OF THE TEST EFFORT
• ADVOCATING THE APPROPRIATE LEVEL OF TESTABILITY
• ADVOCATING THE APPROPRIATE LEVEL OF QUALITY

WHAT ARE THE CHALLENGES IN TEST MANAGEMENT?
 NOT ENOUGH TIME TO TEST
 NOT ENOUGH RECOURCES TO TEST
 THE PROJECT BUDGET IS LOW
AND SCHEDULE IS TOO TIGHT
 TESTING TEAMS ARE NOT ALWAYS IN ONE PLACE
 THE REQUIREMENTS ARE TOO COMPLEX
TO CHECK AND VALIDATE

MAIN PROBLEM
HEY YOU!
TEST THIS APPLICATION
TO ENSURE HIGH
QUALITY!
OKAY, BUT I NEED
PEOPLE, BUDGET,
TIME… LET ME
CREATE A TEST PLAN
FOR HIGH QUALITY
TESTING.
BOSS
TM

LOOK! HERE IS MY TEST PLAN.
AT FIRST SIGHT IT COSTS
A LOT, BUT ALL THESE ACTIVITIES
ARE NECESSARY FOR GOOD
TESTING.
WHAT?!! COST IS TOO
HIGH! CUT YOUR
BUDGET IN 4 TIMES!!!
AND FINISH THE PROGECT
IN HALF TIME!!!

YOU HAVE 1 DAY TO PRESENT COMPLETE
TEST PLAN BASED ON THE APPROVED
BUDGET!
IF YOU CAN’T TO IT, WE’LL FIND ANOTHER
TEST MANGEMENT WHO CAN!

ALWAYS COMPARE
YOUR COSTS AND
BENEFITS

1. Decide What to Automate
2. Prioritize & Divide Tasks
3. Prepare Test Cases & Scenario Beforehand
4. Create Tests that Don’t Affect UI Changes
5. Don’t Automate Every Test
6. Review Tests Periodically
7. Compare Your Costs And Benefits
CALCULATE YOUR COSTS

EVERYTHING SHOULD BE MADE AS SIMPLE
AS POSSIBLE, BUT NO SIMPLER

7 Principles of TESTING
1. Exhaustive testing is not possible
2. Defect Clustering
3. Pesticide Paradox
4. Testing shows a presence of defects
5. Absence of Error - fallacy
6. Early Testing
7. Testing is context dependent
10 Principles for Agile
Testers
1. Provide Continuous Feedback
2. Deliver Value to the Customer
3. Enable Face-to-Face Communication
4. Have Courage
5. Keep It Simple
6. Practice Continuous Improvement
7. Respond to Change
8. Self-Organize
9. Focus on People
10. Enjoy
USE TEST MANAGEMENT PRINCIPLES

Test Tracking and Efficiency
USE TEST METRICS. MEASURE AND RULE!

Test Effort
How long, how many,
and how much?

Test Effectiveness
Defect Detection Percentage =
(DDP)
Defects found by testing stage
Total defects found in all stages

Test Coverage

Defect Density = No. of Defects identified / size
No. of Defects identified 30
No. of requirements 5
Others
Defect Density = (30 / 5) = 6
Defect Removal Efficiency (DRE)
No. of Defects found while Testing + No. of Defects found by User
DRE= х100%
120
No. of Defects found by User 42
No. of Defects found while Testing
DRE = [120 / (120 + 42)] * 100 = [120 /162] * 100 = 74.07%

Others
х100%
120
No. of Defects found by User 42
Example, QA team reported 100 defects out
of which 20 were invalid(not bugs, duplicates,
etc.) and only 65 were fixed
Defect gap % is: (65/100-20)X100= 81%
Defect Gap =
Total No. of Valid Defects reported)
Total No. of Defects Fixed

Others
 
 
 
Total RawTest Steps
TestCaseProductivity = Step(s)/hour
Efforts(hours)
Test Case Name Raw Steps
XYZ_1 30
XYZ_2 32
XYZ_3 40
XYZ_4 36
XYZ_5 45
Total Raw Steps 183
Efforts took for writing 183 steps
is 8 hours.
TCP=183/8=22.8
Test case productivity = 23 steps/hour

Test Automation Metrics
AP (%) =
Automation Progress
# of actual test cases automated
# of test cases automatable
Test Progress
TP (%) =
# of test cases (attempted or completed)
time (days/weeks/months, etc)
Percent of Automated Testing Test Coverage
PTC( (%) =
automation coverage )
total coverage

SCRIPTS FOR SUCCESS
 BEGIN THE TESTING ACTIVITIES EARLY IN THE SDLC
 REUSE TEST ASSETS AND IMPROVE TIME SPENT EVERY TIME
 ENSURE PROPER COORDINATION BETWEEN CO-LOCATED TESTING
RECOURCES
 DEFINE & ENFORCE FLEXIBLE TESTING PROCESSES
 COORDINATE & INTERGRATE WITH DEV TEAMS –
USE DEVOPS SHIFT LEFT PRACTICE
 COMMUNICATE THE CORRECT STATUS AT THE RIGHT TIME
 TO SAVE TIME, AUTOMATE, AUTOMATE, AUTOMATE!

SCRIPTS FOR SUCCESS
 PLAN, DO, CONTROL AND STANDARDIZE!
 RECOGNIZE PROBLEMS.
IT’S COOL BECAUSE NOW YOU CAN FIX THEM.
 DOCUMENT ALL SOLUTIONS AND RESULTS
 EACH DAY –NEW SMALL IMPROVEMENTS
 INVOLVE ALL STAFF WHILE MAKING DECISIONS
 IF YOU DO SOMETHING BE SURE IT WILL STAY THAT WAY
YOU DID IT. SO DO IT PROPERLY AT ONCE.
 ALL THE WORK ON THE PROJECT SHOULD BE CONSIDERED
THROUGH THE LENS OF COMPANY DISTANT TARGETS FOR
FUTURE GROWTH.

TEST PROCESS IMPROVEMENT (TPI) NEXT
TPI NEXT: A continuous business-driven framework for test process improvement
that describes the key elements of an effective and efficient test process.
16 KEY PROCESS AREAS:
1. Stakeholder commitment
2. Degree of involvement
3. Test Strategy
4. Test Organization
5. Communication
6. Reporting
7. Test Process Management
8. Estimating and Planning
9. Metrics
10. Defect Management
11. Testware Management
12. Methodology Practice
13. Tester Professionalism
14. Test Case Design
15. Test Tools
16. Test Environment

TEST PROCESS IMPROVEMENT (TPI) NEXT

CRITICAL TESTING PROCESS (CTP)
CRITICAL TESTING PROCESSE (CTP): A content-based model for test process
improvement built around twelve critical processes.
12 CRITICAL PROCESSES:
1. TESTING
2. ESTABLISHING CONTEXT
3. QUALITY RISK ANALYSIS
4. TEST ESTIMATION
5. TEST PLANNING
6. TEST TEAM DEVELOPMENT
7. TEST SYSTEM DEVELOPMENT
8. TEST RELEASE MANAGEMENT
9. TEST EXECUTION
10. BUG REPORTING
11. RESULTS REPORTING
12. CHANGE MANAGEMENT

SYSTEMATIC TEST AND EVALUATION PROCESS
(STEP)
SYSTEM TEST AND EVALUATING PROCESS (STEP): A structured testing methodology,
also used as a content-based model for improving the testing process which doesn’t
require that improvements occur in a specific order.
Basic premises of the methodology include:
• A requirement-based strategy
• Testing starts at the beginning of the lifecycle
• Tests are used as requirements and usage models
• Testware design leads software design
• Defects are detected earlier or prevented
altogether
• Defects are systematically analyzed
• Testers and developers work together

TESTING MATURITY MODEL integration
(TMMi)
TESTING MATURITY MODEL intergation (TMMi) is composed of 5 maturity levels
and is intended to complement CMMI. Each of the maturity level contains defined
process areas that must be 85% complete by achieving specific and generic goals
before the organization can advance to the next level.

TESTING MATURITY MODEL integration
(TMMi)

1.
2.
! "
3. $
4. & ! '
!( ! !)
5. +
6. - (
. -

+ +
/
0$ &
+ + :
70% 5! 6. 7 ! ! ) !)
20% - ( ' 6 - -
9) ! -9 " 10% : 6 ! "
6 !- ' - - ; ! ".

$ ( 7. ; ( Priority
Severity E!?

(
! ! -
+ ! -
- -
- ( 7 ; !- ?

NO RISK - NO TEST
‘GOOD
ENOUGH’
! ! - !) - ; !
! - ! " 6 U , ( 7 !
! ! ' .W !- - ", !
! ! - ; .

+ +
- X+ ! ! - !)
- (! ! ! - !) YZ
- ) +G + Y ! ! - !)
- [ Z +Y ! ! -

$ + +
$ + +- ]
[ 0^ $ + + +

[ 0^
[ 0^
X ! ! - " "
U!)
"

+ $ X + $ 0 +
_ ^ +
НЕ ПРОВЕРНО
РИСКИ
УСТРАНЕНЫ
РИСКИ
ОСТАЮТСЯ
НЕОПРЕДЕЛЕННОСТЬ
ОЖИДАЕМЫЕ
ХАРАКТЕРИСТИКИ
РЕАЛЬНЫЕ
ХАРАКТЕРИСТИКИ

НЕ
ПРОВЕРЕНО
$ + + $ & [ `+
0& YZ +Y $ 0 +
* +Y & ,
& YZ !
& & Y
^0 0+ 0 +
* + Z ^0 0+
$ & & & 0
* ^ +Y
$ +
^0 + + X &

[ +Y :
 - b ( , - 6
 - ! : '
 7 "
 ; ! )
 9
 $ : " 77. "
 ( ; 7 ! .6 -, b !
 b (
 .!
 ^ ;E6U ! !
 -. 7 ! ; - "
 + !- 7 ( ( ; - b ( , ; 7 6 )
 ! ; ' -
 6 - ;
 U - W
 ; ! !
 ; ! .7 !
 ; E !-! ! ( ; !( ; ( ! .E! ! ) -
b )
 + ; - " - b 7 - "
 $.; ( - W , ; ' - ! : ;.6 ! - 6 . - 7
 $ . " 7 ! ( ! ;.6.! E !) " ; )9 - ' )
 $ - 9 ; , ! ! - , ! ! '6 7 ' b !)
 ! ( " b. ) !)

_
RE=P*C
P=probability (likelihood) of occurrence
for each risk,
C=cost of project when risk occurs

_ + +
+ +Y =M/N
M- ( !- ! -, - ! : -
N- ;W ( !- ! -

X + ] -
Z ]
$ & :
+Y ^ ^ + ] & 6 +.
[ +Y & & , + ^G /
+ & +Y ^0 + $250 K.
+Z y +Y [ ^ YZ [ & , +
^0 + + +Y $100K.
$ ^ & + &, X+ +Y + +Y 20%, X+ &
+ $ , + [ [ + & +Y + + $10K.
X+ +Y?

'6
XF – 6- U !) . ( risk exposure )
b. ) ! F ;
PuseFi – - "! !) ) - " b. ) ! F;
PazFj – - "! !) b b. ) ! F ;
Cj – / 6 !- " b b. ) ! F(
6 9 );
XF=PuseFi * PazFj * Cj
y &0 $ + &
(RISK EXPOSURE)

Risk Reduction Leverage
RRL=
RE before -RE after
REDUCTION COSTS

$ &
"! !) ! 6 : - 20%.
! 7 !) ! ! -"
7 ! 7 !)E - ! - "
6 : ! - " ! $20,000:
20% x $20,000 = $4,000

$ &
& U - 6 !) 7 : 7 ;
.7 )9 !) 5%.
" ;.6 ! U 7, ! - .( ; "
- 7 ! U ! " 7, ! 7 !) ; !
; . ! - ! 2000$
"! !) 0.05 ( 6 "! : 7 )
$ ! $20,000 (! U )
0.05 x $20,000 = $1000
Cost of Risk Reduction $2000
Leverage ($4000 - $1000) / $2000 = 1.5
RRL >1

& + _ + + ] $ + ]
"!!)!."
.W !- !) 6 !-
- 6

^ + & .
+Y + ?
• 0 + (risk avoidance)
• $ X (risk transference)
• (risk mitigation)
• $ + (risk acceptance)

+ –
” 0 Y^ y + ”
ПОКА ДЕФЕКТ НЕ ИСПРАВЛЕН, РИСК В ПРОДУКТЕ
ОСТАЕТСЯ
‘RISK ELIMINATION’: РИСК УСТРАНЯЕТСЯ В
РЕЗУЛЬТАТЕ СПРАВЛЕНИЯ И ВЕРИФИКАЦИИ
ДЕФЕКТА
‘RISK ACCEPTION’: РИСК ПРИНИМАЕТСЯ, КОГДА
ОБНАРУЖЕННЫЙ ДЕФЕКТ РЕШЕНО НЕ ИСПРАВЛЯТЬ
‘RISK SHARING’: КОГДА НЕ ИСПРАВЛЯЕТСЯ
СЕРЬЕЗНЫЙ ДЕФЕКТ, ЕГО ОБІЧНО ДЕЛЯТ:
- С МЕНЕДЖЕРОМ ПРОЕКТА (проектное совещание)
- С ЗАКАЗЧИКОМ (в ходе сдачи-приемки)
- С ПОЛЬЗОВАТЕЛЕМ (описание дефекта в
сопроводительной документации)
‘RISK AVOIDANCE’: ИНОГДА МЫ ПРОЬУЕМ ИЗБЕЖАТЬ
РИСКА
-переписать фрагмент кода с дефектами
- Урезать код (даже путем сокращения функционала)

+ + [ &
SYSTEMATIC SOFTWARE TESTING
PRODUCT RISK ANALYSIS
PRISMA
PRODUCT RISK MATRIX
FMEA
FTP
HAZARD ANALYSIS
COST OF EXPLOSURE

$ $ [ $
X $ + ] [
($ _ ), $ + X + $ + RPN
(RISK PRIORITY NUMBER)
RPN=S * P * L

 RPN 1-10, + $ & $ + +
& & $ + & [ + &
$ & , +.X. & + +
 RPN 11-30, + $ & ^
+ + ] y X
 RPN 31-70, + $ & $ / +
+ + y X
 RPN Z 70, + $ & $ X
^ [ &

$
♦ .U ! - – 5! : 9 .
♦ ! .! !- ! .( 6 - – 5! ; )9 E .
♦ 7 !) .U .7 : E6 , U ! ) 6-.7"
- 9 7 ; - "7 .
♦ X 7 .(9 6 ! ! ! " ! .6 7, ! 7
.(9 ; ! E!.
♦ 7 " 6 !- " 7 ! - " – 6 )' .
♦ ! .6 7 6 ! !) - .E !., (! ;
.9 . ! 7.

^ &
$ +Y Y 0X + 0 ?
А (ΔТ) = N × К × ΔТ,
'6 N — ( !- , ( .;
— - b " ;
Δ+ — - 7" - 6 ; !
( ! - ! " .77 + - 6 ! )
- 6 ! ) + + ! , ( , 7 .;
(Δ+) — ; ! , ! " 6 U ; !)
- - 7" Δ+, -- ( - -
( -.
! E6 :
N = А (ΔТ)/(К × ΔТ)
•KSLOC (кол-во строк кода)
•WTF/h (кол-во фич в час)
•Количество багов
•Focus Factor(вовлеченность)
•Velocity (скорость команды)
•Cycle time (время выполнения 1
цикла/единицы работы)
• прочие KPI

$ + ^ ^ + $ +
+
«^ ! - " ( ' ! !.
$ U ! 7 6»
(+ - )6 . , 6 ! ) Linux).
« ' - , (! ; "
! ;" .- 6 …»
( !).
6 7 HR ! !"! 1,5
7 .! 1 E7 !
6.7 ! , (! . -
7 ' ; )9 - 7 .

^ . + +^ .
 + : ( b!
(57 ) ! !)
 ; - ;
 ! 6 ! !.
 6 6 6 !
(6 )' , ) , !. - !) ", b. - ! )
 ! .(9 - : 9 ! E7
 $ 6. ! - !) . 9 !
 6 6 ! ' - ! “ E”
.(9 , ! - !, ( 7 9 6), ; - EW " 6 .

& ^ +Y + + &
Test Manager – многозадачный руководитель:
 X ! 6 - ! 7 ! ; ! !
 0( ! - : ! -
 •bb ! - -
 ( !- ! )
 6 -6 : - ! ) 7 6

+ Y + Z +&
1. ^ !) ! ; ) 7
2. & 7 ) W W !) ! -
3. $ 6 - !)
4. ^ !) 7 7 ) 7 ! ! 7
5. !) ! -
6. !) U6 7 -
7. $ : 6 !) )9 , .: 6 !) U

• - b ) 6
• E;"! .( !) "
• ) !
• ‘ ’ - ' 6
• U U6.! ; )9 ' ;• 7 !- ! !- !
• ! ; ( ) -
• ! . - "!)
• ! ) ( !
• 66 E! " - " E 6 .' : ' .
• . - 6 ! ) ! ' . 6 7 !.
[ 0$$
0X ^ - Y +
(5 ! ! ! )

 7 " 7 ' ( " ' .
 ! .6 ! - ) - - 7 b. - !
 - . : !) 6 .' - ; ( !
 ! E! ", 6 E! ) 6 , ;
 . - 6 ! ) ! ' . -! !, ;W ! "
! 7 6 7, - 6 7 !) ; ! , 7 ' - W .
0 Y+0 - + Y
[ 0$$

 . )! ! ! ) ( ! 6 " ! " - ;W :
! ; !": - '
 ! ) . - " . - 6 ! "- ' ; ) -
. ! ! ) .
 b ) 6
 - 6 - ) !- ! - ( ) !-
 ! : - ; !
[ Y - 0 Y [ 0$$

$ + _ ]
X ! ; 7 -
E6":,
- ! - 6 ( .

^ + 0 & . ^ + Y.
1. $ ( W ;W ! ) ; .U6 ! ! .6 7 ; (
7 7 ! , !) ; 7 - " !
7 ( - !), . - ! - 7.
2. ! ! ) ; !) 7 ! ! 7 ! .6 7 ,
; ' ! ; ! !- . ; . - 6 ! )- b ".
3. ; - ! , (! . - ! U !) ( ) .
'6 ; W ! 6.

y0 _ +
$ 6- ! ) + .W E( ! )
! .6 ! - !) ;
! ",
( ' 6 !) ;.6 !.

y + –•+ & Y
1. 7 9 ! 6 - 7 7
2. "- ! ' - : ' -
3. ; W ! ) ( ! ,
' - ! 6 !- ":
4. 6 ! 9 -7 !
5. ;•" ! 7.W !-
7 "
6. 7 U ! 9 !) —
. '. . !

 $ - ) 6; 6 -
 •" ! ; - ; ! , ! -
! .6 , ;" ! , !- ! !- ! 6 -
7 ( .
 ! 7 ! 7. - " — 7 ; 7 U !
( ! )
!) - ! " b ! : !. .
 ;W — 7 ' E! ;• 6 "!) E6 .
 ! - " . )!. — ;W - b 7 )
; ! - ; !-. ! ; U E ! .6 -,
: U6 E ;W : ! : ! 7.
& & _ $ X y +

0 Y + 0
3 ' - : - :
• !- ! ) 5! '
! ;: 6 7 .- !)?
• ^ 7. 6 ! -
- 7 U !) 6 !), (!
7 U ! ; ! !) .(9 ?
• - " ! " ( .- ) "
;• ! - .6 - !- ! ) "
; ! ! .6 , 5!
( , - !) 6 ! (
" ?
$ 6' ! -
- - 7 !)
7 6
« ! !. »
' " 7 9 - '6 :. ! - 7 ! ).
«$ -: 9 7.»

0 Y $ -$ / &0
• ;•" ! , ( 7 ( - ! U ! .6
! !) " « -: 9 7.», ; W !
• ; ! - 7 — - )! U6 9 ' 67 !
- " ( ! !, 6 U ! ! . , JIRA,
!.6.)
U 6 . ! !) ! " b ! 7 !)
6 !. ! .6 - U b 7
• - 6 !. ! .6
•$ 6 ( 6 6 .' 7. ! .6 .
• ; 6: 6"W ' - 7
•$ b ! ( " ; 6 ! -9 7 " ! .6 7 .
7 7 : E6 !;)
! 6 U !), .; 6 U !-. -
! 7, (! ! / 0 [

& + _ $
$ ( 6 7 ! - :
• ;7 .! U 6 " ! .6 7 ! - :;
• ' - 6 ! - ! .6 ;
• ! .! !- " 6 ! U . )! ! - !
. - 6 !- ;
• - ! ; - E( - - ! .6 , !
7 !;
• ! ( ' b ) ' ! ;
• ! .! !- 7 - ! !. ! .6 ;
• ! .! !- b 7 , (.- !- ( ! ! 7 .
& ! - " - 5! 6 .
! .6 - - .! ' U " - "!) - E
; !. ( !- ! .6 !) " 7 7 )
!6 ( .
Материальная Нематериальная

• 6 ; 7 7 ( "7 .
• $ .! !- - U : - W ":.
• 7 U !) - ; !) - 7
• $ ); 6 !) - !.
• $.; ( - U ; ' 6 ! .
• 0 .(9 : ' ( ' 7 ! -
! - .
• -7 ! ; 6
• ! - - - "
• $ 6 - " ( 7 7 6 ! 7
& + Y & + _

You have completed the following skills assessment for your team, rating each
person from 1 (low) to 5 (high) for their competency in each area
You are in the middle of a very technical project with significant problems. Tester D
is quite junior and needs frequent guidance. You have to go on vacation for the
next two weeks. Who is the best person on your team to handle the test
management tasks while you are gone?
a. Tester A
b. Tester B
c. Tester C
d. Tester E

You have completed the following skills assessment for your team, rating
each person from 1 (low) to 5 (high) for their competency in each area.
You have an opportunity to send one of your testers to speak at a conference on the
importance of technical testing skills in software testing. This person will also be expected to
attend other seminars and bring back and disseminate that information to the team. Who is
the best candidate for this opportunity?
a. Tester A
b. Tester C
c. Tester D
d. Tester E

You have completed the following skills assessment for your team, rating
each person from 1 (low) to 5 (high) for their competency in each area.
You have a limited training budget, but you can afford to send two people to a course on peer
coaching. In order to best benefit the department, who should you send to this training?
a. Testers C and D
b. Testers A and C
c. Testers B and E
d. Testers B and D

A. W, X
B. V, Y
C. X,Z
D. Y, Z

X‰ + ,
+ ^ + `+
, IT,
AGILE

95% ^ + ^0 0+
& + +Y 0 +
+ Z , $ 0
X + “ &”.

+ Y + 0 &,
/ X ZY, $ Y 0 ‰
+ 0+ + +Y + ^ + ,
+ •+ [
0 ZY, ZY
+ ^0 ZY.

& 0 [ & 0
+ 0 & . / +,
$ 0 + $ + .

_ $ X + & X ],
+ $
‰ + _ :
$ 10 & 0+,
& $
^ + .
[ ^ + +, X+
0 +0$ + & X /,
$ $ & `+ $ $ + Z +Y
^ Y‰ $ +0$ .

+ ]+ “ ] ” + &
^ &, X+ ^ [ & +Y
“Z + ‰ 0”, + & Y.

] , + ]
$ + + 0 ,
$ +Y ] ]
+ ], [ $ ^ +
0 Y+ + [ ^ + .

^0 + + Y
[ +Y, X+0+
& & ].
^0 + + Y
+Y, ^0 0+ X + +Y
+ &.

0 [ + 0 , 0
$ 0 + $ + , +Y ]
[ + .

0 0X +Y ^ +
Z+ y +Y ^ +
0 Y +Y, $ + &0 X+X ` ,
+ 0 `+
0 Y –•+ ^ +,
+ ] + + .

$ & ` + 0 ,
0& +Y /
0 + Y.
$ [ ]+ [ +
Z , + ]+
$ / +Y /
& + + Y .

$ $ X
$ +Y ^ X 0`
$ 0 / +Y &
+ + + 0G ] ^ + .

& 0X Y
$0 +Y y &
& + [ _ +
+ $ & & .

/ Y Z [ ,
$ + ‰+ X0 + +Y, X+
$ / + 0.
$ + ^G ]+ Y
0XZ & + 0 & .
^ ]+ & + Y
_ Y` & + _ ,
$ 0X y & _

^0 +
+Y ^ +
, $ ] 0
+ + + 0`G &
] + &.
X +0` 0
-
+ + X $ & + +Y
X
$ & ^ &

“Yesterday is history,
tomorrow is a mystery,
and TODAY is a gift...
that's why they call it
PRESENT”
MASTER OOGWAY

Test Management by Vladimir Arutin

Recomendados

Recomendados

Más contenido relacionado

Similar a Test Management by Vladimir Arutin

Similar a Test Management by Vladimir Arutin (20)

Más de Vladimir Arutin

Más de Vladimir Arutin (7)

Último

Último (20)

Test Management by Vladimir Arutin