Use a multi-prong approach when you review this practice. You can start by
focusing on the work products that will be produced or used during testing and
then shift to the tasks involved in processing those artifacts. You might play
different roles within your team. If you are a tester, then you will need to
get a very good understanding of the artifacts, the tasks, and the guidelines
supporting them. For a developer, the main points of interest are the artifacts
used within this practice.
Start with the Test artifacts, read their description, and understand when
they are used (produced or used), by whom, and which roles are mainly responsible:
Switch the focus to tasks and, depending on your main role within the team,
review the associated guidelines, concepts and, if applicable, the tool-related
guidance:
|