Test director proposedimprovementsv0.4

Test Director – Proposed improvements within currently used project life cycle By Jason Dynes

Test Director – What is it used for? ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

Test Director – How is it used? ,[object Object],[object Object],[object Object],[object Object],[object Object],Specify Requirements Plan Test Execute Tests Track Defects

Test Director – How is it used? ,[object Object],Specify Requirements Plan Test Execute Tests Track Defects

Requirements – Why use this? ,[object Object],[object Object],[object Object],[object Object]

Requirements – Proposed Changes ,[object Object],[object Object],[object Object],The top level requirement denotes the Change Request Number e.g. CR 213 The second level and below details the actual testing requirements for that particular CR The ‘Product’ field is a lookup field denoting the release that it is associated with

Requirements - Benefits ,[object Object],[object Object]

Requirements – Proposed Changes ,[object Object],[object Object],The ‘Reviewed’ field is amended by the reviewer

Requirements - Benefits ,[object Object],[object Object],[object Object]

Test Plan – Why use this? ,[object Object],[object Object],[object Object]

Test Plan – Proposed Changes ,[object Object],[object Object],The top level requirement denotes the release that the CR is assigned to The second level denotes the Change Request Number e.g. CR 213 The third level and below details the actual testing requirements for that particular CR

Test Plan – Proposed Changes ,[object Object]

Test Plan - Benefits ,[object Object],[object Object],[object Object]

Test Plan – Proposed Changes ,[object Object],[object Object]

Test Lab – Why use this? ,[object Object],[object Object]

Test Lab – Proposed Changes ,[object Object],The top level requirement denotes the release that the CR is assigned to The second level denotes the Change Request Number e.g. CR 213

Test Lab – Proposed Changes ,[object Object],[object Object]

Defects – Why use this? ,[object Object],[object Object],[object Object],[object Object]

Defects – Proposed Changes ,[object Object],[object Object],[object Object],The ‘Project’ field denotes the release that the defect is assigned to The ‘Component’ field denotes the component affected by the problem The ‘CR No. impacted’ field denotes any CR that is impacted by the defect. The ‘System Environment’ defines in which environment the problem was detected in e.g. PROD, INT, UAT, PRS

Defects – Proposed Changes ,[object Object],[object Object],[object Object],[object Object]

Defects – Proposed Changes ,[object Object],[object Object]

Defects - Benefits ,[object Object],[object Object]

Test Director – Implementation ,[object Object],[object Object],[object Object],[object Object],Time Defects Training Defects Requirements Test Plan Phase 1 Test Lab Phase 2 Phase 3 Test Lab Training Test Plan Training Requirements Training

Test Director – FAQ’s ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

Test Director – Other considerations ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

Test Director – The End The End

Test director proposedimprovementsv0.4

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Test director proposedimprovementsv0.4

Similar to Test director proposedimprovementsv0.4 (20)

Recently uploaded

Recently uploaded (20)

Test director proposedimprovementsv0.4