Testing

Overview
 Content

• Objective

• Software Testing

• Different Testing:
– Black Box
– Grey Box
– White Box

2
 Objective of Test

• The main objective of testing is

– to detect software failures

– so that defects may be discovered and corrected

3
 Testing on Software

• Can be done by different kind of people

– User
– Tester
– Developer

• Each kind of people do different kind of test

– User do Black Box testing
– Tester do Grey Box testing
– Developer to White Box testing

4
 Black Box Testing

• Users see the system from the outside.

• Users don’t see your code, don’t look at the

database tables, and don’t evaluate your
algorithms.

• They see the system as a black box, it either

does what they ask for or it doesn’t.

• Users look at application functionality

5
 Black Box Testing (2)

• For a Daelim, …

• It is someone who…

– Don’t know anything to mechanic

– Know how to use it (to drive) it

6
 Black Box Testing (3)

• Black box testing focus on Input and Output:

– The users are outside of the system, they only see what
they put inside and what they get outside.

• Users testing should look for:

– Functionality
– User input validation
– Output results
– Boundary cases

7
 Terminology

Black Box Testing = Functional Testing

Bug = Defect = Failure

8
 Grey Box Testing

• Testers look for the functionality but they also

wants to make sure that things are happening the
way you said it would.

• Testers will have a look at the database for

example to make sure the data are inserted
correctly.

• They can check that ports are closed, that memory

usage is staying stable.

• They see the system as a grey box.

9
 Grey Box Testing (2)

• For a Daelim, …

• It is someone who…

– Know basic mechanic skill enough to maintain motobike

 Change lights
 Change park plug
 Repair cable

– Don’t know advance mechanic skills

 To disassemble the engine

10
 Grey Box Testing (3)

• Grey box testing gets closer to the code:

• The testers are doing

– the same thing than black box testing
– but they also looks at what going on under the system:
database tables, memory leak...

• Testers should look for:

– Database tables
– …

11
 White Box Testing

• Developers see the system as a white box.

• They know everything about the systems, they see

class design, design patterns, duplicated code.

• But because they see so much detail they can miss

some broken functionality or make an assumption
on what users will not do.

12
 White Box Testing (2)

• For a Daelim, …

• It is someone who

– Has advance mechanic skills

– Know how to
 Maintain a motobike
 Completely disassemble the motor
 Build the motor again

13
 White Box Testing (3)

• White box testing uses inside knowledge

• Developers know exactly the code and they have

to do their best to make that code breaks

• Developers should look for:

– Testing all the different branches of code
– Error handling
– …

14
 Any Question?

15
Copyright © 2007 - CIST
 The End

16
Copyright © 2007 - CIST