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