WhiteBox Testing.
-Testing each and every line of source code is known as White box testing.
WhiteBox Testing is done in Two ways.
1- Manually.
2- Automatically.
-While doing WBT manually the DE physically check each and everyline of Src and do the changes accordingly. This process becomes time consuming.
-While doing WBT automatically, the DE write the Test program using the S/W tool called as J unit, Test-NG.
Note- In WBT the Src languages and Test program language should be same.
-When we run the program it automatically check each and every lines of Src and give the result, (Pass/Fail)
There are Five types of WhiteBox Testing.
1.Path Testing.
-Path testing is a white-box testing technique used to design test cases by systematically analyzing the different execution paths in a program. In white-box testing, the internal structure and logic of the code are examined to ensure the thorough testing of all possible paths.
-In path testing, the program's control flow graph is analyzed, and test cases are created to cover all possible paths from the program's start to its end. This helps in ensuring that every statement in the code is executed at least once during testing.
-The goal of path testing is to design test cases that exercise different routes through the program, including loops, conditional statements, and branches. By covering all possible paths, testers can identify potential errors and ensure that the program behaves as expected under various conditions.
-Path testing can be complex, especially for larger programs with multiple branching paths. However, it provides a comprehensive way to validate the correctness of a program by examining its internal logic and ensuring that all possible paths are tested.
2.Condition Testing.
-Condition testing, also known as branch testing or decision testing, is a testing method that focuses on evaluating the different conditional branches in the code. It aims to ensure that all possible branches within each decision point (such as if statements or loops) are tested at least once. The goal is to verify that the program behaves as expected under different conditions.
-In this testing technique, test cases are designed to execute all possible outcomes of a decision. For example, if there is an if-else statement in the code, condition testing would involve creating test cases that cover both the true and false branches of the statement. By doing so, testers can identify and rectify issues related to incorrect or missing conditions, ensuring comprehensive test coverage and improved code quality.
-Overall, condition testing helps in verifying the correctness and reliability of the software by examining its behavior under various conditional scenarios.
3.Loop Testing.
-Loop testing in WhiteBox Testing focuses on examining the flow of control within loops in a program's source code. It aims to ensure that loops are tested thoroughly, including all possible paths such as zero iterations, one iteration, and multiple iterations.
During loop testing, test cases are designed to:
-Execute the loop zero times: Ensuring that the loop is bypassed when the condition is initially false.
-Execute the loop one time: Testing the loop with the minimum number of iterations.
-Execute the loop multiple times: Testing the loop with multiple iterations to ensure that it behaves as expected when the loop iterates more than once.
-This process helps identify issues related to loop initialization, boundaries, and termination conditions. By testing different scenarios within loops, developers can increase the reliability and robustness of their code.
4.Memory point of view.
-Memory point of view testing specifically focuses on how the software utilizes memory resources during its operation. It involves testing different aspects related to memory management, such as:
Memory Leaks: Checking if the application releases allocated memory properly after it is no longer needed. Memory leaks can lead to performance issues and system crashes over time.
Memory Corruption: Examining whether the application unintentionally modifies the content of allocated memory blocks, which can lead to unpredictable behavior or crashes.
Buffer Overflows: Identifying situations where the application writes more data to a block of memory, like an array, than it can hold. This can lead to overwriting adjacent memory, causing unexpected behavior or security vulnerabilities.
Memory Allocation and Deallocation: Ensuring that memory is allocated and deallocated appropriately, and that there are no instances of dangling pointers (pointers that continue to reference a memory location after the memory has been deallocated).
Memory Access Errors: Checking for improper access to memory, such as accessing uninitialized variables or accessing memory locations out of bounds, which can lead to program crashes or data corruption.
-By testing from a memory point of view, WhiteBox testers can identify these issues early in the development process, allowing developers to fix them before the software is released. This type of testing is crucial for ensuring the stability, reliability, and security of the software application.
5.Performance point of view.
-performance testing evaluates the system's performance from an internal perspective, focusing on its internal structures, code, and algorithms. Performance testing in the context of WhiteBox Testing involves assessing how well the internal components of a software application perform under specific conditions.
-This type of testing aims to identify performance bottlenecks, memory leaks, and issues related to the efficient use of system resources. Testers analyze the code, algorithms, and data structures to ensure they are optimized for speed, responsiveness, and resource utilization.
-By conducting performance testing in WhiteBox Testing, developers and testers can optimize the code and algorithms to enhance the software's overall performance, ensuring it meets the required speed and responsiveness criteria. This process helps in delivering a high-quality software product that performs efficiently under different conditions and user loads.