(i) Investigating and reviewing defect and enhancement idea reports: checking to determine whether defects are reproducible, whether defects have been reported already, whether defects are not enhancement ideas or vice versa, and whether enhancement ideas have already been planned. Asking for more information from reporters if something is unclear. (ii) Defect reporting to error management tool. (iii) Existing defect commenting if new use cases for them were found. (iv) Enhancement idea reporting to the requirement management tool. (v) Test case creating/updating based on the defects found. Each defect has to have a corresponding test case in the project’s testware, which then can be used in defect retesting and in regression testing to prevent similar defect leaking again. (vi) Test case creating based on accepted enhancement ideas. (vii) Adding created test cases to the regression test suite. (viii) Test coverage analysis based on defect distribution. If defects cluster in certain area(s), the test coverage of those areas might need to be improved. The development team must also be informed of clustering since it can be a sign of a bad coding. (ix) TET session summary reporting to participants, TET domain management, and other interested parties, and for approach followup. (x) Feedback and idea gathering from session participants for TET session process improvements. (xi) Approach updating based on collected feedback and the facilitator’s own observations. (xii) Defect verification and retesting after corrections.
TET participant
(i) Answering questions concerning unclear reports. (ii) Giving TET session feedback to the facilitator.
TET domain expert
(i) Giving feedback on proposed enhancement ideas. (ii) Giving TET session feedback to the facilitator.
TET domain management
(i) Following up on the results. (ii) Giving TET session feedback to the facilitator. (iii) Adjusting resources, if needed.
