White Box Test
A software Test technique is also known as glass box, structural, clear box and open box Tests, white box Tests, whereby explicit knowledge of the internal processes of the element to be tested is used to select the test data.
Unlike black box testing, white box testing uses specific knowledge of the programming code to investigate outputs. The test is only accurate if the tester knows what the program is supposed to do. He or she can then see whether the program differs from his or her intended goal. White box testing does not take into account errors due to omission, and all visible code must also be readable.
A deep understanding of the system or component is possible if the tester understands this to program or code level. Almost all the time, the tester must therefore either understand or have access to the source code of the system – usually in the Form of specification documents.

The most important principles that support you in the successful execution of white box tests are:
* Statement Coverage-ensure that each line of code is tested.
* Branch Coverage-ensure that each branch (for example, true or false) is tested.
* Path coverage-make sure that all possible paths are tested.

White Box testing procedure is applicable to the following levels of software testing:

* Unit Testing: for testing paths within a unit.
* Integration test: for testing paths between units.
* System test: for Test paths between subsystems.

UNIT TESTING is a software test in which individual units/ components of a software are tested. The purpose is to verify that each unit of the software performs as designed. One unit is the smallest testable part of any software. It usually has one or more inputs and usually a single output. In procedural programming a unit may be an individual program, a function, a procedure, etc. In object-oriented programming, the smallest unit is a method, which may belong to a base/ super class, abstract class or derived/ child class. (Some treat a module of an application as a unit.
Advantage
* Tests can be started at an earlier stage. You don't have to wait until the GUI is available.
* Tests are more thorough, with the ability to cover most paths.
Disadvantage
* Because tests can be very complex, highly qualified resources are required, with thorough knowledge of programming and implementation.
* Maintenance of test scripts can be a burden if the implementation changes too often.
* Because this test method is closely linked to the application to be tested, tools cannot be readily available for any type of implementation/platform.
* Integration Test: Test for detecting defects at the interfaces and in the
Interactions between integrated components or systems. See also component integration
testing, system integration tests.
* system integration testing: Testing the integration of systems and packages; testing
Interfaces to external organisations (e.g. electronic data exchange, Internet).





https://www.exltech.in/software-testing-course.html





Exltechs Software Test Training Program

Being the best it Training Institute in Pune ExlTech provides an opportunity for candidates in the software testing course, the ISTQB certification, which will help you to get easily be able to place in the MNC interview.This is the best training institute in Pune to start your career in testing where you get best practical oriented software testing Training with 100% Placement guarantee.

For more details:https://www.exltech.in/