CH05.L01 . Black box or white box testing

Summary

This script delves into the distinctions between Black Box and White Box Testing, highlighting their respective applications in software development. Black Box Testing, akin to 'specification-based testing', is used for functional and non-functional testing without considering the internal system structure, suitable for later stages like System and Acceptance Testing. In contrast, White Box Testing, known as 'structural-based' or 'glass box', involves examining the system's internal code, crucial for early stages such as Unit and Integration Testing. The script also emphasizes the importance of 'Test to pass' for validating minimum requirements and 'Test to fail' for uncovering software weaknesses, suggesting that practice and learning are key to effective test case development.

Takeaways

• 🔍 Black Box Testing is used for functional and non-functional testing without considering the internal structure of the system.
• 📚 Black Box Testing is based on specifications, where inputs are added and outputs are checked against expected results.
• ✅ If the output matches the expected result in Black Box Testing, it's considered a 'pass'; otherwise, it's a 'fail'.
• 👀 Black Box Testing is conducted from the perspective of an end user without technical background, focusing on the program's functionality.
• 🏢 Black Box Testing is suitable for later testing stages such as System Testing and Acceptance Testing.
• 💼 White Box Testing, also known as Structural Based Testing or Glass Box Testing, allows the tester to see the internal structure and requires access to the source code.
• 🔍 White Box Testing focuses on the code structure, ensuring all paths, conditions, and statements are executed and checked for bugs.
• 🔨 White Box Testing is more suitable for initial testing levels like Unit Testing and Integration Testing.
• 📝 Test cases can be written for two purposes: 'Test to pass' for the happy scenario and 'Test to fail' for the bad scenario.
• 💡 'Test to pass' aims to ensure the software meets its minimum requirements, simulating typical user behavior.
• 🚨 'Test to fail' involves creating the most challenging scenarios to find software weaknesses and bugs, often requiring creative and destructive test cases.

Q & A

What is Black Box Testing?

Black Box Testing is a method of testing where the tester focuses on the functionality of the software without considering the internal structure or the source code. It is based on the software's specifications and is used to determine if the software behaves as expected when given specific inputs.

What is White Box Testing?

White Box Testing, also known as Structural Based Testing or Glass Box Testing, is a method where the tester has access to the internal structure of the software, including the source code. It focuses on the paths, conditions, and statements in the code to ensure that all parts of the code are executed and tested.

When is Black Box Testing typically used?

Black Box Testing is suitable for the later stages of testing, such as System Testing and Acceptance Testing. It is used when the tester wants to evaluate the software from the end user's perspective without needing to understand the internal workings of the software.

When is White Box Testing typically used?

White Box Testing is more suitable for the initial levels of testing, such as Unit Testing and Integration Testing. It is used when the tester needs to understand and test the logic and structure of the software code.

What is the purpose of Black Box Testing?

The purpose of Black Box Testing is to verify that the software meets its functional requirements as specified in the software specifications. It checks if the software produces the expected output when provided with specific inputs.

What is the purpose of White Box Testing?

The purpose of White Box Testing is to ensure that all paths and conditions in the software code are tested. It helps in identifying any untested code paths or conditions that might lead to bugs or errors.

What is meant by 'specification based testing' in the context of Black Box Testing?

'Specification based testing' refers to a testing approach where the test cases are designed based on the software's specifications. The tester does not need to look at the internal code but focuses on whether the software behaves as described in the specifications.

What is the significance of 'Structural based testing' in White Box Testing?

'Structural based testing' in White Box Testing means that the test cases are designed based on the structure of the software code. The tester checks if all code paths, conditions, and statements are executed as expected.

What are the two main reasons for writing test cases in any testing technique?

The two main reasons for writing test cases are to 'Test to pass' and 'Test to fail'. 'Test to pass' aims to ensure that the software meets its minimum requirements and behaves as expected under normal conditions. 'Test to fail' aims to identify the weaknesses in the software and find bugs by testing the software under extreme or unexpected conditions.

How does the approach to test case design differ between Black Box Testing and White Box Testing?

In Black Box Testing, test cases are designed from the perspective of an end user, focusing on the software's functionality and expected outcomes. In White Box Testing, test cases are designed based on the internal structure and logic of the software code, focusing on ensuring that all code paths and conditions are tested.

Why is it important to train, practice, and learn in testing techniques?

Training, practicing, and learning in testing techniques help testers to better understand how to write effective test cases for both 'Test to pass' and 'Test to fail' scenarios. This improves the quality of testing and helps in identifying more bugs and ensuring that the software meets its requirements.

Outlines

00:00

🔍 Understanding Black Box and White Box Testing

This paragraph introduces the fundamental differences between Black Box Testing and White Box Testing. Black Box Testing is described as a 'specification-based testing' approach that focuses on the functionality and non-functionality of a system without considering its internal structure. It is suitable for later stages of testing such as System Testing and Acceptance Testing. In contrast, White Box Testing, also known as 'Structural based testing' or 'Glass box testing', involves examining the internal structure and source code of the system. This method is more suitable for initial testing levels like Unit Testing and Integration Testing. The paragraph also discusses the importance of writing test cases for both 'Test to pass' (Happy scenario) and 'Test to fail' (Bad scenario), emphasizing the need for thorough testing to ensure software reliability.

Keywords

💡Black Box Testing

Black Box Testing is a method of software testing where the tester focuses on the functionality of the software without any knowledge of its internal structure. It is called 'black box' because the tester treats the system as a 'black box' that transforms inputs into outputs. In the video, it is mentioned as being suitable for the last testing levels such as System Testing and Acceptance Testing, emphasizing the 'specification based testing' approach where the program's execution is tested against its specification without looking at the code.

💡White Box Testing

White Box Testing, also known as 'Structural based testing' or 'glass box testing', allows the tester to see the internal workings of the system, including the source code. It is focused on the code structure, ensuring all paths and conditions are tested. The video describes it as suitable for initial testing levels such as Unit Testing and Integration Testing, where the logic of the program is tested.

💡Functional Testing

Functional Testing is a type of testing that checks if the software functions correctly according to its specifications. It is a part of Black Box Testing where the tester verifies the output against the expected results without considering the internal code. The video script uses the example of testing a program that adds numbers, where the focus is on whether the output matches the expected result.

💡Non-Functional Testing

Non-Functional Testing evaluates the software's attributes that are not directly related to its functionality, such as performance, usability, and reliability. In the script, it is mentioned alongside Functional Testing as something that can be tested using Black Box Testing, without referring to the internal structure of the system.

💡Specification Based Testing

Specification Based Testing is a testing approach where tests are designed based on the software's specifications. It is a key aspect of Black Box Testing, as mentioned in the video, where the tester adds inputs and checks if the output matches the expected results written in the specification, without needing to see the program's code.

💡Structural Based Testing

Structural Based Testing is an approach where the test cases are designed based on the internal structure of the software, such as the code paths, conditions, and statements. It is a core concept of White Box Testing, as explained in the video, where the tester ensures that all parts of the code have been executed and checked for potential bugs.

💡System Testing

System Testing is the process of testing a complete, integrated software system to evaluate its compliance with specified requirements. The video script mentions it as one of the last testing levels where Black Box Testing is applied to ensure the system functions as intended from an end-user perspective.

💡Acceptance Testing

Acceptance Testing is performed to determine if the software is ready to be delivered to the end-user. It is often the final testing phase before deployment. The script highlights Acceptance Testing as a level where Black Box Testing is suitable to confirm that the software meets the user's needs and requirements.

💡Unit Testing

Unit Testing is the process of testing individual components or units of a software to determine if they function correctly. The video script describes it as an initial testing level where White Box Testing is appropriate to ensure each unit of the code is tested for logic and execution.

💡Integration Testing

Integration Testing is the phase where individual software modules are combined and tested as a group to ensure they work together correctly. The video mentions it as another initial testing level where White Box Testing is used to check the interaction between different parts of the software.

💡Happy Scenario

The 'Happy Scenario' refers to the testing approach where the aim is to ensure the software performs its minimum requirements as expected under normal conditions. The video script explains it as 'Test to pass', where test cases are written to confirm that the software works as intended without any issues.

💡Bad Scenario

The 'Bad Scenario' in software testing is the strategy of testing the software under extreme or unfavorable conditions to find its weaknesses and bugs. The video script describes it as 'Test to fail', where the tester intentionally chooses difficult scenarios to stress-test the software and identify potential failures.

Highlights

Black Box Testing is applied for functional and non-functional testing without referring to the internal structure of the system.

Black Box Testing is also known as 'specification based testing'.

In Black Box Testing, inputs are added to a running program without seeing the program's code.

The output is compared against the expected result written in the specification to determine if the test passes or fails.

Black Box Testing is suitable for System Testing and Acceptance Testing.

White Box Testing is referred to as 'Structural based testing' or 'glass box testing'.

White Box Testing involves seeing the internal structure of the system and having access to the source code.

This type of testing focuses on the structure of the code, ensuring all paths and conditions are covered.

White Box Testing is more suitable for initial levels of testing such as Unit Testing and Integration Testing.

Test cases in White Box Testing are designed for the logic test of the program.

Testing techniques can be used to write test cases for two reasons: to pass (Happy scenario) and to fail (Bad scenario).

The 'Test to pass' aims to assure that the software meets its minimum requirements.

The 'Test to fail' strategy involves choosing the hardest scenarios to find the weaknesses and bugs in the software.

Writing test cases that can damage the program is part of the 'Test to fail' approach.

Training, practicing, and learning are essential for effectively identifying 'test to pass' and 'test to fail' scenarios.

Both Black Box and White Box testing have their unique applications and are crucial in different stages of the software testing process.

Transcripts

Black Box Testing

& white Box Testing:

what is the difference between them? when do we use them?

which one of them will be used in

each level of testing?

That is what we will know together.

we will start with Black box testing

which we apply for functional and non-functional

without referring to

the internal structure of the system

which we call "specification based testing"

because I have

a running program and according to

its specification,I can try its execution

I will add input

without seeing the program's code.

if the output is the same as the expected result

written in the specification,

then the result is "pass".

if not, then it is "fail".

For example, if the required is a ,

it presents a certain value when

we add numbers on it. so we test

the output and if the result i have is correct or

without referring to the calculator's code

I should act from

the view of the end user,

and deal as a user

who doesn't have any technical background.

therefore, the Black box testing

is suitable for all the

last testing levels, such as

System testing and acceptance testing.

As for the White box testing

which we call "Structural based testing"

or "glass box testing".

From its name, we can understand that

I can see the internal of the system

and I have at least the source code.

it focuses on the structure

of the code. Since the code of

the system has paths, conditions

and many statements, this type

of testing ensures that

I have passed all paths and conditions

and check if the compiler makes

an execution for them, or there are

some lines of codes have not been checked

due to a certain bug. And since the test case design

in White box testing is written

for the logic test of the program,

so this way of testing is more suitable

for the initial levels of testing

such as: Unit Testing

and Integration Testing.

Finally, there is an important note in

any testing techniques, that we can write

the test case for 2 reasons: either

Test to pass, and that is what we call

the Happy scenario of the software,

or Test to fail, and that is what we call

the Bad scenario of the software.

in "Test to pass" our aim is to assure

that the software is doing its minimum

requirements. The way we write

the test case is simple, as the user

may use the software in a right way

without facing any problems.

for the "Test to fail",

I choose the hardest scenarios

of the software, and use the strategy

that finds out the weaknesses of the software

and lets me find the bugs as much as I can.

I write the test case with the ideas

that I can use to damage the program.

we have to notice that, when you

start to write the test case,

you may fail to write the test case

which makes this program fails.

or you don't know any scenarios.

Of course, this will be easier by training, practicing

and learning which will form a good reference

for us to find out "test to pass"

and "test to fail", whether we work

as Black box testing

or White box testing.