Your SlideShare is downloading. ×
0
Black box testing
Black box testing
Black box testing
Black box testing
Black box testing
Black box testing
Black box testing
Black box testing
Black box testing
Black box testing
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Black box testing

433

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
433
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
21
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

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

    • 1. BLACK BOX TESTING
    • 2. Definition
      Web definition
      “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.”
      (-http://www.bughuntress.com)
    • 3. Also known as..
      Data driven testing
      Input/output based testing
      Specific based testing
    • 4. View software as BLACK BOX
    • 5. Aims at finding cases in which the software does not behave according to its specifications or requirements errors
      The main criterion is exhaustive input testing!!!!
      Test data are derived from the specification
      (no need for taking advantage of knowledge of code)
    • 6. Advantage
      Easy to use
      Quicker test and case development
      Simplicity
      The environment the program is running is also tested
      The invested effort can be used multiple times.
    • 7. Disadvantage
      The results are often overestimated.
      The reason for a failure is not found.
      Not all properties of a software product can be tested
    • 8. Ideal Tools should have..
      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
      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
      Exploratory testing: testing without specific expectation about test outcomes, and generally without a precise test plan
    • 9. Data analysis:
      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.
    • 10. Example
      Eggplant
      IBM Rational Functional Tester
      GUI dancer

    ×