gt 06 testing fundamentals 2

5/28/2018 GT 06 Testing Fundamentals 2

1/17

GAM

ETESTING

05 |Testing Fundamentals (2)Eriq Muhammad Adams J | [email protected]


2/17

GAM

ETESTING

The Test Process

2 type of testing Black Box Testing

White Box Testing


3/17

GAM

ETESTING

Black Box Testing

Almost all game testing isblack box

testing; No knowledge of, or access to, the

source code is granted to the tester.


4/17

GAM

ETESTING

Black Box Testing (cont.)

The player's feedback loop adjusts to thegame's input and vice versa.


5/17

GAM

ETESTING

White Box Testing

white boxtesting gives the tester anopportunity to exercise the source code

directly in ways no end user ever could.

Test :

new code for integration

cross platform modules

game engine

modders

low level routines


6/17

GAM

ETESTING

The Life Cycle of a Build

0. Plan and design the test

1. Prepare for testing

2. Perform the test

3. Report the results

4. Repair the bug

5. Return to step 1 and re-test.

Testing Process Feedback Loop


7/17

GAM

ETESTING

Testing By Numbers

There is a number of metrics to track andimprove testing results : Test Progress Chart (# of tests completed by team each day, # of tests

required each day)

Test Completed/Days of Effort (# of tests completed, # days of test

effort for each tester) Test Participation (# of days of effort for each tester, # of days each

tester assigned to test)

Test Effectiveness (# of defects, # of tests: for each release and/or

tester)

Defect Severity Profile (# of defects of each severity for each release)

Star Chart (# of defects of each severity for each tester)

Testing Star (# of defects of each severity for each tester, point value of

each severity)

Best Tester (# of tests per tester, # of total tests, # of defects per tester,

# of total defects)


8/17

GAM

ETESTING

Testing By Numbers : Testing Progress

Planned and actual test execution progress data


9/17

GAM

ETESTING


Planned and actual test execution progress graph.


10/17

GAM

ETESTING


Test completion rate per tester per day.


11/17

GAM

ETESTING


Tester participation rate calculations


12/17

GAM

ETESTING

Testing By Numbers : Testing Effectiveness

Test Effectiveness measurements


13/17

GAM

ETESTING


Test Effectiveness graph.


14/17

GAM

ETESTING


TE measured for individual testers.


15/17

GAM

ETESTING


Defect severity trend data.


16/17

GAM

ETESTING

Testing By Numbers : Tester Performance


17/17

GAM

ETESTING

Testing By Numbers : Tester Performance

Tester B executed 151 of the team's 570 Dev1 tests. This comes

out to 26.5%. B has also found 9 of the 34 Dev1 defects, which isalso 26.5%. B's composite rating is 53.

Tester C ran 71 of the 570 tests, which is 12.5%. C found 7 out of

the 34 total defects in Dev1, which is 20.5%. C's rating is 33.

Tester D ran 79 tests, which is approximately 14% of the total. D

also found 6 defects, which is about 17.5% of the total. D gets a

rating of 31.5.

Tester K ran 100 tests and found 3 defects. These represent

17.5% of the test total and about 9% of the defect total. K has a

26.5 rating. Tester Z ran 169 tests, which is about 29.5% of the 570 total. Z

found 9 defects, which is 26.5% of that total. Z's total rating is

56.

Tester Z has earned the title of "Best Tester."

gt 06 testing fundamentals 2

Documents