White box testing involves looking at the structure of the code. When you know the internal structure of a product, tests can be conducted to ensure that the internal operations performed according to the specification. And all internal components have been adequately exercised.

While white box testing is applicable at the unit, integration and system levels of the software testing process, it is typically applied to the unit. While it normally tests paths within a unit, it can also test paths between units during integration, and between subsystems during a system level test. Though this method of test design can uncover an overwhelming number of test cases, it might not detect unimplemented parts of the specification or missing requirements, but one can be sure that all paths through the test object are executed.

Typical white box test design techniques include:

* Control flow testing

* Data flow testing

Answered by jaivir , an ibibo Master, at 5:19 PM on September 11, 2008

The White Book, which was released in 1993 by Sony, Philips, Matsushita, and JVC, is the specification document for Video CD (VCD). Like other compact disk (CD) standards documents, the White Book is based on the original CD specification document, Philips and Sony's Red Book. VCD is defined in the White Book as a particular adaptation of CD-ROM XA (extended architecture) that is designed to hold MPEG-1 video data. The CD-ROM XA sector structure (as described in the Yellow Book and ISO 9660) is used to define the physical and logical blocks, and MPEG-1 is used to compress data so that full-screen, full-motion video data can be contained on the disk - without compression, the disk could only hold about 2 minutes worth of video. VCD resolution is similar to that of VHS.
White Book specifications include the disk format (such as the use of tracks, for example), a data retrieval structure compatible with ISO 9660, data fields to enable fast forward and reverse, and closed captioning. VCD, Photo CD, and Karaoke CD are defined as bridge disks, a format based on CD-ROM XA to enable the disks to work in compatible CD-ROM and CD-i (CD-Interactive) drives. Following the original specifications, VCD 2.0 was released in 1995, VCD-Internet in 1997, and SuperVCD in 1998, all from extensions to the White Book. Video CD is expected to be one of the first of all the CD formats to be completely supplanted by digital versatile disk (DVD) technology, which is of much higher quality.

Answered by Nishu's , an ibibo Master, at 10:12 AM on September 11, 2008

White box testing strategy deals with the internal logic and structure of the code. White box testing is also called as glass, structural, open box or clear box testing. The tests written based on the white box testing strategy incorporate coverage of the code written, branches, paths, statements and internal logic of the code etc.

In order to implement white box testing, the tester has to deal with the code and hence is needed to possess knowledge of coding and logic i.e. internal working of the code. White box test also needs the tester to look into the code and find out which unit/statement/chunk of the code is malfunctioning.

Advantages of White box testing are:
i) As the knowledge of internal coding structure is prerequisite, it becomes very easy to find out which type of input/data can help in testing the application effectively.
ii) The other advantage of white box testing is that it helps in optimizing the code
iii) It helps in removing the extra lines of code, which can bring in hidden defects.

Disadvantages of white box testing are:
i) 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.
ii) And it is nearly impossible to look into every bit of code to find out hidden errors, which may create problems, resulting in failure of the application.

Answered by Sharad Singh , an ibibo Master, at 7:10 PM on September 10, 2008

White Box Testing are tests that are run an application with the knowledge of the internal working of the code base. White box testing is used in three of the six basic types of testing: unit, integration, and regression testing. Unit testing is done on a small piece, or unit, of code. This unit is usually a class. When a unit is integrated into the main code base, it is more difficult to find a bug in that unit. Integration testing looks at how all components of an application interact. White box integration tests specifically look at the interfaces between the components. Regression testing verifies that modifications to the system have not damaged the whole of the system. Unit tests and integration tests can be rerun in regression testing to verify that modifications to the application work properly.

White box test cases should test different paths, decision points (both true and false decisions), execute loops, and check internal data structures of the application. Basis path testing, equivalence partitioning, and boundary value analysis are all used to create white box tests. Basis path testing looks at the decision points in the application. Equivalence partitioning divides the set of possible input values into equivalence classes. Only a value from each of the equivalence classes needs to be tested. Boundary value analysis looks at testing around a set boundary. A test case should be made for the boundary value, n, n-1, and n+1.

The goal of white box testing is to cover testing as many of the statements, decision point, and branches in the code base as possible.

For more details :

http://openseminar.org/se /modules/46/index/screen.do

Answered by Shobhit , an ibibo Master, at 6:04 PM on September 10, 2008

White box testing - This testing is based on knowledge of the internal logic of an application’s code. Also known as Glass box Testing. Internal software and code working should be known for this type of testing. Tests are based on coverage of code statements, branches, paths, conditions.

Source: http://thiyagarajan.wordpress. com/2008/03/14/types-of-softwa re-testing/

Answered by alok , an ibibo Master, at 5:51 PM on September 10, 2008

well, White box testing (a.k.a. clear box testing, glass box testing or structural testing) uses an internal perspective of the system to design test cases based on internal structure. It requires programming skills to identify all paths through the software. The tester chooses test case inputs to exercise paths through the code and determines the appropriate outputs. In electrical hardware testing. While white box testing is applicable at the unit, integration and system levels of the software testing process, it is typically applied to the unit. While it normally tests paths within a unit, it can also test paths between units during integration, and between subsystems during a system level test. Though this method of test design can uncover an overwhelming number of test cases, it might not detect unimplemented parts of the specification or missing requirements.
source site: http://en.wikipedia.org/wiki/W hite_box_testing

Answered by Nidhi Singh , an ibibo Master, at 5:50 PM on September 10, 2008

well,WHITE BOX TESTING. Testing based on an analysis of internal workings and structure of a piece of software. Includes techniques such as Branch Testing and Path Testing. Also known as Structural Testing and Glass Box Testing.
source:www.aptest.com/testtype s.html -

Answered by Debashis , an ibibo Master, at 3:29 PM on September 10, 2008

White box testing involves looking at the structure of the code. When you know the internal structure of a product, tests can be conducted to ensure that the internal operations performed according to the specification. And all internal components have been adequately exercised.

White Box Testing is coverage of the specification in the code.

Code coverage:

Segment coverage:
Ensure that each code statement is executed once.

Branch Coverage or Node Testing:
Coverage of each code branch in from all possible was.

Compound Condition Coverage:
For multiple condition test each condition with multiple paths and combination of different path to reach that condition.

Basis Path Testing:
Each independent path in the code is taken for testing.

Data Flow Testing (DFT):
In this approach you track the specific variables through each possible calculation, thus defining the set of intermediate paths through the code.DFT tends to reflect dependencies but it is mainly through sequences of data manipulation. In short each data variable is tracked and its use is verified.
This approach tends to uncover bugs like variables used but not initialize, or declared but not used, and so on.

Path Testing:
Path testing is where all possible paths through the code are defined and covered. Its a time consuming task.

Loop Testing:
These strategies relate to testing single loops, concatenated loops, and nested loops. Independent and dependent code loops and values are tested by this approach.

we do White Box Testing To ensure:

* That all independent paths within a module have been exercised at least once.
* All logical decisions verified on their true and false values.
* All loops executed at their boundaries and within their operational bounds internal data structures validity.

Need of White Box Testing To discover the following types of bugs:

* Logical error tend to creep into our work when we design and implement functions, conditions or controls that are out of the program
* The design errors due to difference between logical flow of the program and the actual implementation
* Typographical errors and syntax checking

For more visit :

http://www.softwaretestin ghelp.com/white-box-testing/

Answered by Ashish Yadav , an ibibo Wizard, at 3:14 PM on September 10, 2008

Welll , White box testing (a.k.a. clear box testing, glass box testing or structural testing) uses an internal perspective of the system to design test cases based on internal structure. It requires programming skills to identify all paths through the software. The tester chooses test case inputs to exercise paths through the code and determines the appropriate outputs. In electrical hardware testing, every node in a circuit may be probed and measured; an example is in-circuit testing (ICT).

Since the tests are based on the actual implementation, if the implementation changes, the tests probably will need to change, too. For example ICT needs updates if component values change, and needs modified/new fixture if the circuit changes. This adds financial resistance to the change process, thus buggy products may stay buggy. Automated optical inspection (AOI) offers similar component level correctness checking without the cost of ICT fixtures, however changes still require test updates.


While white box testing is applicable at the unit, integration and system levels of the software testing process, it is typically applied to the unit. While it normally tests paths within a unit, it can also test paths between units during integration, and between subsystems during a system level test. Though this method of test design can uncover an overwhelming number of test cases, it might not detect unimplemented parts of the specification or missing requirements, but one can be sure that all paths through the test object are executed.

Typical white box test design techniques include:

* Control flow testing

* Data flow testing

For more details , Please visit the source site :

http://www.google.co.in/s earch?hl=en&q=whit+box+testing &btnG=Search&meta=

Answered by Alok Gupta , an ibibo Guru, at 3:06 PM on September 10, 2008

well, White box testing (a.k.a. clear box testing, glass box testing or structural testing) uses an internal perspective of the system to design test cases based on internal structure. It requires programming skills to identify all paths through the software. The tester chooses test case inputs to exercise paths through the code and determines the appropriate outputs. In electrical hardware testing, every node in a circuit may be probed and measured; an example is in-circuit testing (ICT).

Since the tests are based on the actual implementation, if the implementation changes, the tests probably will need to change, too. For example ICT needs updates if component values change, and needs modified/new fixture if the circuit changes. This adds financial resistance to the change process, thus buggy products may stay buggy. Automated optical inspection (AOI) offers similar component level correctness checking without the cost of ICT fixtures, however changes still require test updates.



Source: http://en.wikipedia.org/wiki/W hite_box_testing

Answered by Satya ~ , an ibibo Master, at 3:04 PM on September 10, 2008