Sell me this defect …

The defect[bug] is an important role in the software development lifecycle, finding a bug[defect] seemed to be easy, but closing those defects are not a simple. In our software industries, 25% of bugs are opened more than 12 months, due to various reason, the bug does not explain properly, not communicated properly or prioritized or reports share to right audiences.

Defect[ bug ] Life Cycle.

Open > Defect has been open by anyone from our team, would be a developer, tester, Manager, product owner, and business analyst or end users.

Assigned > Defects should be assigned to the development team or Business Owner Ex: Our testing scope added multiple interfaces then it’s a challenge to get root cause on time, So set up the defect-triage meeting assign those defects to the respective team by Test lead, Scrum Master, Product/business owner or Development Manager. Some scenario defect assigned to Product owner or BA if you need clarifications.

Fixed > We(QA) get the fix from the development team.

Retest > Fixed defect should be deployed to test environment [Dev, QA, UAT, Preprod, PRODUCTION ], defect state should be moved to retest state which means tester should ready to start the testing when the fix was deployed on the test environment. Mostly done by development lead/release manager or deployment team.

Rejected > Defect can be rejected due to various reasons, such as invalid defect, assigned to the different team, Data error, Duplicate defect. Those defect should be rejected by Test lead, Scrum Master, Product owner or Development Lead/Manager.

Reopened> > We[qa] team has to retest the defect on time, if it is failed the defect should be reopened or reraised. Mostly done by tester/Test lead/Automation Tester. if unable to retest the defect as a testing team provide the justification.

Deferred > Defect can be moved to the deferred state, due to various reason might be feature ticket, other dependencies and out of scope.

For defect report should be mapped to root cause and it’s mandatory, this helps to reduce defect and improve the quality and prevention.

Accessibility issue > All external users application should meet the section508 compliance. It’s a subset of usability issue if a physically challenged person does not able use the application, we[qa] marked as an accessibility issue.

Authentication error > It’s maybe various reason such as login issue, environment problem [ Server issue, Database connections issue], token expired/not assigned, Data issue, User id is an inactive state, password problem, network issue, VPN connectivity problem and more…

Application[System] error > Such as application down, not pointing to the right environment ,functional failures…

Business error > Business requirement is not clear, expected information is missing in the BRD [Business requirement document].

Browser issueOn Cross browser testing, the specific browser does not support.
ex: Website working only on Chrome, Not mush responsive

Content issue > Image is not clear, Audio is not playing, Video is not clear/not playing, content color is not visible, font type is not clear, the format is the mismatch, file size problem, content is not downloading and more…

Data issue > Could be test data issue , Data migration issue, data setup issue,Invalid data and more.

Database issue > Not pointing to expected DB, Services was down, data table issue, data is not stored, data migration issue and more…

Duplicate bug > Most of the time created by the testing team. :), It’s should review by QA-team and should be closed.

Design bug > Screen Display location, User information message, repeated screen design, some scenario tester’s clarification has been mapped to the design bug.

Devices Specific error: Mostly digital arena, Ex: iPhone-X does not support forms.

Environment issue > Could be various reasons, more information click this Link Environment issue

Functional issue > The expected functionality is not working,
ex: Button does not respond
when clicking on the button, getting an error.

Interface error > Interface system does not support expected the response code, API service was down, Interface service issue.

Ex :
502 Bad Gateway
503 Service Unavailable
504 Gateway Timeout

Installation issue > Application does not installed properly
[Ex: App does not installed properly, App crashed after the installations etc…]

Network error > Connectivity issue , host file error.

Ex :
511 Network Authentication Required
599 Network Connect Timeout Error

Program error > This bug leaked from unit testing, example: when we submit the form getting an error[ could be Syntax errors, Logical errors, Runtime errors etc…]

Performance issue > 25% of performance issue observed during the live. Example page loading issue, slow response, the image is not loading, concurrent login issue etc.

Ex: Click this link :

Requirement error > 30% of bugs have been identified on requirement area, the reason behind, less documentation, requirements are very high level, the tester does not participate on an early phase. Most the tester clarification mapped to requirement error/gap.

Report error > This bug always been a low priority, unless if the specific requirement has been raised by business. I’d raised the defect on the TAT report [ Siebel on Demand], Turn around time is mismatched when choosing the different registration/time zone.

OS Specific > Most of the latest Operating system should be supported to applications, if not that would be OS specific error or Compatibility issue.

Out of Box functionality > few features does not support interface system or third-party application, which means OOB functionality for our testing scope.

Security bug > Security bug is more critical one
Ex: Authentication, Security misconfiguration, sensitive data exposure, Unvalidated redirects, cross-site script etc.

Tester error > On Test execution phases, few defects are created, however, those defect(s) are not valid bugs, such as test data setup issue, test cases understanding challenges, execution error.

Usability issue > Application is hard to use by users, pagination, and user forms are added additionally, an additional pop-up message for user error information, error handling issue and more.

Clarifications > For understanding purpose tester can create a defect, this may moved to feature defects or Internal Audit purpose.

UTR[Unable to Reproducible] > During Test execution, few defects are unable to reproducible every time.such as network related issue, content download issue, App crashed etc..

For below the reports are generated based on mock-up data and used piktochart, more information
check out thislink

Defect Leakages are measured from different phase

– Requirement
– Design
– Unit Testing
– System Testing
– Integration Testing
– System Integration Testing.
– End to End Testing.
– User Acceptance Testing
– Beta Phase.
– Production.

Defect vs Applications.

Detailed defect report by number[s]

Applications vs Defect Priority Report

Defect reopened reports, Defect vs Test cases, Defect opened vs fixed, Defect vs team …more

5,110 thoughts on “Sell me this defect …

  1. Howdy! I could have sworn I’ve been to this website before
    but after browsing through some of the post I
    realized it’s new to me. Anyhow, I’m definitely glad I found it and I’ll be
    bookmarking and checking back often!

  2. Piece of writing writing is also a fun, if you be acquainted with afterward you can write if not it is complex to write.

  3. Hi! Would you mind if I share your blog with my facebook
    group? There’s a lot of people that I think would really appreciate your content.
    Please let me know. Thanks

  4. An outstanding share! I have just forwarded this onto a co-worker who had been doing a little research on this.

    And he in fact bought me breakfast due to the fact that I found it for him…
    lol. So allow me to reword this…. Thanks for the meal!!
    But yeah, thanks for spending some time to discuss this topic here on your web

  5. Hello! I’ve been reading your site for a while now and finally got the bravery to
    go ahead and give you a shout out from Atascocita Tx! Just wanted to mention keep up the
    fantastic work!

  6. This is really interesting, You’re an overly professional blogger.
    I have joined your feed and sit up for in the hunt for
    extra of your great post. Also, I have shared your
    website in my social networks

  7. We’re a group of volunteers and opening a new scheme in our community.
    Your web site provided us with valuable info to
    work on. You’ve done a formidable job and our entire community will
    be grateful to you.

  8. I like the valuable info you supply on your articles. I will bookmark your weblog and take a look at once
    more here regularly. I am somewhat sure I will be told many new stuff right right here!
    Good luck for the following!

  9. I love your blog.. very nice colors & theme. Did you design this
    website yourself or did you hire someone to do it for you?
    Plz respond as I’m looking to construct my own blog and would like to find
    out where u got this from. thanks

  10. Wonderful items from you, man. I have remember your
    stuff previous to and you’re just extremely fantastic. I really like what you have bought right here, really like what you are saying
    and the way in which through which you are saying it.
    You make it enjoyable and you continue to care for to
    keep it wise. I can’t wait to learn far more from you.

    This is really a great site.

  11. When someone writes an paragraph he/she keeps the idea of a user
    in his/her brain that how a user can know it. Thus that’s why this article is outstdanding.

  12. I absolutely love your blog.. Pleasant colors & theme.
    Did you create this amazing site yourself? Please reply back as I’m trying to create my own personal site and would love to know where you got this
    from or exactly what the theme is called. Appreciate it!

  13. Unquestionably imagine that which you stated. Your favourite reason seemed
    to be at the net the simplest thing to take into account of.
    I say to you, I certainly get annoyed even as folks consider worries
    that they plainly don’t know about. You managed to hit the nail upon the top and outlined
    out the whole thing with no need side-effects , people can take a
    signal. Will probably be back to get more. Thank you

  14. Hi there I am so thrilled I found your webpage, I really found you by error, while I was browsing on Askjeeve for something else, Anyways I am here now and would just like
    to say thanks for a fantastic post and a all round enjoyable blog (I also love the theme/design),
    I don’t have time to read it all at the moment but I have bookmarked it and also included your RSS
    feeds, so when I have time I will be back to read more, Please do keep up the great work.

  15. Greetings! I know this is kind of off topic but I was wondering which blog platform are you using for
    this site? I’m getting tired of WordPress because I’ve had
    problems with hackers and I’m looking at alternatives for
    another platform. I would be great if you could point me
    in the direction of a good platform.

  16. I’ve been surfing online more than 4 hours today, yet I never found any
    interesting article like yours. It’s pretty worth enough for me.
    In my opinion, if all web owners and bloggers made good content as you did, the web will be a lot more useful than ever before.

  17. You actually make it seem so easy with your presentation however I to find this topic to be really one thing which I believe I might never understand.

    It seems too complicated and extremely huge for me. I
    am having a look ahead to your next publish, I will attempt to
    get the hang of it!

  18. Hi! This post could not be written any better!
    Reading this post reminds me of my good old room mate!

    He always kept talking about this. I will forward this page to him.
    Pretty sure he will have a good read. Thank you for

  19. My brother recommended I might like this web site. He was entirely right.
    This post actually made my day. You can not imagine simply how
    much time I had spent for this info! Thanks!

  20. Thank you for the auspicious writeup. It in fact was a amusement account it.
    Look advanced to more added agreeable from you! By the way,
    how can we communicate?