Motive of White Box Testing
Posted by: kamaltyagy123 on: January 20, 2009
White Box testing is done with the code perspective. The emphasis is to ensure that each line of the code is executed atleast once.
Unit Testing: Testing performed to isolate and expose faults and failures as soon as the source code is available, regardless of the external interfaces that may be required. Often times, the detailed design and requirements documents are used as a basis to compare how and what the unit is able to perform. White and black-box testing methods are combined during unit testing.
Can derive test cases to ensure:
1. all independent paths are exercised at least once. 2. all logical decisions are exercised for both true and false paths. 3. all loops are executed at their boundaries and within operational bounds. 4. all internal data structures are exercised to ensure validity.
Why White box testing when black box testing is there to test conformance to requirements – Logic errors and incorrect assumptions most likely to be made when coding for “special cases”. Need to ensure these execution paths are tested. – May find assumptions about execution paths incorrect, and so make design errors. White box testing can find these errors. – Typographical errors are random. Just as likely to be on an obscure logical path as on a mainstream path.
“Bugs lurk in corners and congregate at boundaries”
White Box Testing Techniques
1. Basis Path Testing
a. Flow Graph Notation
b. Cyclomatic Complexity
c. Deriving Test Cases
d. Graph Matrices
2. Control Structure testing
a. Conditions Testing
b. Data Flow Testing
c. Loop Testing
White Box testing
Posted by: kamaltyagy123 on: December 5, 2008
A testing which is done at the coding level is called the white box testing. In white box testing the procedures and the coding standards are confirmed and the tester’s main motive is to find out the bugs due to poor coding etc
White box testing some times also called the Clear box testing.
Black box testing
Posted by: kamaltyagy123 on: December 1, 2008
A testing which is done only having outer view of the build or AUT (application under test) is called black box testing.
Outer view of the build means without having any knowledge of internal stucture of the ck box coding done. Black box testing is basically to test the functionality of the build and to check if the build we have made is according to the requirement or not.
Levels of Software Testing
Posted by: kamaltyagy123 on: November 26, 2008
Software Testing is the process of running a program in order to find the errors and mistake of the program at the time of execution. The main intention of Software Testing is to evaluate an attribute and to check the potentiality of the program whether it gives the required output. 
Testing is not just giving data’s and obtaining the output, it is entirely different – it works at the time if the software fails to function or if it never gives the required output. Discovering the various nonstarter modes of software is quite not possible. Software Testing helps to find and check the quality, safety, security, perfection and completeness of the software developed.
There are different stages of Software Testing and let us go through the process one by one.
Black-box testing:- The Black-box testing is one of the method that is involved in testing. In this method the test data is derived from the defined functional requisites without affecting the structure of the program at the time of completion. It otherwise termed as Input/Output driven, Data-driven or Requirement based Testing.
The major functionality of Black-box testing is to check the functionality of the module. Black-box testing also denotes to functional testing, which is a method of testing accented on carrying out the functions and assessment of both the input and the output data. Here the tester will indulge the software under the black box test, where the specification of the input and output will seeable. The functionality is calculated by detecting the output to the equivalent inputs.
White-box Testing:- White-box testing is just opposite to Black-box testing. The software is considered as a glass-box or white-box under this category, because the structure of the software and its flow rate is clearly seeable to the tester in this type. White-box testing is otherwise termed as Logic-driven testing, Glass-box testing or Design-based testing.
There are various proficiencies accessible in white-box testing, as the trouble of intractableness is alleviated by particular knowledge and care on the formation of the software below this test.
Search
Categories
- Black Box Testing (2)
- Gray Box Testing (4)
- Latest Testing Terms (3)
- Software Testing (3)
- Testing Interview Questions (3)
- Testing Tools (2)
- Uncategorized (1)
- White Box Testing (4)
