0:02 hello everyone welcome again in the
0:04 software testing tutorial
0:07 we are going to understand difference
0:09 between test scenario and test case
0:13 now this is very important to understand
0:15 the difference between test scenario and
0:17 test case because both of them go hand
0:18 in hand
0:20 and you will be work whenever you are
0:22 working in any software testing project
0:25 you will be using them a lot and this
0:28 helps this these you know two concepts
0:29 test cases we have already understood
0:31 what exactly test case is
0:33 but test scenario you will listen you
0:34 know a lot
0:36 for example write the test scenario and
0:38 then test case so basically you need to
0:41 understand what exactly is test scenario
0:43 how it is related to test case how is it
0:44 different to test case
0:48 and how you apply practically these two things
0:49 things
0:50 in any software testing project all
0:53 right so let's first understand
0:55 the differences between test scenario
0:56 and test case
0:58 because once you know the differences
0:59 you will understand where
1:02 to apply which one and how both of them
1:04 are correlated all right
1:07 so if we talk about test scenario so
1:08 test scenario
1:11 is very high level okay so test scenario is
1:12 is
1:15 high level uh documentation of
1:17 basically what you are going to test in
1:18 application okay so
1:20 say for example i take an example of
1:21 e-commerce website
1:23 now e-commerce website has registration
1:26 functionality has login functionality
1:27 check out so there are a lot of
1:29 functionalities right now
1:31 if in your application you have one
1:33 particular functionality say for example
1:36 i'll take a login functionality okay so
1:36 i'll say
1:40 login functionality now
1:47 if we talk about the test scenario for
1:48 this particular functionality so test
1:51 scenario will be very high level
1:55 one liner you know scenario description
1:58 of what you are going to test in the
2:00 login functionality okay so for example
2:03 in the login functionality i want to
2:07 uh you know test login
2:14 user and password
2:19 okay then with invalid
2:23 user and password okay another scenario
2:26 then valid user
2:30 invalid password okay so these are just
2:35 one liner descriptions of what all
2:37 scenarios i'm going to cover as part of
2:39 the login functionality
2:42 right so one liners so when we write
2:45 high-level one-liner description of any
2:46 functionality or
2:48 what we are going to test in the
2:50 application that is
2:53 test scenario okay
2:56 now when we talk about the test case to
2:58 write a test case we refer back to the scenarios
2:59 scenarios
3:02 okay and test case is more detailed
3:04 description of
3:06 what you are going to test right so here
3:07 we are understanding
3:10 what we are going to test now when we convert
3:11 convert
3:12 these scenarios so basically we will use
3:14 these scenarios so
3:16 with valid username and password right
3:17 so this is one of the scenario
3:19 that we are going to test in the login
3:21 functionality now when we write the test
3:22 case for it
3:26 we describe or we describe the steps or
3:28 we elaborate
3:31 and we elaborate that how you are going
3:32 to test this
3:34 okay so in the test case what you will
3:36 do is you will write
3:39 the steps one two three four
3:46 the e-commerce portal in particular
3:48 browser okay
3:51 step two click on login link
3:54 step three enter a valid user and valid password
3:56 password
3:59 step four click on login button right
4:02 so these this elaboration that you do
4:04 for a particular scenario
4:07 becomes the test case okay
4:09 so this is a brief difference between
4:11 the test scenario and test case so test
4:12 scenario is
4:17 high level one liner and explains
4:20 what all you are going to test okay test case
4:20 case
4:23 along with what you are going to test it
4:24 also describes
4:26 how you are going to test it describes
4:27 the steps
4:30 of a particular scenario all right
4:34 now when we talk about the scenarios
4:35 so test scenarios mostly you will be
4:37 deriving from
4:39 requirement documents okay so
4:40 requirement documents
4:42 for example software requirement specification
4:44 specification
4:47 and user stories okay user stories or
4:50 any documents that are available which
4:52 will help you to come up with these
4:54 scenarios okay so because requirements
4:56 will have the detailed requirement of
4:58 login and in login functionality what
5:01 all requirements are being described for
5:03 the login functionality so
5:04 with seeing the requirements you can
5:07 easily come up with one liner
5:09 test scenario so you the baseline or
5:10 basically the basis
5:13 for writing the test scenarios is your
5:15 user stories your requirement
5:18 okay but in terms of test case
5:20 how you write the test case you
5:22 basically you then
5:24 derive your test case based on the
5:27 scenarios that you have written so
5:29 based on the srs you have written all these
5:31 these
5:33 scenarios right and then you refer to
5:34 these scenarios and you write the test
5:36 case for each of these
5:38 scenarios okay so that is the difference
5:41 between test scenario and test case
5:42 and how they are correlated so you have
5:45 the requirement from the requirements
5:46 from the user stories you come up with
5:48 the test scenarios
5:50 test scenarios are nothing but high
5:52 level liner
5:55 description of what all you are going to
5:57 test in that particular functionality
6:00 test case is more detailed description of
6:01 of
6:02 those scenarios so test cases are
6:04 derived from the
6:06 scenarios okay so requirement scenarios
6:07 and test case
6:09 so that's the hierarchy okay so you have
6:11 requirement from requirement you
6:14 come up with the scenarios and
6:17 from scenarios you write the test cases
6:18 you elaborate those
6:21 okay so this is how you actually do in
6:22 the practical
6:25 testing okay this is the flow you follow
6:26 in the any of the practical
6:28 testing approach because if you directly start
6:29 start
6:32 writing your test cases describing
6:34 detailing from the requirement it
6:37 most of the time you will miss couple of
6:38 steps so
6:41 this step is very important because you
6:43 apply your thought process you apply the
6:46 tester's mindset to basically
6:48 see what all combination what all
6:50 scenarios can be tested for that
6:51 particular feature
6:54 so you write all the positive negative
6:55 scenarios just
6:57 one liner quick one and then based on one-liner
6:58 one-liner
7:00 scenarios you convert those to test
7:02 cases which becomes really easy
7:05 okay so that is the difference between
7:07 the test scenario and test case
7:10 how they are related uh among each other
7:13 okay now next
7:17 is i'll explain one of the example
7:19 okay so let me take an e-commerce
7:21 website example
7:24 and i'll take a functionality
7:28 of registration okay
7:30 and let me write some of the scenarios
7:31 for this registration
7:33 and the test cases for that now
7:35 registration is one of the functionality which
7:36 which
7:38 will be described into the software
7:40 requirements or the user stories for
7:41 registration okay
7:44 so based on the user stories what i'll
7:44 do is
7:48 i'll start writing the scenarios
7:50 okay so first scenario that you can
7:51 think of
8:03 then register
8:06 with google
8:08 right so this is just one line i am
8:09 quickly writing okay
8:11 positive scenario so whatever
8:13 registration functionality supports
8:16 so say for example it also supports fbs
8:17 or also supports
8:19 registration using twitter account so
8:21 i'll write these four
8:25 scenarios okay fifth scenario
8:27 will will cover some of the negative
8:28 scenarios right so
8:32 um verify you know registration is not
8:32 successful with
8:41 registration fails
8:43 okay another scenario so negative scenario
8:45 scenario
8:48 so this is how you will keep extending or
8:48 or
8:51 thinking about how or what all
8:53 scenarios could be possible for this
8:55 particular functionality
8:57 right now your requirement document will
8:58 explain all
8:59 these things within the requirement
9:00 document and you will go through the
9:02 requirement document
9:04 understand those if there are in doubt
9:06 you will go back to the business analyst
9:08 and understand the gaps or
9:11 if there is any you know things that are
9:12 missing in the requirement you
9:13 understand those gaps
9:16 and keep extending these scenarios so
9:18 these are one-liner high-level scenarios
9:21 written once you have these scenarios written
9:22 written
9:26 then the next step is as a test engineer
9:28 i'll pick the scenario and then i'll convert
9:29 convert
9:33 this into the test case right
9:36 a scenario can be can have just one test case
9:37 case
9:40 for it or there could be a scenario
9:42 which is a combination of multiple test cases
9:42 cases
9:45 okay say for example a scenario at this
9:46 particular level
9:47 is specific to registration
9:50 functionality but
9:52 a scenario for end-to-end scenario or
9:53 end-to-end testing
9:57 could be a combination of registration
10:00 login you know adding items to cart so
10:02 in that particular case you write
10:06 one-liner scenario say for example
10:08 successful checkout or successful
10:12 purchase say for example right if i say
10:13 another scenario which is end-to-end
10:15 scenario of e-commerce website
10:19 so customer
10:33 items successfully
10:36 right so one liner
10:39 scenario okay foreign e-commerce purchase
10:40 purchase
10:42 so customers should be able to purchase
10:44 items successfully this is end-to-end
10:46 scenario but in this particular case
10:47 there are a lot of functionalities
10:50 involved okay so what all
10:53 is involved you need to have a
10:54 registered customer
10:56 right so in this particular case if i
10:57 talk about the
10:59 test cases that will be there within
11:01 this particular scenario
11:03 so there will be test case for register
11:04 so there will be
11:07 test case for register that you will add then
11:08 then
11:10 you will have login with registered user right
11:11 right
11:15 then add items then
11:22 payment and
11:25 then confirmation right so just
11:28 high level now these are high level
11:30 functionalities that will be required to
11:32 fulfill this particular scenario
11:36 and if i'm going to have the test cases
11:37 that will cover this particular
11:39 scenario we'll have test cases for
11:41 registration login add items
11:42 proceed to checkout payment and
11:44 confirmation right so all those test
11:45 test cases
11:49 sequentially combined will be
11:51 required to cover this particular
11:52 scenario okay
11:55 so a scenario can have just one test case
11:55 case
11:58 in it or a scenario can have multiple or
12:00 combination of test case
12:02 to cover that particular scenario in
12:04 software testing so that is a very
12:05 important concept
12:08 that you need to cover uh you need to understand
12:08 understand
12:10 practically right so that is why i'm
12:12 trying to cover all this software
12:13 testing concept
12:15 with the practical approach so that you
12:17 know you understand what is scenario you
12:19 understand what is test case and
12:21 for a particular scenario there could be
12:22 you know like one test case or there
12:24 could be multiple test cases to
12:27 achieve that particular test scenario but
12:28 but
12:30 the key thing is you have the requirement
12:31 requirement
12:33 from the requirement you have the scenarios
12:34 scenarios
12:36 and based on the scenarios you write the
12:38 test cases
12:42 and also you write
12:44 or if there is end-to-end scenario you
12:45 basically write
12:47 multiple test cases to fulfill that
12:49 end-to-end scenario
12:51 all right or in this particular case you
12:53 would have already written
12:55 the test cases you just have to you know
12:57 pull the existing test case
12:59 to make sure that this particular
13:00 scenario has been
13:02 successfully tested all right or
13:04 whosoever is going to test this
13:06 particular scenario
13:08 knows the step that he has to follow to
13:10 successfully test this particular
13:12 scenario all right so that's the
13:14 difference between test scenario and
13:15 test case
13:17 how the test scenario and test case are related
13:19 related
13:21 and how you come up with the test
13:23 scenario from the test scenario how to
13:25 derive the test cases
13:27 so those are some of the key concept
13:29 around test scenario
13:31 and test case in software testing so
13:33 that's all for this tutorial hope it was helpful
13:34 helpful
13:35 please do share and subscribe and thank
