Software Testing Project - HRMS Report

Till now we saw how we tested a live website or live application. We saw its employee registration form and saw where all the issues come from. We saw these things. Now what will we do? Now we will make a defect report. Most of the companies have a tracking tool to make the defect reports. such as Bugzilla or Mentis. Suppose you go to a company where there is no tracking tool but you want to make a bug report. So, how will you do that? Bug report will be made in what? In excel. Okay. Now, let's see how we will make the bug report in excel. Suppose you have to send the bug report to a client. So, what will we do here? Name of the company. What will come first is the name of the company. After that there will come its URL. After that we will write columns here. 1^st of all, what will come? Defect ID, as it is a unique identification number of the defect. After that what will come, defect description, after that comes, defect steps to reproduce. Right? Steps to reproduce means that the client that you are giving it to, he should know the steps, in which way he will reproduce the particular bugs. Those steps will come in steps to reproduce. After that will come severity, priority, status, created by, assigned to, whom have we assigned, to the developer or the team lead and screen shot. Screenshot is an important thing in bug reporting. If the screenshot is not there then the QA will not be able to prove where and how the actual bug is coming and how it is looking. So guys, screenshot is important in bug reporting. Now, you will think, what is priority and severity? Okay, no problem, I will explain priority and severity here. Pay attention. First of all, let’s talk about priority. You must have heard that this work is on priority. Priority means what is the priority of that particular defect. Does it need to be solved quickly or if it is late, it will be okay or if it can be comfortably done. Understood. We can see the priority in 3 categories, 1^st is low, medium and high. The kind of defect and its impact on the system, according to that, you will give that defect low, medium or high priority. Okay. Now we will talk about severity. Severity means if this is a bug what is the impact it has on the system. How severe is that bug? Severity is also divided in 4 categories. 1^st will come critical, then will come major, after that medium and low.okay! giving you 2 to 3 examples so, You will understand. Imagine that you are nor able to login in any system. As soon as I click the login button, the system crashes. Are you able to enter the system, is the other testing happening? No, so what will be its severity, critical. And what will be its priority? High. Right? Now, major ! What happens in major is I am not able to login to the system. The basic functionality of the system, like to create employee. The Create employee is not working but the rest of the system is working. So, that priority will be also high but its severity will be major. Why? Because that is the main, that is the base of our system. If he is not able to create the employee, how will he use the further system? Right? Let’s talk about mediums. The date of birth will come in medium. Why? System is working, employees are getting created but the only thing is that we cannot insert a date of birth feature, so we are making it a defect and that severity will be medium. Low, low means anu UI issues. I will give you a live example of low, you have a look. See, this logo that is there is cut into half. This logo is halfcut, you are not able to see it, N and Y are cut. This is known as the UI issue. Its priority will be low and the severity will be? speak? Tell me? Severity will also be low. Because, is it affecting the system?  Is any of my functionality getting affected? No. Right? Come now we will make a defect of the Birthday field issue that was there, that one. I have made it beforehand, we will go through it. Like I have written in defect description, employee registration form, birthdate, except future date. The form is accepting the future date. Which steps we will write, the same ones that we have written in the test case. Like how we are going till that particular field. And we will give an example here, like If we insert this date.  What should be the expected result? Users should get a prompt here that the future birthdays should be given or calendars should block future dates. It means that for the future birthdates, the user is not able to enter, for that block the calendar, after the current date. Then we will go on severity, what will be its severity? It will be medium, what we talked about. Priority will be major. Why? because suppose, by mistake I inserted the birthdate forth and back. Instead of 2014 if the calendar inserts 2018’s at the time of registration. Status will remain open. Created by QAT members and assigned to QA lead and screenshot is the very important part of bug report. Like I said earlier, Screenshot is very important for bug reports. Till now you must have understood how to make the test case, how to make the defect report. What is the important role of severity and priority in defect reports?