Software Testing Tutorial #18 - What is Black Box Testing
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
📦 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.
🛠️ 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
💡Input
💡Output
💡Functional Testing
💡Test Case
💡Create Account Feature
💡Internal Code
💡Browser
💡Expected Result
💡Verification
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.
Transcripts
hello everyone welcome again in the
software testing tutorial
we are going to learn what is black box
testing
now as the name suggests the black box
so usually in computing or engineering
the black box term
came from you know when you don't have
any
knowledge of internal workings of
anything
and you are just verifying the output
based on the input
that's what a black box usually in
engineering or computing means
now when we correlate that with the
testing it's basically the same thing
in terms of software testing so usually
what happens if i
if i draw the diagram so usually in the
black box what happens is you provide
the input you don't know what exactly
this is a black box for you
okay so as an end user if i'm a tester
or person testing that's that particular
you know software
i'll just provide the input
and then i'll verify the output
okay and if output is what is expected
then i'll say the test has passed right
so usually
this is what the you know
key thing to remember about the black
box is that you don't know what
exactly is the implementation within
this particular box
as a tester you're just verifying
the output based on different set of
inputs that you will provide
all right and this type of testing is
known as black box testing and
functional testing is
one of it right so in functional testing
you you have
you know usually it is the black box for
the software tester so let me take
same example that we took in the
previous tutorial so functional test
of this gmail create account feature
right so in the create account feature
what we did
uh if you are testing the create account
usually you will follow certain steps
which will be a test case
so here there are a couple of tests that
i have written so i'll launch
the application if i'm testing that
particular application i'll launch that
application
you know in some browser right so in
browser
and browser could be you know like
chrome firefox so that will be specific
in the test cases when you'll detail
this out in your test case right this is
just to explain you
the steps so that is why i have not
written written all the details in this
particular
scenario so first step will be to launch
gmail.com in the browser if the launch
is being successful then
i will say output is passed right so
in here input the step one input is
basically
launching gmail in the browser this is
my input right so these are the
actions that i'll do now when i
open the browser okay and i type in
gmail.com
and after typing gmail.com i hit enter
right or hit go then it opens the
gmail.com
as a software tester or person launching
this application
i don't know what all happens behind the
scene
before i see gmail.com page on my
browser
right so that is a black box for me all
the functionality that has happened
after i provided gmail.com in the
url or and then hit enter
then after that i don't know what has
happened what application
implementation is there what software
has been written to basically
you know fetch the data and show the
gmail.com page to me right so that is
black box for me and that is why
this is the black box testing or how the
black box testing
will work second input for me
in the same test case is the black box
testing so create click on create
account so once i click on
create account link say for example
then i'm not sure what implementation
has been done
once a user clicks on create account
right so i don't know what
coding is there within this particular
box as an end user i don't have any idea
about it
yet and i'm not concerned about the
internal coding how the methods are
written
how the classes are written how the
internal code is being called when i
click on create account
what all happens inside i'm just worried
about or i'm just concerned about
when i click on create account you know
link
i should be displayed or basically i'll
click
on i'll draw here so output should be
uh you know create
account page right which will have uh
provide your first name last name
so i'll say first name last name
i'll provide which email so i have to
search the email
and then provide the password and
then click on register alright so
i need to verify these details but
internally when i click on
create account how everything work or
how the code has run
internally as a manual tester as a
you know black box tester or black box
testing i'm not concerned about any of
those internal working details right so
this is how
the black box testing will happen and
what
or what black box testing is so each
step in your test case
j is is basically the input and whatever
expected result of your test case is
is the output in terms of black box
testing
in the third case i'll provide the you
input user details
right and then click on sign up button
so
once user details have been provided
here that becomes the input
and a user clicks on you know sign up or
register button
and then he should be redirected to the
this is the black box in this case
and he should be directed to the actual
gmail account right
so any step that we perform without the
knowledge of the internal working of the
software
uh is known as black box testing
right so this is what
black box testing is and i have covered
how
a particular test case can be easily
correlated or what exactly you do
in the black box testing you do not
worry about the internal code internal
structure what classes are there how the
calls
how the method and calls are being made
that is not
your concern in black box testing
right so that's all for this tutorial
about black box testing
i'll cover the details about the white
box testing
in upcoming tutorial thank you very much
for watching
Weitere ähnliche Videos ansehen
Software Testing Tutorial #17 - What is Functional Testing
Software Testing Tutorial #19 - What is White Box Testing
CH05.L01 . Black box or white box testing
ISTQB FOUNDATION 4.0 | Tutorial 36 | Value of White Box Test Techniques | CTFL Tutorials | TM SQUARE
ISTQB FOUNDATION 4.0 | Tutorial 19 | Test Types | White Box Testing | Black Box Testing | TM SQUARE
CH05.L08 . Conclusion
5.0 / 5 (0 votes)