Scribd
Upload
8 views

4965white Box Testing

Uploaded by

dsouzaunknowndevilroy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
8 views

4965white Box Testing

Uploaded by

dsouzaunknowndevilroy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

White box testing, also known as clear box testing, glass box testing, or transparent box

testing, is a software testing method where the tester has full knowledge of the internal
workings, structure, and design of the application being tested. This approach allows
testers to create test cases based on the internal logic of the code, rather than just its
functionality from an external perspective.

Key Aspects of White Box Testing

1. Code Visibility: Testers can see the code and understand how it operates,
which helps in designing effective test cases.
2. Testing Techniques: It involves techniques such as code coverage, path
testing, and control flow testing to ensure that all possible paths and
branches in the code are tested.

3. Automation: White box testing can often be automated, allowing for more
efficient testing processes.

Necessity of White Box Testing

1. Thoroughness: It helps in identifying hidden errors and bugs that may not
be detected through black box testing, which focuses solely on input and
output without considering internal code structure.
2. Optimization: By examining the code, testers can identify redundant code
segments and improve system performance.
3. Security: It allows for a deeper analysis of security vulnerabilities within the
code, ensuring that potential exploits are identified and mitigated.
4. Maintenance: Understanding the code structure aids in easier maintenance
and updates to the software, as testers can pinpoint areas that need
attention.

5. Quality Assurance: It enhances overall software quality by ensuring that all


parts of the application are functioning as intended.

It is basically done by developers. Developers after completing the coding, they check each
and every line of code is working properly or not. Here code base is visible. Hence it is
called WBT. This can be done in the following ways:

● Unit testing,
● Path testing ,
● Predicate testing,
● Loop testing,
● Testing carried out from memory point of view,

● Testing carried out from performance point of view.

It is basically done by developers. Developers after completing the coding, they check each
and every line of code is working properly or not. Here code base is visible. Hence it is
called WBT. This can be done in the following ways:

● Unit testing,
● Path testing ,
● Predicate testing,
● Loop testing,
● Testing carried out from memory point of view,

● Testing carried out from a performance point of view.

Unit testing, testing carried out from memory and performance point of view can be done in
both the ways i.e manually and using automation tools. Though it is done by developers, it
will be better for a test engineer to have knowledge on it.

White box testing, also known as clear box testing or structural testing, involves testing the
internal structures or workings of an application. It requires knowledge of the internal logic
and structure of the code. Here are the main types of white box testing:

1. Unit Testing:
- Focuses on testing individual components or functions of the software in
isolation.
- Typically done by developers during the development phase.
2. Integration Testing:
- Tests the interaction between integrated components or systems.
- Ensures that combined parts work together as expected.
3. Functional Testing:
- Verifies that the software functions according to specified requirements.
- Tests specific functionalities of the application.
4. Code Coverage Testing:
- Measures the amount of code that is executed during testing.
- Helps identify untested parts of the codebase, such as branches or paths.
5. Control Flow Testing:
- Focuses on testing the control flow of the software.
- Involves creating test cases that execute various paths through the code.
6. Data Flow Testing:
- Examine the flow of data within the software.
- Ensures that data is properly defined, used, and destroyed.
7. Mutation Testing:
- Involves modifying the code (mutations) to check if the existing test cases
can detect the changes.
- Helps assess the effectiveness of test cases.

8. Static Code Analysis:


- Involves analyzing the code without executing it.
- Tools are used to identify potential vulnerabilities, coding standards
violations, and other issues.

Each type of white box testing serves a specific purpose and helps improve the quality and
reliability of the software by ensuring that the internal workings are functioning correctly.

You might also like