{"id":31675,"date":"2016-01-21T17:34:41","date_gmt":"2016-01-21T12:04:41","guid":{"rendered":"http:\/\/www.tothenew.com\/blog\/?p=31675"},"modified":"2016-01-27T11:21:08","modified_gmt":"2016-01-27T05:51:08","slug":"effective-techniques-for-bug-reporting-and-bug-tracking","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/effective-techniques-for-bug-reporting-and-bug-tracking\/","title":{"rendered":"Effective techniques for Bug Reporting and Bug Tracking"},"content":{"rendered":"<h1><strong>Bug Reporting<\/strong><\/h1>\n<p>Bug Reporting is the activity of posting a bug to the development team to fix it. Bug reporting in <a title=\"Independent Software Testing Services\" href=\"http:\/\/www.tothenew.com\/testing\/automated-independent-manual-testing\">independent software testing<\/a> can be done using a simple spread sheet or using a bug tracking tool. While reporting a bug don\u2019t forget to fill up following fields &#8211;<\/p>\n<ul>\n<ul>\n<li>Bug ID (Auto generated in case of tool)<\/li>\n<li>Project Name<\/li>\n<li>Bug Summary<\/li>\n<li>Description<\/li>\n<\/ul>\n<\/ul>\n<p>&#8211; Reproducible steps<br \/>\n&#8211; Actual Result<br \/>\n&#8211; Expected Result<\/p>\n<ul>\n<li>Bug Priority<\/li>\n<li>Bug Severity<\/li>\n<li>Assigned To<\/li>\n<li>Status<\/li>\n<li>Reporter<\/li>\n<li>Affects Version<\/li>\n<li>Environment<\/li>\n<li>Component\/Module<\/li>\n<li>Attachments<\/li>\n<li>Test Case link<\/li>\n<li>User Story link<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<h3><strong>Severity Vs Priority<\/strong><\/h3>\n<p>In the Bug reporting, the terms \u201cPriority\u201d and \u201cSeverity\u201d are used to share the importance of a bug among the team and to fix it accordingly.<\/p>\n<ul>\n<ul>\n<li><strong> Priority:<\/strong><\/li>\n<\/ul>\n<\/ul>\n<p>&#8211; Priority means how fast a bug has to be fixed.<br \/>\n&#8211; The priority status is set based on the customer requirements.<br \/>\n&#8211; Values can be (Blocker, Critical, Major, Minor, Trivial)<\/p>\n<ul>\n<ul>\n<li><strong>Severity:<\/strong><\/li>\n<\/ul>\n<\/ul>\n<p>&#8211; Severity of a software bug is based on the degree of the bug impact on the operation of the system.<br \/>\n&#8211; Values can be (Blocker, Critical, Major, Minor, Trivial)<\/p>\n<h3><strong>Why Need a Good Bug Report?<\/strong><\/h3>\n<p>If your bug report is effectively documented, chances are very high that it will get fixed. So fixing a bug depends on how effectively you have reported it.<\/p>\n<h3><strong>Qualities of a Good Bug Report<\/strong><\/h3>\n<ul>\n<li>Reproducible \u2013 Incorporate reproducible steps.<\/li>\n<li>Be Specific \u2013 there should not be any ambiguity in bug summary and description.<\/li>\n<li>Add required screenshots and error logs wherever required.<\/li>\n<\/ul>\n<h3><strong>Tips to write a Good Bug Report <\/strong><\/h3>\n<ul>\n<li>Report the problem immediately if using a bug reporting tool.<\/li>\n<li>Reproduce the bug twice before writing bug report.<\/li>\n<li>Test the same bug occurrence on other similar module as well.<\/li>\n<li>Write a good bug summary that gives a brief about the bug.<\/li>\n<li>Read bug report before clicking on Submit\/Save button.<\/li>\n<li>Do not use Abusive language at all.<\/li>\n<\/ul>\n<h1><strong>Bug Tracking<\/strong><\/h1>\n<p>Bug tracking means tracking the status of any bug until it get closed. At any point of time a bug must be in any of the states given below in the diagram-<br \/>\n<img decoding=\"async\" loading=\"lazy\" class=\"alignnone size-full wp-image-31678\" src=\"\/blog\/wp-ttn-blog\/uploads\/2016\/01\/Bug-Tracking.png\" alt=\"Bug Tracking\" width=\"777\" height=\"441\" \/><br \/>\nThere are several stages in a bug life cycle<\/p>\n<ul>\n<li>Open &#8211; bug that is raised and yet to be validated.<\/li>\n<li>In Progress &#8211; bug is validated and under fixing.<\/li>\n<li>Not a Bug &#8211; Sometimes developer or team lead can mark the bug as \u201cNot a Bug\u201d if the system is working according to specifications and bug is just due to some misinterpretation.<\/li>\n<li>Deferred &#8211; When a bug cannot be addressed in that particular cycle it is deferred to future release.<\/li>\n<li>Duplicate \u2013 Same bug is already logged by QA team.<\/li>\n<li>Fixed \u2013 Bug has been fixed by developer and QA has to verify it in next build.<\/li>\n<li>Reopened &#8211; When the bug is NOT fixed, QA reopens\/reactivates the bug.<\/li>\n<li>Closed &#8211; If bug is verified by the QA team and it is fixed then QA can mark bug as \u2018Closed\u2019 or a bug can be closed if the defect is duplicate or considered as NOT as bug.<\/li>\n<\/ul>\n<h3><strong>Need of Bug Tracker<\/strong><\/h3>\n<p>The risks of not using a bug tracker in any project might result to the following &#8211;<\/p>\n<ul>\n<li>Important issues getting lost.<\/li>\n<li>Project teams waste too much time figuring out the stability of the project.<\/li>\n<li>Customers do not have the idea about the progress of bug fixing activity.<\/li>\n<li>Developer don&#8217;t realize that they&#8217;ve been assigned an issue.<\/li>\n<li>Getting bug status reports takes too long.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Bug Reporting Bug Reporting is the activity of posting a bug to the development team to fix it. Bug reporting in independent software testing can be done using a simple spread sheet or using a bug tracking tool. While reporting a bug don\u2019t forget to fill up following fields &#8211; Bug ID (Auto generated in [&hellip;]<\/p>\n","protected":false},"author":825,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":75},"categories":[1817,1816],"tags":[3020,3021],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/31675"}],"collection":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/users\/825"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/comments?post=31675"}],"version-history":[{"count":0,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/31675\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/media?parent=31675"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/categories?post=31675"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/tags?post=31675"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}