Your SlideShare is downloading. ×
Quality Center Roles and Defect WorkflowBU AdminPERMISSIONS:• Can modify all QC Components at the project level except Adm...
PFG Business AnalystPERMISSIONS:• Can add, modify and delete requirementsRESTRICTIONS:• Can’t add or remove tests from cov...
Developer Roles (3 Levels)PFG Developer LeadPERMISSIONS:• Can add, modify and delete tests in Test Plan module• Can add, m...
PFG DeveloperPERMISSIONS:• Can add, modify and delete tests in Test Plan module• Can run tests and modify run in Test Lab ...
PFG Developer LimitedPERMISSIONS:• Can run tests and modify run in Test Lab module• Can add and modify defectsRESTRICTIONS...
Tester Roles (3 Levels)PFG Test LeadPERMISSIONS:• Can add, modify and delete requirements and add/remove them from test co...
PFG TesterPERMISSIONS:• Can add, modify and delete tests in Test Plan module• Can add, move, modify and delete folders in ...
PFG Tester LimitedPERMISSIONS:• Can run tests and modify run in Test Lab module• Can add and modify defects• Defect Workfl...
Defect Form status workflow• When a defect transitions from NEW to ASSIGNED status the ‘Assigned to’ field is required• Wh...
Defect Form status workflow• When a defect transitions from NEW to ASSIGNED status the ‘Assigned to’ field is required• Wh...
Upcoming SlideShare
Loading in...5
×

Quality center roles and defect workflow

3,192

Published on

Free quality center Tutorial ebooks download - quality center Tutorial in free PDF format ebooks for Beginners ready to download with high speed - www.ebookzdownload.com

Published in: Education, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
3,192
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "Quality center roles and defect workflow"

  1. 1. Quality Center Roles and Defect WorkflowBU AdminPERMISSIONS:• Can modify all QC Components at the project level except Administration items reserved to theQC Admin (specifics still TBD)• Administer security at the QC project level• Create QC projects and modify fields determined to be customizable at the BU Admin level• Can delete a defectPFG BPTPERMISSIONS:• Can create and modify components in Business Process TestingRESTRICTIONS:• View only access to other modules, can be combined with another role for additional access
  2. 2. PFG Business AnalystPERMISSIONS:• Can add, modify and delete requirementsRESTRICTIONS:• Can’t add or remove tests from coverage• View only access to other modules, may be combined with another security role (such as PFGTester)
  3. 3. Developer Roles (3 Levels)PFG Developer LeadPERMISSIONS:• Can add, modify and delete tests in Test Plan module• Can add, move, modify and delete folders in Test Plan module• Can add, modify and delete test sets• Can add and modify defectsRESTRICTIONS:• View only access to Requirements and Business Components modules• Defect Workflow - Cannot change defect status to CLOSED, except when Test Type selected forthe defect is UNIT• Cannot delete a defect
  4. 4. PFG DeveloperPERMISSIONS:• Can add, modify and delete tests in Test Plan module• Can run tests and modify run in Test Lab module• Can add and modify defectsRESTRICTIONS:• View only access to Requirements and Business Components modules• Cannot add, move, modify or delete folders in Test Plan module• Defect Workflow - Cannot change defect status to CLOSED, except when Test Type selected forthe defect is UNIT• Cannot delete a defect
  5. 5. PFG Developer LimitedPERMISSIONS:• Can run tests and modify run in Test Lab module• Can add and modify defectsRESTRICTIONS:• View only access to Requirements, Business Components and Test Plan modules• Defect Workflow - Cannot change defect status to CLOSED, except when Test Type selected forthe defect is UNIT• Cannot delete a defect
  6. 6. Tester Roles (3 Levels)PFG Test LeadPERMISSIONS:• Can add, modify and delete requirements and add/remove them from test coverage• Can add, modify and delete tests in Test Plan module• Can add, move, modify and delete folders in Test Plan module• Can add, modify and delete test sets• Can add and modify defectsRESTRICTIONS:• View only access to Business Components module• Cannot delete a defect
  7. 7. PFG TesterPERMISSIONS:• Can add, modify and delete tests in Test Plan module• Can add, move, modify and delete folders in Test Plan module• Can run tests and modify run in Test Lab module• Can add and modify defectsRESTRICTIONS:• View only access to Requirements and Business Components modules• Cannot delete a defect
  8. 8. PFG Tester LimitedPERMISSIONS:• Can run tests and modify run in Test Lab module• Can add and modify defects• Defect Workflow – is allowed to change defect status from READY FOR RETEST to ASSIGNEDin the event a test of a fixed defect failsRESTRICTIONS:• View only access to Requirements, Business Components and Test Plan modules• Defect Workflow - Cannot change defect status from NEW to ASSIGNED• Defect Workflow - Cannot change defect status to CLOSED• Cannot delete a defect
  9. 9. Defect Form status workflow• When a defect transitions from NEW to ASSIGNED status the ‘Assigned to’ field is required• When CLOSE status is selected the ‘Root Cause’ field is required.Questions for BU Reps on Defect Form1. Is date field required on defect form for the date a defect is closed or will defect historybe sufficient for tracking date closed? A field for this purpose would allow for filteringby Closed Date but History does provide date/time stamps for when the defect is closed.2. Are date fields required for tracking duration defects remain in ‘IN PROGRESS’ statusor will defect history be sufficient for tracking time it takes developer to fix defects oncethey are accepted (as indicated by changing status to IN PROGRES)? We noted someareas are currently tracking time required to fix by using date fields within their defectform.3. Do we need to add a field to the defect form titled Build/Version# or will the ‘DetectedIn’ field provide enough flexibility in conjunction with the folder structure to track defectdetection by build and test cycle?4. Do we want the ‘Detected By:’ field to be read only reflecting the ID of the person thatopened the defect or will we allow this field to be modified? Consideration is that adefect may be opened by one test team member on behalf of another. History does trackID when this field is changed.
  10. 10. Defect Form status workflow• When a defect transitions from NEW to ASSIGNED status the ‘Assigned to’ field is required• When CLOSE status is selected the ‘Root Cause’ field is required.Questions for BU Reps on Defect Form1. Is date field required on defect form for the date a defect is closed or will defect historybe sufficient for tracking date closed? A field for this purpose would allow for filteringby Closed Date but History does provide date/time stamps for when the defect is closed.2. Are date fields required for tracking duration defects remain in ‘IN PROGRESS’ statusor will defect history be sufficient for tracking time it takes developer to fix defects oncethey are accepted (as indicated by changing status to IN PROGRES)? We noted someareas are currently tracking time required to fix by using date fields within their defectform.3. Do we need to add a field to the defect form titled Build/Version# or will the ‘DetectedIn’ field provide enough flexibility in conjunction with the folder structure to track defectdetection by build and test cycle?4. Do we want the ‘Detected By:’ field to be read only reflecting the ID of the person thatopened the defect or will we allow this field to be modified? Consideration is that adefect may be opened by one test team member on behalf of another. History does trackID when this field is changed.

×