Defining the TET session parameters: (i) Setting goal(s): when selecting the goal(s) for the session, factors to be taken into account include, for example, the phase of development and the defect situation. (ii) Scheduling: selecting a good point in time for a TET session and deciding on the session duration. (iii) Taking care of practicalities such as space arrangements. (iv) Selecting possible TET focus areas. (v) Selecting TET participants. (vi) Formulating and sending a session invitation and following up on the responses. It is good to briefly introduce the TET session approach and ET in general in the invitation as well as the session goals and possible focus areas. (vii) If applicable: creating/updating defect and enhancement idea templates. (viii) If applicable: creating and preparing/checking test accounts and needed test data. (ix) If applicable: familiarizing with and checking utilized testing tools. (x) If applicable: familiarizing with utilized test technique. (xi) Smoke testing of the target software version. If the latest target software version suffers from severe regression, the session can be rescheduled or a previous working version can be used. ET can be used as a smoke-testing approach. (xii) Configuring and checking software, hardware, network, and other environment variables to be used in the session. (xiii) Preparing the TET approach introduction.
TET participant candidate
(i) Allocating time for the session/rejecting the invitation to let the TET facilitator decide whether she should invite more people.
TET domain expert
(i) Allocating time for the session/proposing a new time. (ii) Supporting the TET facilitator in arrangements, for example, proposing fruitful focus areas. (iii) Preparing the target software (version) introduction, including basic use cases.
TET domain management
(i) Allocating resources for the TET session execution.
