blackboxandwhiteboxtesting in software testing.ppt

blackboxandwhiteboxtesting in software testing.ppt

• 1.
  BLACKBOX AND WHITEBOXTESTING
• 2.
  BLACKBOX TESTING  InBlack Box Testing we just focus on inputs and output of the software system without bothering about internal knowledge of the software program. [Figure of Blackbox Testing]  The above Black Box executable program can be any software system you want to test.
• 3.
  BLACKBOX TESTING  Byapplying black-box techniques, you derive a set of test cases that satisfy the following criteria:  (1) test cases that reduce, by a count that is greater than one the number of additional test cases that must be designed to achieve reasonable testing, and  (2) test cases that tell you something about the presence or absence of classes of errors, rather than an error associated only with the specific test at hand.
• 4.
  BLACKBOX TESTING  BlackboxTechniques/ Methods:  Equivalence partitioning: It is a software test design technique that involves dividing input values into valid and invalid partitions and selecting representative values from each partition as test data.  Boundary Value Analysis: It is a software test design technique that involves determination of boundaries for input values and selecting values that are at the boundaries and just inside/ outside of the boundaries as test data.  Cause effect graphing: It is a software test design technique that involves identifying the cases (input conditions) and effects (output conditions), producing a Cause-Effect Graph, and generating test cases accordingly.
• 5.
  WHITEBOX TESTING:  WhiteBox Testing (also known as Clear Box Testing, Open Box Testing, Glass Box Testing, Transparent Box Testing, Code-Based Testing or Structural Testing) is a software testing method in which the internal structure/ design/ implementation of the item being tested is known to the tester.  White Box Testing is like the work of a mechanic who examines the engine to see why the car is not moving.  Using white-box testing methods, you can derive test cases that  (1) guarantee that all independent paths within a module have been exercised at least once
• 6.
   (2) exerciseall logical decisions on their true and false sides  (3) execute all loops at their boundaries and within their operational bounds  (4) exercise internal data structures to ensure their validity. WHITEBOX TESTING:
• 7.
  WHITEBOX TESTING: [Figure ofWhitebox Testing Approach]
• 8.
  WHITEBOX TESTING: Why andWhen White-Box Testing:  White box testing is mainly used for detecting logical errors in the program code.  It is used for debugging a code, finding random typographical errors, and uncovering incorrect programming assumptions.  White box testing is done at low level design and implementable code.  It can be applied at all levels of system development especially Unit, system and integration testing.  White box testing can be used for other development artifacts like requirements analysis, designing and test cases.
• 9.
  WHITEBOX TESTING: Whitebox TestingTechniques:  Following are Whitebox testing techniques:  Statement coverage: This technique is aimed at exercising all programming statements with minimal tests.  Branch and decision coverage: This technique is running a series of tests to ensure that all branches are tested at least once.  Tools: An example of a tool that handles branch coverage testing for C, C++ and Java applications is TCAT-PATH  Path coverage: This technique corresponds to testing all possible paths which means that each statement and branch is covered.
• 10.
  WHITEBOX TESTING: [Figure ofPath coverage Example]
• 11.
  COMPARISON OF BLACKBOXTESTING AND WHITEBOX TESTING:
• 12.
  COMPARISON OF BLACKBOXTESTING AND WHITEBOX TESTING:
• 13.
  THANK YOU