The core theme is to differentiate between a test scenario and a test case in software testing, explaining their relationship, how they are derived, and their practical application.
Mind Map
Click to expand
Click to explore the full interactive mind map • Zoom, pan, and navigate
hello everyone welcome again in the
software testing tutorial
we are going to understand difference
between test scenario and test case
now this is very important to understand
the difference between test scenario and
test case because both of them go hand
in hand
and you will be work whenever you are
working in any software testing project
you will be using them a lot and this
helps this these you know two concepts
test cases we have already understood
what exactly test case is
but test scenario you will listen you
know a lot
for example write the test scenario and
then test case so basically you need to
understand what exactly is test scenario
how it is related to test case how is it
different to test case
and how you apply practically these two things
things
in any software testing project all
right so let's first understand
the differences between test scenario
and test case
because once you know the differences
you will understand where
to apply which one and how both of them
are correlated all right
so if we talk about test scenario so
test scenario
is very high level okay so test scenario is
is
high level uh documentation of
basically what you are going to test in
application okay so
say for example i take an example of
e-commerce website
now e-commerce website has registration
functionality has login functionality
check out so there are a lot of
functionalities right now
if in your application you have one
particular functionality say for example
i'll take a login functionality okay so
i'll say
login functionality now
if we talk about the test scenario for
this particular functionality so test
scenario will be very high level
one liner you know scenario description
of what you are going to test in the
login functionality okay so for example
in the login functionality i want to
uh you know test login
user and password
okay then with invalid
user and password okay another scenario
then valid user
invalid password okay so these are just
one liner descriptions of what all
scenarios i'm going to cover as part of
the login functionality
right so one liners so when we write
high-level one-liner description of any
functionality or
what we are going to test in the
application that is
test scenario okay
now when we talk about the test case to
write a test case we refer back to the scenarios
scenarios
okay and test case is more detailed
description of
what you are going to test right so here
we are understanding
what we are going to test now when we convert
convert
these scenarios so basically we will use
these scenarios so
with valid username and password right
so this is one of the scenario
that we are going to test in the login
functionality now when we write the test
case for it
we describe or we describe the steps or
we elaborate
and we elaborate that how you are going
to test this
okay so in the test case what you will
do is you will write
the steps one two three four
the e-commerce portal in particular
browser okay
step two click on login link
step three enter a valid user and valid password
password
step four click on login button right
so these this elaboration that you do
for a particular scenario
becomes the test case okay
so this is a brief difference between
the test scenario and test case so test
scenario is
high level one liner and explains
what all you are going to test okay test case
case
along with what you are going to test it
also describes
how you are going to test it describes
the steps
of a particular scenario all right
now when we talk about the scenarios
so test scenarios mostly you will be
deriving from
requirement documents okay so
requirement documents
for example software requirement specification
specification
and user stories okay user stories or
any documents that are available which
will help you to come up with these
scenarios okay so because requirements
will have the detailed requirement of
login and in login functionality what
all requirements are being described for
the login functionality so
with seeing the requirements you can
easily come up with one liner
test scenario so you the baseline or
basically the basis
for writing the test scenarios is your
user stories your requirement
okay but in terms of test case
how you write the test case you
basically you then
derive your test case based on the
scenarios that you have written so
based on the srs you have written all these
these
scenarios right and then you refer to
these scenarios and you write the test
case for each of these
scenarios okay so that is the difference
between test scenario and test case
and how they are correlated so you have
the requirement from the requirements
from the user stories you come up with
the test scenarios
test scenarios are nothing but high
level liner
description of what all you are going to
test in that particular functionality
test case is more detailed description of
of
those scenarios so test cases are
derived from the
scenarios okay so requirement scenarios
and test case
so that's the hierarchy okay so you have
requirement from requirement you
come up with the scenarios and
from scenarios you write the test cases
you elaborate those
okay so this is how you actually do in
the practical
testing okay this is the flow you follow
in the any of the practical
testing approach because if you directly start
start
writing your test cases describing
detailing from the requirement it
most of the time you will miss couple of
steps so
this step is very important because you
apply your thought process you apply the
tester's mindset to basically
see what all combination what all
scenarios can be tested for that
particular feature
so you write all the positive negative
scenarios just
one liner quick one and then based on one-liner
one-liner
scenarios you convert those to test
cases which becomes really easy
okay so that is the difference between
the test scenario and test case
how they are related uh among each other
okay now next
is i'll explain one of the example
okay so let me take an e-commerce
website example
and i'll take a functionality
of registration okay
and let me write some of the scenarios
for this registration
and the test cases for that now
registration is one of the functionality which
which
will be described into the software
requirements or the user stories for
registration okay
so based on the user stories what i'll
do is
i'll start writing the scenarios
okay so first scenario that you can
think of
then register
with google
right so this is just one line i am
quickly writing okay
positive scenario so whatever
registration functionality supports
so say for example it also supports fbs
or also supports
registration using twitter account so
i'll write these four
scenarios okay fifth scenario
will will cover some of the negative
scenarios right so
um verify you know registration is not
successful with
registration fails
okay another scenario so negative scenario
scenario
so this is how you will keep extending or
or
thinking about how or what all
scenarios could be possible for this
particular functionality
right now your requirement document will
explain all
these things within the requirement
document and you will go through the
requirement document
understand those if there are in doubt
you will go back to the business analyst
and understand the gaps or
if there is any you know things that are
missing in the requirement you
understand those gaps
and keep extending these scenarios so
these are one-liner high-level scenarios
written once you have these scenarios written
written
then the next step is as a test engineer
i'll pick the scenario and then i'll convert
convert
this into the test case right
a scenario can be can have just one test case
case
for it or there could be a scenario
which is a combination of multiple test cases
cases
okay say for example a scenario at this
particular level
is specific to registration
functionality but
a scenario for end-to-end scenario or
end-to-end testing
could be a combination of registration
login you know adding items to cart so
in that particular case you write
one-liner scenario say for example
successful checkout or successful
purchase say for example right if i say
another scenario which is end-to-end
scenario of e-commerce website
so customer
items successfully
right so one liner
scenario okay foreign e-commerce purchase
purchase
so customers should be able to purchase
items successfully this is end-to-end
scenario but in this particular case
there are a lot of functionalities
involved okay so what all
is involved you need to have a
registered customer
right so in this particular case if i
talk about the
test cases that will be there within
this particular scenario
so there will be test case for register
so there will be
test case for register that you will add then
then
you will have login with registered user right
right
then add items then
payment and
then confirmation right so just
high level now these are high level
functionalities that will be required to
fulfill this particular scenario
and if i'm going to have the test cases
that will cover this particular
scenario we'll have test cases for
registration login add items
proceed to checkout payment and
confirmation right so all those test
test cases
sequentially combined will be
required to cover this particular
scenario okay
so a scenario can have just one test case
case
in it or a scenario can have multiple or
combination of test case
to cover that particular scenario in
software testing so that is a very
important concept
that you need to cover uh you need to understand
understand
practically right so that is why i'm
trying to cover all this software
testing concept
with the practical approach so that you
know you understand what is scenario you
understand what is test case and
for a particular scenario there could be
you know like one test case or there
could be multiple test cases to
achieve that particular test scenario but
but
the key thing is you have the requirement
requirement
from the requirement you have the scenarios
scenarios
and based on the scenarios you write the
test cases
and also you write
or if there is end-to-end scenario you
basically write
multiple test cases to fulfill that
end-to-end scenario
all right or in this particular case you
would have already written
the test cases you just have to you know
pull the existing test case
to make sure that this particular
scenario has been
successfully tested all right or
whosoever is going to test this
particular scenario
knows the step that he has to follow to
successfully test this particular
scenario all right so that's the
difference between test scenario and
test case
how the test scenario and test case are related
related
and how you come up with the test
scenario from the test scenario how to
derive the test cases
so those are some of the key concept
around test scenario
and test case in software testing so
that's all for this tutorial hope it was helpful
helpful
please do share and subscribe and thank
Click on any text or timestamp to jump to that moment in the video
Share:
Most transcripts ready in under 5 seconds
One-Click Copy125+ LanguagesSearch ContentJump to Timestamps
Paste YouTube URL
Enter any YouTube video link to get the full transcript
Transcript Extraction Form
Most transcripts ready in under 5 seconds
Get Our Chrome Extension
Get transcripts instantly without leaving YouTube. Install our Chrome extension for one-click access to any video's transcript directly on the watch page.
