Permalink
Fetching contributors…
Cannot retrieve contributors at this time
60 lines (33 sloc) 2.09 KB

Defect standards

Why

  • We want to provide sufficient and wholistic information to developers on defects/issues found, in order to properly diagnose, reproduce, and resolve them.

  • We want to be able to monitor and measure production and staging defects to see the application health and trend, in order to make informed decisions on specific areas for improvement.

What

We need a standard process of how to

  • Properly report defects
  • Properly monitor defects

To accomplish the above, we use JIRA for issue tracking, and align on using the issue type TD Defect for all production and staging defect reports.

This specific issue type contains useful fields for diagnosis, it also enables data collection and visualization through domo, so that we can do data analysis on defects across all teams.

How

JIRA:

Make sure the issue type TD Defect is enabled for your project by following this google doc.

When logging defects, make sure to provide as much information as possible, such as:

  • Testing environment
  • Defect nature
  • Browser type

etc.

So that application owners can easily identify and investigate the problem.

As mentioned in the What section, we want to be able to visualize defect data. These are tracked in the Domo/defect reports view.

FAQ

Q: “TD Defect” is not showing up when I create issue?

A: That’s because it’s not configured for your project, refer to the documentation: enabling your project for TD Defect for instructions.

Who

@qa

Reference