Software Testing Tutorial #18 - What is Black Box Testing

Software Testing Mentor

16 Nov 202006:53

Summary

TLDRThis tutorial explains the concept of black box testing in software testing. It highlights that in black box testing, the tester verifies the output based on the provided input without knowing the internal workings of the system. Using a practical example of testing the Gmail account creation feature, the video emphasizes how testers focus on the input and expected output while disregarding the internal code or implementation. The tutorial provides a step-by-step explanation of how this testing method works, making it easier for viewers to understand black box testing.

Takeaways

🔍 Black box testing involves verifying software functionality without knowing the internal workings.
💡 In black box testing, testers provide inputs and verify the outputs without worrying about the underlying code.
📦 The term 'black box' comes from engineering, where the internal process is unknown, and only input and output are observed.
📑 Functional testing is a type of black box testing where the tester focuses on functionality rather than implementation details.
🌐 Example: Testing Gmail's 'create account' feature involves providing inputs like URL, entering details, and verifying the result without knowing the internal code.
🚪 When testing, steps like opening Gmail in a browser and clicking 'create account' are seen as black box processes since the tester does not need to know how the backend works.
👤 As an end user, the tester is only concerned with the interface and ensuring the expected output is achieved after performing specific actions.
🔗 Each action performed, such as entering data or clicking buttons, serves as an input in black box testing, and the corresponding expected result is the output.
🧑‍💻 Black box testing contrasts with white box testing, where internal implementation details are crucial.
📚 The tester in black box testing focuses solely on functionality, not the underlying code, structure, or method calls.

Q & A

What is black box testing?
-Black box testing is a software testing method where the tester evaluates the output based on the input, without any knowledge of the internal workings or code of the software. The focus is solely on verifying the functionality from an external perspective.
What does the term 'black box' mean in computing or engineering?
-In computing or engineering, 'black box' refers to a system where the internal processes are not visible or known. The focus is on the inputs and outputs, without understanding or interacting with how the system functions internally.
How does black box testing relate to functional testing?
-Black box testing is a part of functional testing, where testers verify that the software behaves as expected based on the provided inputs. The internal code and logic are irrelevant to the tester in this method.
What is an example of black box testing in the context of the Gmail account creation process?
-An example is testing the Gmail account creation process. The tester inputs 'gmail.com' in the browser, clicks 'Create Account,' and then verifies that the appropriate page loads (asking for first name, last name, email, password, etc.). The tester is not concerned with the internal code or how Gmail processes these actions.
Why is the internal working of the software not a concern in black box testing?
-In black box testing, the goal is to verify the system's behavior based on input and output, rather than understanding or evaluating the internal code. The focus is solely on whether the software meets the expected functional requirements.
What does the tester do if the output is as expected in black box testing?
-If the output is as expected, the tester concludes that the test has passed. This means the software is functioning as required for the given set of inputs.
What are the key steps a tester follows in black box testing?
-The tester follows a series of steps like launching the application, providing inputs, and verifying the output against the expected results, without any regard for the internal logic or implementation of the system.
What would a black box tester verify when clicking on the 'Create Account' button in Gmail?
-A black box tester would verify that clicking the 'Create Account' button successfully navigates the user to a page that asks for details like first name, last name, email, and password. The tester is not concerned with how this process happens internally.
What is the relationship between test cases and black box testing?
-In black box testing, each test case consists of specific inputs and expected outputs. The tester executes the test case by providing inputs and checking if the output matches the expected results, without worrying about the internal structure or coding of the software.
How does black box testing differ from white box testing?
-Black box testing focuses on the external functionality of the software without considering the internal code, while white box testing involves testing the internal logic and structure of the code. In black box testing, the tester doesn't need to know how the software is implemented.

Outlines

00:00

📦 Introduction to Black Box Testing

In this paragraph, the concept of black box testing is introduced, explaining its origins in engineering and computing. The term refers to testing a system where the internal workings are unknown to the tester, and only the inputs and outputs are evaluated. The key takeaway is that the tester verifies the output without needing to understand the implementation details of the system.

05:03

🛠️ Black Box Testing in Software Development

This section correlates black box testing with software testing, explaining how testers provide input, verify the output, and determine if the test passes without knowing the internal mechanisms. The example used is a functional test case for Gmail's 'Create Account' feature. The tester inputs a URL and verifies if the Gmail page loads correctly without understanding the underlying processes.

🔍 Functional Testing Example: Gmail Create Account

Here, the author walks through an example of black box testing for the 'Create Account' feature in Gmail. The tester provides inputs such as first name, last name, and email, and checks if the correct output (a successfully created account) is displayed. The key point is that the tester does not need to know the internal coding, just that the expected result is achieved after the inputs are provided.

⚙️ Black Box Testing Steps Explained

This paragraph further illustrates black box testing by describing how testers provide user details, click buttons like 'Sign Up', and verify if the user is redirected to the correct page. Each test step is considered an input, while the observed outcome is the output. The lack of concern about the internal workings of the software is emphasized, as black box testers focus only on the user-facing results.

🎯 Conclusion and Next Steps

The conclusion reiterates the essence of black box testing, highlighting that testers do not need to understand the code, methods, or structure of the software. The focus is solely on inputs and outputs. The author also hints at covering white box testing in the next tutorial, which will delve into understanding the internal workings of the software.

Mindmap

Keywords

💡Black Box Testing

Black Box Testing refers to a method of software testing where the tester does not have any knowledge of the internal workings or implementation of the system being tested. The tester provides inputs and verifies the outputs without needing to understand the underlying code or logic. In the video, the speaker explains that this approach is analogous to using a 'black box' in engineering, where only the inputs and outputs are considered.

💡Input

Input in the context of black box testing refers to the data or actions a tester provides to the system in order to evaluate its performance. This could be URLs, form data, or commands. In the video, the speaker gives examples such as entering 'gmail.com' in a browser or providing user details in a registration form, both of which are inputs used to test software functionality.

💡Output

Output is the result produced by the software after processing the given inputs in black box testing. The tester evaluates whether this result matches the expected outcome. In the video, the output is described as the successful launch of 'gmail.com' or the display of a 'Create Account' page after clicking a link, with the expected result confirming whether the test has passed.

💡Functional Testing

Functional Testing is a type of black box testing that focuses on verifying that the software performs its intended functions correctly based on given inputs. It tests the software’s functionality against the requirements without regard to the internal code structure. The speaker relates functional testing to testing features like Gmail’s 'Create Account' functionality by ensuring all steps in the process work as expected.

💡Test Case

A Test Case is a set of conditions or actions used by testers to determine whether a software system behaves as expected. It includes inputs, execution steps, and expected outputs. In the video, the speaker outlines a test case for Gmail’s 'Create Account' feature, where launching the Gmail page and clicking on the 'Create Account' link are part of the test steps.

💡Create Account Feature

The 'Create Account' feature is used as an example in the video to demonstrate how black box testing is applied in a real-world scenario. It refers to the functionality in Gmail where users can create new accounts by filling out their details. This example is used to explain how testers input user information and expect the system to respond with the next step, such as directing the user to a registration page, without knowing the internal code.

💡Internal Code

Internal Code refers to the underlying programming and logic that drives the software's functionality. In black box testing, the tester is not concerned with or knowledgeable about this code. As explained in the video, when testing features like 'Create Account' in Gmail, the tester does not need to know how the internal methods, classes, or functions work, but only verifies the outputs from inputs.

💡Browser

A Browser is a software application used to access the web, such as Chrome or Firefox. In the video, the browser is a tool through which the test is conducted. For instance, the speaker mentions launching 'gmail.com' in a browser as an input step to test the 'Create Account' functionality, illustrating how external tools are used in black box testing.

💡Expected Result

Expected Result refers to the outcome that a tester anticipates after providing an input in a test case. If the actual result matches the expected result, the test is considered successful. The speaker uses the example of clicking on the 'Create Account' link and expecting the Gmail registration page to appear as the expected result in this test scenario.

💡Verification

Verification is the process of checking whether the software output matches the expected result based on the input given. It is a key part of black box testing, as testers are responsible for confirming that the software behaves as intended. In the video, verification happens after each step in the Gmail 'Create Account' test, such as confirming the Gmail page has loaded correctly after entering the URL.

Highlights

Introduction to black box testing and its significance in computing and engineering.

Black box testing involves verifying outputs based on input without knowledge of the internal workings.

The process of black box testing in software testing mimics the general concept used in engineering.

Testers provide input and verify output without concern for the implementation details of the software.

Functional testing is a type of black box testing used to verify software features.

Example of Gmail's create account feature is used to demonstrate black box testing.

Test case step one: Launch Gmail in a browser and verify if the page loads correctly.

Testers are unaware of how the Gmail page loads after providing the URL; this is the 'black box.'

Black box testing involves verifying the output of 'create account' without knowing the underlying code.

Second step: Clicking on the 'create account' link and verifying the appearance of the account creation page.

Internal workings of the code when clicking 'create account' are unknown to the tester in black box testing.

Output verification includes ensuring fields like first name, last name, email, and password appear on the page.

In the third step, input includes user details like name and email, while the output is account creation.

Manual testers focus on results and outputs, not the methods or internal processes behind them.

Summary: Black box testing focuses on functionality and expected outputs without internal code knowledge.