Low quality of testing

A cluster of problems including:

  • poor test cases or not proper test techniques applied

  • absent or poor requirements testing process

  • absence of relevant skills or competency in a testing team

  • absent or poor bug reporting process 

  • absent or poor naming conventions (the same issues are logged in the system, but under different titles which hardly can be found, so duplicates are produced)

  • poor knowledge of technology (e.g native features of platform)

  • poor bug refinement and analysis process before submission (e.g. duplicates in bug tracking system)

  • invalid test tools and data

  • wrong environment is used for testing

  • no issue root cause analysis and troubleshooting (several issues are logged as consequences of the same problem)

Discovered by combination of metrics:

Invalid Defects, when internal team logs issues which are closed with resolution "works as expected" or/and submitted bugs do not indicate actual product deviation from acceptance criteria 

Defect Density, when code of low quality successfully passes quality gates for product to be delivered for testing by QA team

Defect Containment, if internal team skips significant amount of valid issues which are captured by the external team during product acceptance or upon release / in production 

Recommendations: 

  1. Introduce or enhance EngX in delivery

  2. Introduce or enhance Test Approach

  3. Improve requirements and backlog management