Add Bug Report Digital Signature with airSlate SignNow

Signature bug report

hi friends this is suma from software testing material comm in this video we are going to see how to write a good buck report let's see the following in detail what is a bug report what is a bad bug report what is a good bug report how to write a good bug report bug report checklist first let's see what is a bug report bug report is also known as defect report it can list the detailed information about the bug to the developers it allows developers to replicate the bug easily it is one of the test artifacts earlier we have made a video on test artifacts check out our video on test deliverables to know more on the list of test artifacts in software testing with detailed explanation next what is a bad bug report have you ever seen a rejected bug with comments it is not reproducible sometimes development team rejects a few bugs due to bad bug report imagine you are using Mozilla Firefox for testing you found an issue that log in button is not working you have posted the same issue with all the steps except mentioning the name and version of the browser you one of the developers open that report and try to reproduce it based on the steps you mentioned in the report here in this case the developer is using Internet Explorer the login button is working properly in their enrollment so the developer will reset the bug by mentioning the comments as the bug is not reproducible you will find the same issue of that Udo retest again you will report the same issue and get the same comments from the development team you forgot to mention the name and version of browser in your bug report if you forgot some key information to reproduce the bug in the developers environment you will face the consequences it creates a bad impression on you action will be taken on you based on the company for wasting the time and effort there is an old saying you never get a second chance to make a first impression what is a good buck report writing good bug report is a skill every tester should have you have to give all necessary details to the development team to get your issue fixed do you want to get the bug fixed the total section so you have to report it by using a good bug report how to write good bug report let's see each and every field of a bug report in detail defect report template or bug report template comes into picture then the test execution phase is started defect ID added effect ID using a naming convention followed by your team the defect ID will be generated automatically in case of defect management tool title or summary title should be short and simple it should contain specific terms related to the actual issue be specific while writing the title assume you have found a bug in the registration page while uploading a profile picture that to a particular file format system is crashing while uploading a jpg file please note that I am going to use this example throughout the video good way of writing it uploading a jpg file in the registration page crashes the system bad way of writing it system crashes reporter name name of the one who found the defect usually distressed name but sometimes it might be developer business and list subject matter expert customer defect reported date mention the date on which you have found the bug who detected specify the designation of the one who found the defect example QA developer business analyst SME and customer how detected in this field you must specify on how you have detected such as while doing testing or while doing review or while giving walkthrough etc project name sometimes we may work on multiple project simultaneously so choose the project name correctly specify the name of the project release or build version on which release this issue occurs mention the build version details clearly defect or enhancement if the system is not behaving as intended then you need to specify it as a defect if it's just a request for a new feature then you must specify it as enhancement environment you must mention the details of operation systems browser details and any other related to the test environment in which you have encountered the bug example Windows 8 chrome 48 priority priority defines how soon the bug should be fixed usually the priority of the bug is said by the managers based on the priority developers could understand how soon it must be fixed and said the order in which a bug should be resolved categories of priority high medium low severity severe t talks about the impact of the bug on the customers business usually the severity of the bug is said by the managers sometimes testers choose the severity of the bug but in most cases it will be selected by managers or leads categories of severity blocker critical major/minor and trivial status specify the status of the bug if you just found a bug and about to post it then the status will be new in the course of bug fixing the status of the bug will change example new assigned open fixed test verified closed reopen duplicate deferred rejected cannot be fixed not reproducible need more information description in the description section you must briefly explain what you have done before facing the bug steps to reproduce in this section you should describe how to reproduce the bug in step-by-step manner easy-to-follow steps give room to the developers to fix the issue without any chaos these steps should describe the bug well enough and allows developers to understand and act on the bug without discussing to the one who wrote the bug report start with opening the application include prerequisites if any and right till the step which causes the bug good way of writing it open URL click on registration page upload jpg file in the profile photo field bad way of writing it upload a file in the registration page URL mention the URL of the application expected result what is the expected output from the application when you make an action which causes failure good way of writing it a message should display profile picture uploaded successfully bad way of writing it system should accept the profile picture actual result what is the expected output from the application when you make an action which causes failure good way of writing it uploading a jpg file in the registration page crashes the system bad way of writing it system is not accepting profile picture attachments attach the screenshots which you had captured when you faced the bug it helps the developers to see the bug which you have faced defect closed date the defect closed date is the date which needs to be updated once you ensure that the defect is not reproducible key points to keep in mind by writing a good bug report the first thing we should do before writing a bug report is to reproduce the book two or three times if you are sure that bug exists then as a time whether the same bug was posted by someone else or not use some keywords related to your bug and search in the defect tracking tool if you did not find an issue which is related to the bug same like you found then you could start writing a bug but hold on why could not we ascertain whether the same issue is available in the related modules if you find that the same issue is available in the later modules then you could address those issues in the same bug report it saves a lot of time in terms of fixing the issues and writing repeated bug reports for the same kind of issues start writing a bug report by mentioning all the details in the fields as I said earlier and write detailed steps to reproduce make a checklist and ensure whether you have passed all the points before reporting a bug have I reproduced the burgh two to three times have a verified in the defect tracking tool whether someone else already posted the same issue have a verified the similar issue in the related modules have a written the detailed steps to reproduce the bug have a written proper defect summary have a attached relevant screenshots have a missed any necessary fields in the bug report consolidating all the points on how to write good bug report reproduce the bug two to three times use some keywords related to your book and search in the defect tracking tool check in similar modules report the problem immediately write detailed steps to reproduce the bug try to good defect summary watch your language in the process of writing the bug report your words should not often people never use capital letter vilest explaining the issue advisable to illustrate the issue by using proper screenshots proofread your bug report twice or Trice before posting it earlier we have made a video on how to write test cases check that video to learn writing the test cases manually time's French if you have any queries please comment below if you did enjoy this video be sure to like the video don't forget to subscribe this channel by clicking the subscribe button I'll see you soon in the next video thank you have a good day you