BLACK BOX TESTING <br />
Definition<br />Web definition<br />“Black-box testing implies that a tester doesn't know how an application is designed a...
Also known as.. <br />Data driven testing<br />Input/output based testing<br />Specific based testing<br />
View software as BLACK BOX<br />
Aims at finding cases in which the software does not behave according to its specifications or requirements errors<br />Th...
Advantage<br />Easy to use<br />Quicker test and case development<br />Simplicity<br />The environment the program is runn...
Disadvantage<br />The results are often overestimated.<br />The reason for a failure is not found.<br />Not all properties...
Ideal Tools should have..<br />Fuzzing: the injection of random or systematically-generated data at various interfaces, wi...
Data analysis:<br />Monitoring program behavior: When a large number of tests are automatically applied, it is useful to a...
Example <br />Eggplant<br />IBM Rational Functional Tester<br />GUI dancer<br />
Upcoming SlideShare
Loading in …5
×

Black box testing

765 views
569 views

Published on

Published in: Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
765
On SlideShare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
21
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Testing based on an analysis of the specification of a piece of software without reference to its internal workings.
  • Black box testing

    1. 1. BLACK BOX TESTING <br />
    2. 2. Definition<br />Web definition<br />“Black-box testing implies that a tester doesn't know how an application is designed at the code level, i.e., it involves dynamic testing of compiled applications. The tester interacts with the software system via its interface and analyzes the application reaction.”<br /> (-http://www.bughuntress.com)<br />
    3. 3. Also known as.. <br />Data driven testing<br />Input/output based testing<br />Specific based testing<br />
    4. 4. View software as BLACK BOX<br />
    5. 5. Aims at finding cases in which the software does not behave according to its specifications or requirements errors<br />The main criterion is exhaustive input testing!!!!<br />Test data are derived from the specification<br />(no need for taking advantage of knowledge of code)<br />
    6. 6. Advantage<br />Easy to use<br />Quicker test and case development<br />Simplicity<br />The environment the program is running is also tested<br />The invested effort can be used multiple times. <br />
    7. 7. Disadvantage<br />The results are often overestimated.<br />The reason for a failure is not found.<br />Not all properties of a software product can be tested<br />
    8. 8. Ideal Tools should have..<br />Fuzzing: the injection of random or systematically-generated data at various interfaces, with various levels of human intervention to specify the format of the data<br />Syntax testing: generating a wide range of legal and illegal input values, usually with some knowledge of the protocols and data formats used by the software<br />Exploratory testing: testing without specific expectation about test outcomes, and generally without a precise test plan<br />
    9. 9. Data analysis:<br />Monitoring program behavior: When a large number of tests are automatically applied, it is useful to also have automatic techniques for monitoring how the program responds.<br />
    10. 10. Example <br />Eggplant<br />IBM Rational Functional Tester<br />GUI dancer<br />

    ×