modal-121 / 04 - Practical Testing Process When Tester find a Bug and do Bug Reporting /001 What Tester has to do in case heshe find bug_en.srt
| 1 | |
| 00:00:00,000 --> 00:00:08,000 | |
| Welcome to the testing world in this session, I'll show you what Bester will have to do in case when | |
| 2 | |
| 00:00:08,000 --> 00:00:10,000 | |
| he or she find a book. | |
| 3 | |
| 00:00:11,000 --> 00:00:12,000 | |
| OK, what does it mean? | |
| 4 | |
| 00:00:13,000 --> 00:00:19,000 | |
| It means when we are doing software testing and while doing testing, if I find a book, what will be | |
| 5 | |
| 00:00:19,000 --> 00:00:20,000 | |
| the next process? | |
| 6 | |
| 00:00:21,000 --> 00:00:24,000 | |
| OK, so let's take an example. | |
| 7 | |
| 00:00:24,000 --> 00:00:29,000 | |
| Previously, I've shown you that I have SARS means that if you have some requirements. | |
| 8 | |
| 00:00:30,000 --> 00:00:32,000 | |
| So let me go and check that requirement. | |
| 9 | |
| 00:00:32,000 --> 00:00:33,000 | |
| OK? | |
| 10 | |
| 00:00:33,000 --> 00:00:40,000 | |
| There is a requirement like user can search item by the name only, not by the partial name. | |
| 11 | |
| 00:00:40,000 --> 00:00:41,000 | |
| OK. | |
| 12 | |
| 00:00:41,000 --> 00:00:42,000 | |
| I have already shown you. | |
| 13 | |
| 00:00:43,000 --> 00:00:48,000 | |
| Let me move to my application and I'm doing the testing of that. | |
| 14 | |
| 00:00:48,000 --> 00:00:55,000 | |
| Like if users search by the complete name, it should give the output. | |
| 15 | |
| 00:00:56,000 --> 00:00:57,000 | |
| OK, you are getting the result. | |
| 16 | |
| 00:00:58,000 --> 00:01:07,000 | |
| But as per the requirement, if user search by partial name, it should not be such a key for testing | |
| 17 | |
| 00:01:07,000 --> 00:01:14,000 | |
| that I'm just going to the application again and I'm putting partial name like IP Edge, I'm searching | |
| 18 | |
| 00:01:14,000 --> 00:01:14,000 | |
| again. | |
| 19 | |
| 00:01:15,000 --> 00:01:17,000 | |
| Here it is still searching. | |
| 20 | |
| 00:01:17,000 --> 00:01:24,000 | |
| So if you see as per the requirement, it should not search, but actually it is searching. | |
| 21 | |
| 00:01:24,000 --> 00:01:31,000 | |
| So the expected result was in case with a partial input it should not search, but in actual results | |
| 22 | |
| 00:01:32,000 --> 00:01:38,000 | |
| it is working means actual and expected are not matching and we have seen previously if actual results | |
| 23 | |
| 00:01:38,000 --> 00:01:40,000 | |
| is not equal to the X Factor result that is called book. | |
| 24 | |
| 00:01:41,000 --> 00:01:50,000 | |
| Now the point is what do we need to do when we find a bug in the application so that we need to understand | |
| 25 | |
| 00:01:50,000 --> 00:01:51,000 | |
| in the current video? | |
| 26 | |
| 00:01:51,000 --> 00:01:52,000 | |
| So what? | |
| 27 | |
| 00:01:52,000 --> 00:01:58,000 | |
| As a tester, we will do in case we find a bug in the application? | |
| 28 | |
| 00:01:59,000 --> 00:02:04,000 | |
| So first of all, whenever you find a bug in the application, we will try to replicate by using the | |
| 29 | |
| 00:02:04,000 --> 00:02:05,000 | |
| same steps. | |
| 30 | |
| 00:02:05,000 --> 00:02:06,000 | |
| OK? | |
| 31 | |
| 00:02:06,000 --> 00:02:11,000 | |
| Sometimes when we are doing testing, we find a bug, but it always a good practice. | |
| 32 | |
| 00:02:11,000 --> 00:02:17,000 | |
| Whenever you find a bug, try to replicate it one more time by following the same steps. | |
| 33 | |
| 00:02:17,000 --> 00:02:24,000 | |
| So my step was I was going to the main page or two homepage putting partial data in the search box, | |
| 34 | |
| 00:02:24,000 --> 00:02:25,000 | |
| then click it. | |
| 35 | |
| 00:02:26,000 --> 00:02:28,000 | |
| And still, yes, I'm getting the bug. | |
| 36 | |
| 00:02:28,000 --> 00:02:32,000 | |
| So always, it's a good practice whenever you find a bug. | |
| 37 | |
| 00:02:32,000 --> 00:02:34,000 | |
| Just confirm it one more time. | |
| 38 | |
| 00:02:35,000 --> 00:02:39,000 | |
| So once you find a bug, try to replicate by using same steps. | |
| 39 | |
| 00:02:39,000 --> 00:02:43,000 | |
| If you replicate it successfully, what do we have to do now? | |
| 40 | |
| 00:02:43,000 --> 00:02:49,000 | |
| Once we replicate and the book is replicated successfully now, we will do bug reporting. | |
| 41 | |
| 00:02:49,000 --> 00:02:52,000 | |
| For that, we are going to use bug reporting tool. | |
| 42 | |
| 00:02:52,000 --> 00:02:55,000 | |
| So later on, I show you, what do you mean by the bug reporting tool? | |
| 43 | |
| 00:02:55,000 --> 00:02:57,000 | |
| So it's nothing but a software there. | |
| 44 | |
| 00:02:57,000 --> 00:03:03,000 | |
| We can put information about the bug, know whenever we are going for the bug reporting software. | |
| 45 | |
| 00:03:04,000 --> 00:03:06,000 | |
| I'm just telling you the standard process. | |
| 46 | |
| 00:03:06,000 --> 00:03:09,000 | |
| We are not directly filling the information of the code. | |
| 47 | |
| 00:03:09,000 --> 00:03:14,000 | |
| First of all, we check might be a 30 member already reported that bug. | |
| 48 | |
| 00:03:15,000 --> 00:03:17,000 | |
| So we're checking it over there. | |
| 49 | |
| 00:03:17,000 --> 00:03:23,000 | |
| If Bug is already in the system by searching it, but I'm taking example. | |
| 50 | |
| 00:03:23,000 --> 00:03:24,000 | |
| No, nobody reported this bug. | |
| 51 | |
| 00:03:25,000 --> 00:03:27,000 | |
| I'm the first person who is going to report this book. | |
| 52 | |
| 00:03:28,000 --> 00:03:31,000 | |
| So if no, we have to report a new bill into the system. | |
| 53 | |
| 00:03:32,000 --> 00:03:36,000 | |
| So I'll show you how we can report people did. | |
| 54 | |
| 00:03:36,000 --> 00:03:44,000 | |
| Are many bug reporting software available in the market might be you have heard about the Bug Jila JIRA | |
| 55 | |
| 00:03:44,000 --> 00:03:45,000 | |
| vendors. | |
| 56 | |
| 00:03:45,000 --> 00:03:46,000 | |
| So we have many softwares. | |
| 57 | |
| 00:03:47,000 --> 00:03:49,000 | |
| One of the most popular software is JIRA. | |
| 58 | |
| 00:03:50,000 --> 00:03:54,000 | |
| So next session, I'll show you how we can set up JIRA for this purpose. | |
| 59 | |
| 00:03:55,000 --> 00:03:58,000 | |
| And then I'll show you how we can report Bug into the Giro gyro. | |
| 60 | |
| 00:03:59,000 --> 00:04:05,000 | |
| Just to summarize over here, whenever you are testing and you find a bug first step, we will try to | |
| 61 | |
| 00:04:05,000 --> 00:04:07,000 | |
| replicate that by using the same ESTEP. | |
| 62 | |
| 00:04:07,000 --> 00:04:08,000 | |
| Yes. | |
| 63 | |
| 00:04:08,000 --> 00:04:09,000 | |
| Still, we are getting that book. | |
| 64 | |
| 00:04:10,000 --> 00:04:15,000 | |
| Now I'll go to the software, which is our bug reporting software, and then I will check. | |
| 65 | |
| 00:04:16,000 --> 00:04:20,000 | |
| Does anybody else previously put this bug into the software? | |
| 66 | |
| 00:04:21,000 --> 00:04:23,000 | |
| If answer is no, no, it's not there. | |
| 67 | |
| 00:04:23,000 --> 00:04:27,000 | |
| Then we'll have to report Bug for reporting we can use different software. | |
| 68 | |
| 00:04:27,000 --> 00:04:32,000 | |
| Just remember these names like Bajela, JIRA or BSD or many others. | |
| 69 | |
| 00:04:32,000 --> 00:04:38,000 | |
| We are going to use JIRA, as I told you in the next session, I'll show you how we can set up JIRA | |
| 70 | |
| 00:04:38,000 --> 00:04:40,000 | |
| so that you can practice on that. | |
| 71 | |
| 00:04:40,000 --> 00:04:44,000 | |
| And after that, I'll show you how we can report bug in that. | |
| 72 | |
| 00:04:45,000 --> 00:04:46,000 | |
| That's all we have for the session. | |
| 73 | |
| 00:04:47,000 --> 00:04:48,000 | |
| Thanks for watching this video. | |