White box & Black box testing
- 1. White Box & Black Box Testing Presented By: Nitish Mhaske
- 2. What is White Box Testing ? ïŽ Testing internal coding and infrastructure ïŽ Identify which line of code is actually executed and which is not, which may indicate that there is either missing logic or a typo. ïŽ Internal Structure known in addition to i/o & Relationships. ïŽ Often used for verification. ïŽ Done by the Developers. ïŽ Structure-based / Glass-box testing ïŽ Called Because here the testers require knowledge of how the software is implemented.
- 3. How to encounter a bug in white box testing? ïŽ It involves testing a series of predefined inputs against expected outputs , so when a specific input does not result in the expected output, you have encountered a bug
- 4. Advantage of Whitebox Testing ïŽ Testing can be commenced at an earlier stage. ïŽ One need not wait for the GUI to be available. ïŽ Testing is more thorough, with the possibility of covering most paths. ïŽ The other advantage of white box testing is that it helps in optimizing the code
- 5. Disadvantage of Whitebox Testing ïŽ As knowledge of code and internal structure is a prerequisite. ïŽ A skilled tester is needed to carry out this type of testing, which increases the cost ïŽ Not looking at the code in a runtime environment...
- 6. What is Blackbox Testing? ïŽ Blackbox Testing is a software testing method in which the internal structure of the item being tested is not known to the tester.. ïŽ Blackbox testing is often used for Validation.. ïŽ Black box testing is done by the professional testing team. ïŽ Type 1. Functional 2. Non Functional 3. Reg Test
- 7. Advantage of Blackbox Testing ïŽ Tester can be non-technical. ïŽ Tester needs no knowledge of implementation, including specific programming languages ïŽ Tests will be done from an end user's point of view. Because end user should accept the system.
- 8. Disadvantage of Blackbox Testing ïŽ Not all properties of a software product can be tested ïŽ The reason for a failure is not found. ïŽ Only a small number of possible inputs can be tested and many program paths will be left untested..
- 9. Unit Testing ïŽ Unit testing is that validate individual unit of source code working properlyâŠ ïŽ Unit is smallest testable part of an application.. ïŽ Mostly done by developers of the modules.. ïŽ Done after Code compilation
- 10. Goal of Unit Testing ïŽ To isolate each part of program and show that individual parts are correct.. ïŽ Typically Written & run by s/w developer to ensure design & behaviour
- 11. Advantage of Unit Testing ïŽ Reduces the level of bugs in production code.. ïŽ Unit Testing inspires confidence.. ïŽ Makes easier to change and refactor code. ïŽ Concern with the correctness & Completeness ïŽ Isolate each part ïŽ Check conditional logic ïŽ Check for wiring bugs
- 12. Disadvantage of Unit Testing ïŽ Unit-testing will not catch every error in the program. ïŽ It only tests the functionality of the unitsâŠ.
- 13. Thank YouâŠ