Software Testing Social Network

Owner

Task

Test Lead

Create the test execution schedule.

Tester

Execute Test Cases.

Create Defects when defect is encountered using Test Director tool.  Follow guidelines for mandatory fields and required test data. (see below for ‘Tester’ role).  Assign Owner as Work stream Lead

Development Lead

Query ‘Submitted’ Defects on a daily basis in preparation for meeting.  Also email notification is sent so severity can be assessed.

Review any new defects inputted several times a day for validity and duplication.

Initial assessment of severity and assignment.

Development Lead

Assess validity of defect.

Valid Defects: Assign to appropriate developer, validate, adjust priority and give a Date of Resolution.

Invalid Defect: Change state to Working as Designed or Enhancement Required, Resolved, Save, Change State to Ready for Test and Assign ownership back to submitter and add a Comment indicating reason. Click on OK.

Developer

Receive Defect notification email; change State to Open indicating the defect is currently being addressed. 

Assess Validity of Defect.  (double check point after Work stream lead makes same initial evaluation)

Invalid Defect: Change state to Working as Designed or Enhancement Required,  Resolved, Save, Change State to Ready for Test and Assign ownership back to submitter and add a Comment indicating reason. Save.

Valid Defect:  Complete fix according to Defect Resolution Timeline (see above).  Upon completion, change State to Resolved and assign to Build and Deploy team.  Input the resolution details in the Comments entry area. Save the State change.

Build Verification Team

Finalize scheduled build date/time.

Open all affected defects, input Build Version information, update to resolution of ‘Resolved’, and assign the defect to Ready to Test and assign the tester who originated the defect.

Send Test Lead a list components/defect ID’s modified for the new build version when the build is complete.

Build and Deploy Team

Deploy new build for system test environment (frequency based on severity of current defects)

• Release Notes should include defect ID’s
• Email should be sent to all Technical Leads and other appropriate parties indicating completion of build along with release notes.

Tester

Receive email notification indicating defects ready to Re-test.

For those defects returned from developer as ‘Working as Designed’ or ‘Enhancement Required’,  speak to Test Lead and Defect Manager and do not change current state of defect or retest.   Final resolution may require reassignment to IBM/ProjectX business analyst.

Re-test associated test case.

Successful retest:  Change the Status to ‘Closed’.

Unsuccessful retest: Reassign defect to Developer and Enter Comment indicating reason for reassignment.

 Test Lead

Create Defect Report/Test Results Report(s) including defects resolved as ‘Working as Designed’ or ‘Enhancement Required’