8/14/2019 DOP2010 Introduction to Testing

1/16

TestingOverview

8/14/2019 DOP2010 Introduction to Testing

2/16

2

Content

Objective

Software Testing

Different Testing: Black Box Grey Box White Box

8/14/2019 DOP2010 Introduction to Testing

3/16

3

Objective of Test

The main objective of testing is

to detect software failures

so that defects may be discovered and corrected

8/14/2019 DOP2010 Introduction to Testing

4/16

4

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

8/14/2019 DOP2010 Introduction to Testing

5/16

5

Black Box Testing

Users see the system from the outside.

Users dont see your code, dont look at thedatabase tables, and dont evaluate youralgorithms.

They see the system as a black box , it eitherdoes what they ask for or it doesnt.

Users look at application functionality

8/14/2019 DOP2010 Introduction to Testing

6/16

6

Black Box Testing (2)

For a Daelim,

It is someone who

Dont know anything to mechanic

Know how to use it (to drive) it

8/14/2019 DOP2010 Introduction to Testing

7/167

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

8/14/2019 DOP2010 Introduction to Testing

8/168

Terminology

Black Box Testing = Functional TestingBug = Defect = Failure

8/14/2019 DOP2010 Introduction to Testing

9/169

Grey Box Testing

Testers look for the functionality but they alsowants to make sure that things are happening theway you said it would.

Testers will have a look at the database forexample to make sure the data are insertedcorrectly.

They can check that ports are closed, that memoryusage is staying stable.

They see the system as a grey box .

8/14/2019 DOP2010 Introduction to Testing

10/1610

Grey Box Testing (2)

For a Daelim,

It is someone who

Know basic mechanic skill enough to maintain motobikeChange lightsChange park plugRepair cable

Dont know advance mechanic skillsTo disassemble the engine

8/14/2019 DOP2010 Introduction to Testing

11/1611

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

8/14/2019 DOP2010 Introduction to Testing

12/1612

White Box Testing

Developers see the system as a white box .

They know everything about the systems, they seeclass design, design patterns, duplicated code.

But because they see so much detail they can misssome broken functionality or make an assumptionon what users will not do.

8/14/2019 DOP2010 Introduction to Testing

13/1613

White Box Testing (2)

For a Daelim,

It is someone who

Has advance mechanic skills

Know how toMaintain a motobikeCompletely disassemble the motorBuild the motor again

8/14/2019 DOP2010 Introduction to Testing

14/16

14

White Box Testing (3)

White box testing uses inside knowledge

Developers know exactly the code and they haveto do their best to make that code breaks

Developers should look for: Testing all the different branches of code Error handling

8/14/2019 DOP2010 Introduction to Testing

15/16

15Copyright 2007 - CIST

Any Question?

8/14/2019 DOP2010 Introduction to Testing

16/16

16C i ht 2007 CIST

The End