{"id":6707,"date":"2016-06-14T18:29:49","date_gmt":"2016-06-14T18:29:49","guid":{"rendered":"http:\/\/www.abstracta.us\/?p=6707"},"modified":"2025-05-05T21:21:14","modified_gmt":"2025-05-05T21:21:14","slug":"common-mistake-bug-life-cycle","status":"publish","type":"post","link":"https:\/\/abstracta.us\/blog\/software-testing\/common-mistake-bug-life-cycle\/","title":{"rendered":"The Most Common Mistake in the Bug Life Cycle"},"content":{"rendered":"<p><!-- Go to www.addthis.com\/dashboard to customize your tools --><script src=\"\/\/s7.addthis.com\/js\/300\/addthis_widget.js#pubid=ra-58d80a50fc4f926d\" type=\"text\/javascript\"><\/script><\/p>\n<h1><span style=\"font-weight: 400; color: #333333;\">Don&#8217;t forget this key step when debugging software<\/span><\/h1>\n<p><span style=\"color: #333333;\"><span style=\"font-weight: 400;\">The bug (or creature on Earth for that matter) with one of the shortest life cycles is the <a href=\"http:\/\/www.newworldencyclopedia.org\/entry\/Mayfly\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">Mayfly<\/span><\/a><\/span><span style=\"font-weight: 400;\">, who, after transitioning into the adult stage of its lifespan, typically reproduces and then dies within just 30 minutes. <\/span><b>What if bugs in software were born and eliminated that quickly and easily!<\/b><span style=\"font-weight: 400;\">\u00a0When testers and developers work together effectively, the period of time from a bug\u2019s creation to its elimination in software is minimal.\u00a0<\/span><\/span><\/p>\n<p><span style=\"color: #333333;\"><span style=\"font-weight: 400;\">Although bugs can never be 100% preventable and software will never be 100% bug-free, there are good practices that teams can adopt so that bugs in software live for only a brief amount of time and never get around to multiplying. A good incident management system helps to ensure that most bugs are found and fixed well before going into production.<\/span><\/span><\/p>\n<h2><span class=\"ez-toc-section\" id=\"The_Bug_Life_Cycle\"><\/span><strong><span style=\"color: #00b674;\">The Bug Life Cycle<\/span><\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><em><img decoding=\"async\" class=\"aligncenter size-full wp-image-6919\" src=\"http:\/\/www.abstracta.us\/wp-content\/uploads\/2016\/06\/Flujo_Ciclo-de-vida-de-un-bug_new-02-1024x724-min.png\" alt=\"bug life cycle\" width=\"1024\" height=\"724\" \/><span style=\"font-weight: 400;\">Thanks to Giulliana and Ayessa for designing this awesome graphic!<\/span><\/em><\/p>\n<p><span style=\"color: #333333;\"><span style=\"font-weight: 400;\">This is a basic sketch that sums up one of the possible ways to represent the bug life cycle that I talked about in our new <a href=\"http:\/\/abstracta.us\/blog\/test-automation\/ebook-complete-introduction-to-functional-test-automation\/\" target=\"_blank\" rel=\"noopener\">functional test automation<\/a><\/span><\/span> <span style=\"font-weight: 400;\">ebook<\/span>. <span style=\"font-weight: 400;\">There could actually be a thousand different variations of the bug life cycle based on the size of the team, the organizational structure, etc. but, for us, this cycle is basically law!<\/span><\/p>\n<h2><span class=\"ez-toc-section\" id=\"Where_Incident_Management_Can_Go_Wrong\"><\/span><strong><span style=\"color: #00b674;\">Where Incident Management Can Go Wrong<\/span><\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><span style=\"color: #333333;\"><span style=\"font-weight: 400;\">One of the most typical mistakes in bug management that the team at Abstracta has seen from working with different companies throughout the years across traditional and agile environments is when a bug is fixed and the developer marks it as closed. Yet, we must not forget to <\/span><b>double check<\/b><span style=\"font-weight: 400;\"> incidents! First, the tester reports it and then the developer fixes it, but the person who should ultimately determine if it has been resolved is the tester that reported it in the first place. What if the developer thinks it&#8217;s gone, but upon further testing, it is still there? What if a new bug has been created? <\/span><\/span><\/p>\n<p><span style=\"color: #333333;\"><span style=\"font-weight: 400;\">[tweet_box design=&#8221;default&#8221; float=&#8221;none&#8221;]A tester should always go back and check that the bug no longer exists in order to minimize risk.\u00a0[\/tweet_box]<\/span><\/span><\/p>\n<h2><span class=\"ez-toc-section\" id=\"Variations_of_the_Bug_Life_Cycle\"><\/span><strong><span style=\"color: #00b674;\">Variations of the Bug Life Cycle<\/span><\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><span style=\"font-weight: 400; color: #333333;\">There are several other valid variations of this scheme. For example, you may have someone who has the responsibility of revising the incidents that come in and decide which ones to fix and which ones not to. This situation could work within the flow above, whether it be the tester or the developer who marks a bug as \u201cresolved,\u201d \u201cwon\u2019t fix,\u201d or through a dialogue (via the tool or a different medium), both the tester and developer could decide together what is the appropriate decision, showing mutual agreement between the two. <\/span><span style=\"font-weight: 400; color: #333333;\">In another scheme, you may want to add when to re-open an incident and what happens once it is re-opened. Or, an old bug would simply appear as a new one and start the lifecycle all over again.<\/span><\/p>\n<p><span style=\"font-weight: 400; color: #333333;\">Incident management is a basic indicator of the efficiency of a development team and it is additionally a key area where you can see if testers and developers feel like they are a part of the same team or not. Both sides need to do their part to work as a team. It&#8217;s not just developers who need to work on collaborating with testers, but also testers need to not complain when bugs aren\u2019t resolved and instead share a global vision focused on the objectives of the whole team while understanding that there\u2019s no fixing everything.<\/span><\/p>\n<p><span style=\"font-weight: 400; color: #333333;\">I\u2019d love to hear your comments regarding the bug life cycle and if you follow a similar scheme or another that is more useful or appropriate for you, the typical problems you face, etc.<\/span><\/p>\n<h3><\/h3>\n<p>&nbsp;<\/p>\n<hr \/>\n<h2><span class=\"ez-toc-section\" id=\"Recommended_for_You\"><\/span><strong>Recommended for You<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><a href=\"http:\/\/abstracta.us\/blog\/software-testing\/the-software-testing-wheel\/\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">The Software Testing Wheel<\/span><\/a><br \/>\n<a href=\"http:\/\/abstracta.us\/blog\/software-testing\/career-path-software-tester-infograhic\/\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">The Career Path of a Software Tester: An Infographic<\/span><\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Don&#8217;t forget this key step when debugging software The bug (or creature on Earth for that matter) with one of the shortest life cycles is the Mayfly, who, after transitioning into the adult stage of its lifespan, typically reproduces and then dies within just 30&#8230;<\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v14.0.2 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>The Most Common Mistake in the Bug Life Cycle | Abstracta<\/title>\n<meta name=\"description\" content=\"Testers are familiar with the bug life cycle as they find and report bugs to developers, but there is one crucial step not to forget!\" \/>\n<meta name=\"robots\" content=\"index, follow\" \/>\n<meta name=\"googlebot\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<meta name=\"bingbot\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/abstracta.us\/blog\/software-testing\/common-mistake-bug-life-cycle\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"The Most Common Mistake in the Bug Life Cycle | Abstracta\" \/>\n<meta property=\"og:description\" content=\"Testers are familiar with the bug life cycle as they find and report bugs to developers, but there is one crucial step not to forget!\" \/>\n<meta property=\"og:url\" content=\"https:\/\/abstracta.us\/blog\/software-testing\/common-mistake-bug-life-cycle\/\" \/>\n<meta property=\"og:site_name\" content=\"Blog about AI-powered quality engineering for teams building complex software | Abstracta\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/AbstractaQA\/\" \/>\n<meta property=\"article:published_time\" content=\"2016-06-14T18:29:49+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2025-05-05T21:21:14+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/abstracta.us\/wp-content\/uploads\/2016\/06\/Bug_Cycle2-min.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"420\" \/>\n\t<meta property=\"og:image:height\" content=\"236\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@fltoledo\" \/>\n<meta name=\"twitter:site\" content=\"@AbstractaUS\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebSite\",\"@id\":\"https:\/\/abstracta.us\/blog\/#website\",\"url\":\"https:\/\/abstracta.us\/blog\/\",\"name\":\"Blog about AI-powered quality engineering for teams building complex software | Abstracta\",\"description\":\"AI-powered quality engineering\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":\"https:\/\/abstracta.us\/blog\/?s={search_term_string}\",\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/abstracta.us\/blog\/software-testing\/common-mistake-bug-life-cycle\/#primaryimage\",\"inLanguage\":\"en-US\",\"url\":\"http:\/\/www.abstracta.us\/wp-content\/uploads\/2016\/06\/Flujo_Ciclo-de-vida-de-un-bug_new-02-1024x724-min.png\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/abstracta.us\/blog\/software-testing\/common-mistake-bug-life-cycle\/#webpage\",\"url\":\"https:\/\/abstracta.us\/blog\/software-testing\/common-mistake-bug-life-cycle\/\",\"name\":\"The Most Common Mistake in the Bug Life Cycle | Abstracta\",\"isPartOf\":{\"@id\":\"https:\/\/abstracta.us\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/abstracta.us\/blog\/software-testing\/common-mistake-bug-life-cycle\/#primaryimage\"},\"datePublished\":\"2016-06-14T18:29:49+00:00\",\"dateModified\":\"2025-05-05T21:21:14+00:00\",\"author\":{\"@id\":\"https:\/\/abstracta.us\/blog\/#\/schema\/person\/7421e539de0357d3adb0c69ed469a1c2\"},\"description\":\"Testers are familiar with the bug life cycle as they find and report bugs to developers, but there is one crucial step not to forget!\",\"breadcrumb\":{\"@id\":\"https:\/\/abstracta.us\/blog\/software-testing\/common-mistake-bug-life-cycle\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/abstracta.us\/blog\/software-testing\/common-mistake-bug-life-cycle\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/abstracta.us\/blog\/software-testing\/common-mistake-bug-life-cycle\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/abstracta.us\/blog\/\",\"url\":\"https:\/\/abstracta.us\/blog\/\",\"name\":\"Home\"}},{\"@type\":\"ListItem\",\"position\":2,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/abstracta.us\/blog\/software-testing\/\",\"url\":\"https:\/\/abstracta.us\/blog\/software-testing\/\",\"name\":\"Software Testing\"}},{\"@type\":\"ListItem\",\"position\":3,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/abstracta.us\/blog\/software-testing\/common-mistake-bug-life-cycle\/\",\"url\":\"https:\/\/abstracta.us\/blog\/software-testing\/common-mistake-bug-life-cycle\/\",\"name\":\"The Most Common Mistake in the Bug Life Cycle\"}}]},{\"@type\":[\"Person\"],\"@id\":\"https:\/\/abstracta.us\/blog\/#\/schema\/person\/7421e539de0357d3adb0c69ed469a1c2\",\"name\":\"Federico Toledo, Chief Quality Officer at Abstracta\",\"image\":{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/abstracta.us\/blog\/#personlogo\",\"inLanguage\":\"en-US\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/6de7ec6536c4028b5c02ad4ec1b9af0d?s=96&d=blank&r=g\",\"caption\":\"Federico Toledo, Chief Quality Officer at Abstracta\"},\"description\":\"Co-founder and COO of Abstracta\",\"sameAs\":[\"https:\/\/twitter.com\/fltoledo\"]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","_links":{"self":[{"href":"https:\/\/abstracta.us\/blog\/wp-json\/wp\/v2\/posts\/6707"}],"collection":[{"href":"https:\/\/abstracta.us\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/abstracta.us\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/abstracta.us\/blog\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/abstracta.us\/blog\/wp-json\/wp\/v2\/comments?post=6707"}],"version-history":[{"count":12,"href":"https:\/\/abstracta.us\/blog\/wp-json\/wp\/v2\/posts\/6707\/revisions"}],"predecessor-version":[{"id":17526,"href":"https:\/\/abstracta.us\/blog\/wp-json\/wp\/v2\/posts\/6707\/revisions\/17526"}],"wp:attachment":[{"href":"https:\/\/abstracta.us\/blog\/wp-json\/wp\/v2\/media?parent=6707"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/abstracta.us\/blog\/wp-json\/wp\/v2\/categories?post=6707"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/abstracta.us\/blog\/wp-json\/wp\/v2\/tags?post=6707"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}