software testing session 10 wims

8/13/2019 Software Testing Session 10 WIMS

1/30

ISAS SEMINAR ONSOFTWARE TESTING

Presented by

Jaikumar

Sudharshan


2/30

CONTENTS

1. Introduction

2. Testing objectives3. Testing principles

. !lassi"ication o" testing

#. $lack bo% testing


3/30

CONTENTS

1. &hite bo% testing

2. Per"ormance testing3. 'eliability testing

. Security testing

#. Testing automation


4/30

CONTENTS

1. (vailable Tools (nd Techni)ues

2. Testing level3. Testing cycle

. Summary

#. *ueries


5/30

INTRODUCTION

So"t+are testing,

Testing aso"t+are "or its

!orrectness

!ompleteness

Security.


6/30

INTRODUCTION

S*( - So"t+are *uality

(ssurance is testing a

so"t+are product

completely in a broader

aspect.

So"t+are testing is a

part o" S*(.


7/30

TESTING OBJECTIVES

Testing e%ecuting a program to "ind an

error*uality o" a test case, probability o" "inding

an as/yet undiscovered error.

( success"ul test uncovers a lot o"

undiscovered error


8/30

TESTING PRINCIPLES

(ll tests should be

0ade according to customer re)uirements planned long be"ore testing begins

begin in/the/small and progress to+ard in/

the/large

%haustive testing is not possible


9/30

Classification of testin

It is broadly classi"ied based on point o" vie+

a test engineer takes as $lack/bo% testing

&hite/bo% testing


10/30

BLAC! BO" TESTING

nly inputs and output "unctionality arevisible

Inputs are given and outputs are comparedagainst speci"ication.

o implementation details o" the code are

considered. 4ata driven testing.


11/30

BLAC! BO" TESTING

Targets, To "ind

incorrect or missing "unctions inter"ace errors

per"ormance errors


12/30

W#ITE BO" TESTING

!ontrary to black/bo% testing.

structure and code are visible. Implementation o" the so"t+are is given

importance

programming language5 logic5 and styles are

considered.


13/30

W#ITE BO" TESTING

Targets, To check

!ontrol/"lo+ 6ooping

data/"lo+

all the nodes or paths are covered ortraversed at least once.


14/30

PERFORMANCE TESTING

so"t+are should not take in"inite time or

in"inite resource to e%ecute. P'7'0(! $89S - process that

causes system per"ormance to degrade.

8sage o" +orkload to check so"t+are

per"ormance.


15/30

PERFORMANCE TESTING

Targets, To check

!P8 cycles.4isk space.

4isk access operations.

0emory usage.


16/30

RELIABILIT$ TESTING

probability o" "ailure/"ree operation o" a

so"t+are.'obustness testing / degree to +hich it can

"unction correctly in the presence o"

e%ceptional inputs.


17/30

RELIABILIT$ TESTING

Targets,

To check "or robustness problems such asmachine crashes.

process hangs.

abnormal termination.


18/30

SECURIT$ TESTING

eed "or security testing,

7la+s in so"t+are can be e%ploited byhackers.

&ith the development o" the Internet5

so"t+are security problems are becoming

even more severe.


19/30

SECURIT$ TESTING

Targets, To check

security violations. validating the e""ectiveness o" security

measures.

Simulated security attacks to "ind security

vulnerabilities.


20/30

TESTING AUTOMATION

The need,

So"t+are testing can be very costly. (utomation is a good +ay to cut do+n time

and cost.

In order to automate the testing process +e

have to generate the test cases to check "or

complete correctness.


21/30

TESTING AUTOMATION

Today +e still don:t have a "ull/scale system

that has achieved this goal. signi"icant amount o" human intervention is

still needed in testing.

The degree o" automation remains at the

automated test script level.


22/30

AVAILABLE TOOLS AND

TEC#NI%UES

( lot o" testing tools are available. some o" them are

Mothora :

3. mutation testing tool developed at Purdue university.

. !an create and e%ecute test cases5 measure

ade)uacy

#. 4etermine input - output correctness5 remove bugs


23/30

AVAILABLE TOOLS AND

TEC#NI%UES

NuMega's Boundschecker, National's Purify

2.

'untime checking and debugging aids.3. !heck and protect against memory leaks

and pointer problems. Ballista COTS Software Roustness Testing

!arness,#. 7ull scale automated robustness testing

tool.


24/30

TESTING LEVELS

"cce#tance testing- system re)uirement/per"ormed a"ter testing and be"ore

implementation phase."l#ha testing / testing by an independent

test team at developers: site. Beta testing $ eta %ersions released outside

the coany so&eti&es to o#en #ulic toincrease feedack


25/30

TESTING C$CLE


26/30

SUMMAR$

Testing is aTesting is a

destructive activity.destructive activity. Testing cannotTesting cannot

sho+ the absencesho+ the absence

o" de"ects.o" de"ects.

Testing ; 3


27/30

SUMMAR$

(ll tests should be

traceable tocustomer

re)uirements.

&hite/bo% testing.

$lack/bo% testing


28/30

SUMMAR$

So"t+are )uality5

reliability andsecurity are tightly

coupled.

'obustness5

per"ormance5reliability testing.


29/30

SUMMAR$

>Testing automation>Testing cycle

>Testing levels


30/30

software testing session 10 wims

Documents