blackboxtestingvswhiteboxtesting lg1 f

7/29/2019 BlackBoxTestingVsWhiteBoxTesting LG1 F

1/26

x

White Box TestingLearning Group 1

Anand Menon 298

AmitKumar Das 305Kishor Kumar 319

Sidharth J ain 347

Murali Krishna 326Pawan Thakare - 329


2/26

According to ISTQB:

Testing, either functional or non-functional, without reference tothe internal structure of the component or system

The main ideas are simple:

y Define initial component state, input and expected output forthe test.

y Set the component in the required state

y Give the defined input

y Observe the output and compare to the expected output


3/26

y Not concerned with inner workin of a lication

BLACKBOX

y Mainly accepted for high level of testing

y Acceptance Testing

y System Testing

y Basis for testin is Re uirement S ecifications


4/26

Black Box testing techniquesy Equivalence Class Partitioning

y (+) no need of exhaustive testing

y

(+) Large domain of inputs and outputsy (+) identify a defective domain

y - assump on: a a n a c ass are processe s m ary

y (-) inputs at the boundaries

y oun ary a ue na ys s

y Decision Tables

y State Transition Diagrams


5/26

van ages o ac ox es ngy Tests are done from a end users point of view and will

help in exposing discrepancies in the requirementspecifications

y ester nee not now programmng anguages or t esoftware implementation

the developers, allowing for an objective perspectiveand the avoidance of developer-bias

y Test cases can be designed as soon as thespecifications are complete


6/26

sa vantages o ac ox estng

y Onl a small number of ossible in uts can be tested

and many program paths will be left untested

y Without clear s ecifications which is the situation inmany projects, test cases will be difficult to design

y Tests can be redundant if the software desi nerdeveloper has already run a test case.


7/26

Case Study BST GamesProblemsy US gaming industry > $ 10 billion, competition Xbox 360, Nintendo Wii,

PS3, etc.

y Longer development cycles (6 months 2 yrs)

y

Viral spread of news related to buggy softwareRequirements

y testing

Solution

y ualit Soft ro hired for inde endent third art black box testin of thenew RPG Shooter game

y Automated functional, regression, data driven, distributed tests

y Flexibl accommodated 32 bitand 64 bit latforms

Benefits

y Compressed development cycle with high confidence in game quality

of release

y Low cost


8/26

Demo of Black- Box Testin

(MS-Excel)


9/26


10/26

y Acce ted for followin levels of testin

y Unit Testingy Integration Testing

y System Testing

y Basis for testing is Detailed Design

y Mainly used for testing the algorithm and paths


11/26

f Whit -B x T tiny Statement Testin : Testin individual statements

y Loop Testing:

y

y Loop executed exactly once

y Loop executed more than once

y Path Testing: All paths in the program are executed

least once


12/26


13/26


14/26


15/26


16/26


17/26

Test case Condition-1 Condition-2

1 True Doesnt matter

2 False Doesnt matter

We can easily merge two cases. Only two test cases should be enough


2 False True


18/26

y 100% statement coverage

y Is it strong enough?


19/26


20/26

Refined Test Cases


1 True True

2 False False


21/26

y 100% branch coverage

y Is it strong enough? Can we do more?


22/26

y 100% path coverage

y Now its better !


23/26

van ages o e ox es ngy Testin can be commenced at an earlier sta e. One

need not wait for the GUI to be available.y Testin is more thorou h with the ossibilit of

covering most paths.

y White-box testin can deliver reater stabilit andreusability of test cases if the objects that comprise anapplication never change


24/26

sa vantages o te ox estng

y Since tests can be very complex, highly skilledresources are required, with thorough knowledge ofprogramming and implementation.

y est scrpt mantenance can e a ur en t eimplementation changes too frequently.

application being testing, tools to cater to every kind ofimplementation/platform may not be readily available.

y White Box Testing is like the work of a mechanic whoexamines the engine to see why the car is not moving.

d i l di l


25/26

Case Study: H Memorial MedicalLaboratories, NV

y SLIM document exchange, enterprise collaboration, automated workflow,regulatory compliance

Problems

y Original developer out-of-state before testing and re-engineering

y Huge Investment

Solution

y White box testing by Quality Softpro

y Thoroughly scrutinizing source code branch by branch

y Basis ath and loo testin

y Documenting bugs and failures

y Leaving audit trail for the H Memorial staff to follow

Benefits

y Dozens of bugs and bottlenecks removed before integration testing

y Investment saved


26/26

y http://softwaretestingfundamentals.com/black-box-testing/

y http://en.wikipedia.org/wiki/Black-box_testing

y ~. . . _ _vs_whitebox_testing.pdf

y http://softwaretestingfundamentals.com/white-box-testing/

y http://softwaretestingfundamentals.com/differences-between-black-box-testing-and-white-box-testing/

y http://www.youtube.com/watch?v=wLINA-Gj7eA

y http://www.qualitysoftpro.com/casestud -list.php

blackboxtestingvswhiteboxtesting lg1 f

Documents