1 00:00:00,000 --> 00:00:08,000 Welcome to the testing world in this session, I'll explain you smoke testing and sanity testing, that 2 00:00:08,000 --> 00:00:10,000 is one of the most important topic. 3 00:00:11,000 --> 00:00:16,000 If you're looking for a job as a software tester or if you're working as a software tester, because 4 00:00:16,000 --> 00:00:23,000 this is the topic which will be asked in interviews as well as you will do these testing practically. 5 00:00:23,000 --> 00:00:29,000 So I'll show you what is smoke testing, what is sanity testing and what is the difference between smoke 6 00:00:29,000 --> 00:00:30,000 and sanity? 7 00:00:31,000 --> 00:00:34,000 So let's start with smoke testing. 8 00:00:34,000 --> 00:00:36,000 OK, let's take an example. 9 00:00:37,000 --> 00:00:41,000 We are working in a team and we are getting build from the development site. 10 00:00:42,000 --> 00:00:48,000 But whenever we are getting billed and we start testing on it, we saw there are some changes in the 11 00:00:48,000 --> 00:00:48,000 build. 12 00:00:49,000 --> 00:00:51,000 And because of that, most of the functionalities are not working. 13 00:00:52,000 --> 00:00:56,000 Now we'll go back to the developer will report these issues. 14 00:00:56,000 --> 00:00:58,000 They will correct it and again make it build. 15 00:00:59,000 --> 00:01:05,000 But it is taking a lot of time because every time we go to build, many functionalities are not working. 16 00:01:05,000 --> 00:01:11,000 And if they're not working, we cannot run our test kits because we will run our test cases only when 17 00:01:11,000 --> 00:01:13,000 the functional functionalities are working. 18 00:01:14,000 --> 00:01:18,000 So let's take example of this application. 19 00:01:19,000 --> 00:01:26,000 Here we have a registration page and they ask you to test registration page so you can test this registration 20 00:01:26,000 --> 00:01:32,000 with the multiple set of input data by putting the mandatory data by leaving the mandatory data. 21 00:01:32,000 --> 00:01:40,000 But if I give you a bird where this registration is not opening, or maybe that is open, but that is 22 00:01:40,000 --> 00:01:42,000 not working, if we enter the correct data, we click on it. 23 00:01:42,000 --> 00:01:44,000 So it's not working, it's not working. 24 00:01:44,000 --> 00:01:51,000 In any case, then there is no advantage of getting built because we cannot best any of the test kits 25 00:01:51,000 --> 00:01:53,000 because that functionality is not working. 26 00:01:54,000 --> 00:02:02,000 So here in that kind of scenario where we are not sure big would be stable or not, we have to perform 27 00:02:02,000 --> 00:02:03,000 smoke testing. 28 00:02:04,000 --> 00:02:08,000 So let's take this example this image whenever we are getting built. 29 00:02:09,000 --> 00:02:15,000 First of all, we are doing smoke testing if smoke testing is filled. 30 00:02:15,000 --> 00:02:17,000 We will check the build. 31 00:02:17,000 --> 00:02:19,000 We will not go for actual testing. 32 00:02:20,000 --> 00:02:22,000 So let's again come to this application. 33 00:02:23,000 --> 00:02:30,000 And if I want to go for the testing of registration page, but before doing actual testing, we are 34 00:02:30,000 --> 00:02:36,000 doing smoke testing in which we are just checking this registration functionality is working or not. 35 00:02:37,000 --> 00:02:41,000 If it is not working, we will reject the build note that it is not stable. 36 00:02:41,000 --> 00:02:42,000 Make it correct. 37 00:02:42,000 --> 00:02:44,000 Only after that, I'll do my actual testing. 38 00:02:45,000 --> 00:02:54,000 So here we can see we are testing a build to check whether the building is ready for the testing or 39 00:02:54,000 --> 00:02:54,000 not. 40 00:02:54,000 --> 00:03:00,000 So that is the aim of the smoke testing is to check whether a build is ready for the smoke, ready for 41 00:03:00,000 --> 00:03:02,000 actual testing or not. 42 00:03:02,000 --> 00:03:04,000 So here we are. 43 00:03:04,000 --> 00:03:07,000 Going to test functionalities are working or not. 44 00:03:08,000 --> 00:03:09,000 It is correctly working or not. 45 00:03:10,000 --> 00:03:12,000 That will be covered in the actual testing. 46 00:03:12,000 --> 00:03:18,000 But in smoke testing, we check whether functionalities are working. 47 00:03:19,000 --> 00:03:23,000 Only after that, we will take this build or accept this build and do actual testing. 48 00:03:24,000 --> 00:03:30,000 So as per definition of the smoke testing is to check whether the bird is ready for the testing or not. 49 00:03:30,000 --> 00:03:33,000 Yes, we already covered this in this testing. 50 00:03:33,000 --> 00:03:38,000 We try to cover all the major functionality of the application at upper level. 51 00:03:38,000 --> 00:03:39,000 OK. 52 00:03:39,000 --> 00:03:43,000 In this smoke testing, we are not going to do deep testing. 53 00:03:43,000 --> 00:03:46,000 We are just testing all the functionalities at upper level. 54 00:03:47,000 --> 00:03:48,000 Let's take an example of a G.M.. 55 00:03:49,000 --> 00:03:51,000 I wanted to smoke testing of the gym. 56 00:03:51,000 --> 00:03:57,000 I got a bird and want to do smoke testing of the G.M. So what I do, I try to log in. 57 00:03:57,000 --> 00:03:59,000 I tried to send one email. 58 00:03:59,000 --> 00:04:01,000 I try to chat with someone else. 59 00:04:02,000 --> 00:04:04,000 I try to check send items. 60 00:04:04,000 --> 00:04:06,000 I'll try to make it draft. 61 00:04:06,000 --> 00:04:14,000 So I test all major functionalities at upper level means I'm just checking that is working or not. 62 00:04:14,000 --> 00:04:18,000 It could have many test cases for each functionality, but we are not running all the test cases. 63 00:04:19,000 --> 00:04:21,000 We are just checking it's working or not. 64 00:04:22,000 --> 00:04:26,000 If it is working, but it is past now, it will go to my testing team. 65 00:04:26,000 --> 00:04:32,000 Testing team will perform actual testing, which will run hundreds of test kits. 66 00:04:33,000 --> 00:04:39,000 So in this testing, we try to cover all the major functionalities of application at upper level. 67 00:04:40,000 --> 00:04:42,000 Smoke testing is it scripted? 68 00:04:42,000 --> 00:04:45,000 Means we already have test kits for this mock testing. 69 00:04:46,000 --> 00:04:53,000 So for the application total, we have 500 test kits, but out of the 500, we pick only 22 SKUs, which 70 00:04:53,000 --> 00:04:55,000 will check application functionalities. 71 00:04:55,000 --> 00:04:58,000 Or I would say, major functionalities are working or not. 72 00:04:58,000 --> 00:05:00,000 So we already have test. 73 00:05:00,000 --> 00:05:02,000 Cases of smoke testing. 74 00:05:02,000 --> 00:05:05,000 That's why we called smoke testing a scripted. 75 00:05:05,000 --> 00:05:10,000 Now one question come who will do the smoke testing you? 76 00:05:10,000 --> 00:05:17,000 You as a tester or your test lead or anyone else actually that will be done by the testing team only. 77 00:05:17,000 --> 00:05:18,000 So let's take an example. 78 00:05:18,000 --> 00:05:19,000 I'm a lead. 79 00:05:19,000 --> 00:05:24,000 I'll pick one tester from the team and give the responsibility like you have to do smoke testing. 80 00:05:25,000 --> 00:05:31,000 So every time a bird is coming first, that particular tester will do the smoke testing in which he 81 00:05:31,000 --> 00:05:32,000 will check. 82 00:05:33,000 --> 00:05:35,000 All major functionalities are working or not. 83 00:05:35,000 --> 00:05:38,000 If it does not, he will reject the bird else. 84 00:05:38,000 --> 00:05:40,000 He will accept the bill. 85 00:05:40,000 --> 00:05:47,000 Now, the rest of the team will start doing its testing so I can see Smoke Tester will work over here 86 00:05:47,000 --> 00:05:50,000 and complete the well will work over here. 87 00:05:51,000 --> 00:05:55,000 So once the smoke testing is passed, only completed will work on a particular build. 88 00:05:57,000 --> 00:06:04,000 This type of testing is mainly done when the initial builds because initial builds are a bit unstable, 89 00:06:04,000 --> 00:06:06,000 so we want to check the stability of the build. 90 00:06:06,000 --> 00:06:08,000 Only after that will do testing. 91 00:06:08,000 --> 00:06:09,000 That is. 92 00:06:09,000 --> 00:06:12,000 We do smoke testing with the initial build. 93 00:06:14,000 --> 00:06:19,000 Now I'll come to the Senate digesting insanity testing. 94 00:06:19,000 --> 00:06:24,000 We try to cover one or two functionality at deep level. 95 00:06:26,000 --> 00:06:32,000 So let's take an example I have a build in which in one functionality developer me made changes, and 96 00:06:33,000 --> 00:06:40,000 I just want to make sure after the changes, this particular module, particular functionality is working 97 00:06:40,000 --> 00:06:41,000 correctly or not. 98 00:06:42,000 --> 00:06:45,000 So I'll go with the sanity testing, insanity testing. 99 00:06:45,000 --> 00:06:51,000 We try to cover one or two functionalities only, but deep level what detailed testing we can do, we 100 00:06:51,000 --> 00:06:54,000 will do here in the test, in sanity testing. 101 00:06:56,000 --> 00:07:00,000 Sanity testing is not scripted, it is it I just updated that. 102 00:07:01,000 --> 00:07:07,000 It's a sanity testing is not scripted, not scripted means we are not having any test cases. 103 00:07:07,000 --> 00:07:14,000 So let's take an example we are working on the G.M. There are some changes taking place in compose email 104 00:07:14,000 --> 00:07:14,000 functionality. 105 00:07:15,000 --> 00:07:20,000 I have given the task to my team only just compose email at deep level. 106 00:07:20,000 --> 00:07:25,000 Deep level means whatever you can test, just tested in the particular functionality only. 107 00:07:26,000 --> 00:07:28,000 But if you understand regression, it's all the same. 108 00:07:28,000 --> 00:07:32,000 Yes, but integration, we are going for the complete application here. 109 00:07:32,000 --> 00:07:37,000 Insanity, we are going for a particular module or particular functionality. 110 00:07:37,000 --> 00:07:43,000 Also, integration, we are falling test cases, but sanity testing is not a scripted means. 111 00:07:44,000 --> 00:07:46,000 We are not following any discuses. 112 00:07:47,000 --> 00:07:51,000 This type of testing is mainly done when bills are stable. 113 00:07:52,000 --> 00:07:54,000 So let's take an example. 114 00:07:54,000 --> 00:08:01,000 I have 120 build and one point two zero build, so I know that that build is stable. 115 00:08:01,000 --> 00:08:05,000 After the changes, there is a very less chance it will impact the other part. 116 00:08:06,000 --> 00:08:11,000 So I just wanted to check only a particular module, and I want to check it quickly so I will not go 117 00:08:11,000 --> 00:08:12,000 for the test cases. 118 00:08:12,000 --> 00:08:14,000 I just give it like, okay, due to sanity. 119 00:08:15,000 --> 00:08:20,000 Insanity will try to cover what a deep level will try to test this functionality at a deep level, but 120 00:08:20,000 --> 00:08:22,000 I do not follow any test cases. 121 00:08:25,000 --> 00:08:31,000 So here you can check verify this small section of the functionality is working or not after a make 122 00:08:31,000 --> 00:08:32,000 or break fix. 123 00:08:32,000 --> 00:08:40,000 So once it is passed now, my belt is passed to protesters to do complete detailed testing. 124 00:08:43,000 --> 00:08:45,000 Now, what is the difference between the smoke and sanity? 125 00:08:46,000 --> 00:08:51,000 So smoke testing aim is check, but it is ready for the testing or not. 126 00:08:52,000 --> 00:08:58,000 Incentive to distinguish check functionality is stable after the changes or not, because here I am 127 00:08:58,000 --> 00:09:04,000 taking example some changes taking place on a particular functionality and I want to check after the 128 00:09:04,000 --> 00:09:04,000 changes. 129 00:09:05,000 --> 00:09:10,000 Still, that functionality is up and running, so I want to check it in the detail level. 130 00:09:11,000 --> 00:09:16,000 In smoke testing, we try to cover all the major functionalities, but upper level. 131 00:09:17,000 --> 00:09:19,000 So we check all the functionalities are working or not. 132 00:09:20,000 --> 00:09:23,000 But we are not going to the details of that here. 133 00:09:23,000 --> 00:09:30,000 We will check only one or fewer functionalities, but in deep level, smoke is scripted means we have 134 00:09:30,000 --> 00:09:32,000 the discuses sanity is not scripted. 135 00:09:32,000 --> 00:09:34,000 We do not have the discs. 136 00:09:35,000 --> 00:09:41,000 Normally we do smoke testing when Burt is unstable, so we will do smoke testing in that case. 137 00:09:41,000 --> 00:09:48,000 Normally, we don't sanity when the bird is stable, only changes taking place in one or a few functionalities. 138 00:09:50,000 --> 00:09:54,000 So here we have seen what is smoke testing, what is sanity testing? 139 00:09:54,000 --> 00:10:00,000 You can take it as as a prerequisite before going for actual testing. 140 00:10:00,000 --> 00:10:04,000 So if it is unstable, we can do smoke testing to check. 141 00:10:04,000 --> 00:10:10,000 But it is ready for the testing or not if Bert is stable, but changes taking place in one module. 142 00:10:10,000 --> 00:10:17,000 And I want to make sure that module is correctly working before rolling for the actual testing, actual 143 00:10:17,000 --> 00:10:17,000 detailed testing. 144 00:10:18,000 --> 00:10:19,000 We will do sensory testing. 145 00:10:21,000 --> 00:10:22,000 That's all for this edition. 146 00:10:23,000 --> 00:10:24,000 Thanks for watching this video.