Bug 10222

Summary: Bugzilla component break-down required for QA/Testing
Product: [Infrastructure] Bugzilla Reporter: Benjamin Esquivel <benjamin.esquivel>
Component: bugzillaAssignee: Richard Purdie <richard.purdie>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: Medium CC: bluelightning, infras.bug.watcher, Infras.watcher, joshuagloe, sonia.delgado
Version: unspecified   
Target Milestone: Q4   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Benjamin Esquivel 2016-09-05 18:44:07 UTC 
Currently, when filing a bug against QA/testing you only get components with no break-down. This is the current mapping:

Component:[subcomponent list]
  Automated Build Testing: Automated Build Testing
  Automated Runtime Testing: Automated Runtime Testing
  Manual Testing: Manual Testing
  Test Plans/Suite: Test Plans/Suite

This is not descriptive, the classification categories need breakdown so more info is provided at the bug filing.

The proposal is to include the QA targeted areas as the sub-component list instead. i.e.

  Automated Build Testing: eSDK, bitbake, BSP, etc.
  Automated Runtime Testing: SWUpd, BSP, ptest, etc.
Comment 1 Richard Purdie 2018-11-13 11:04:00 UTC 
I've updated the QA/Testing components to better cover the various kinds of testing we have.