Which type of testing involves using a subjective report from peers?

Document testing involves using a subjective report from peers, as it primarily focuses on evaluating documentation, including project plans, requirements specifications, and design documents. This type of testing relies heavily on feedback from colleagues who review these documents to ensure clarity, accuracy, and completeness. This collaborative approach allows for identifying potential issues, misunderstandings, or gaps in the documentation from different perspectives, ensuring that the materials effectively communicate the intended information.

In contrast, boundary testing examines the limits or boundaries of input values to ensure the system behaves as expected at those extremes. Data validation testing checks that the data input adheres to the necessary quality and format criteria, often using automated checks rather than subjective peer reviews. Unit testing focuses on individual components or functions of code to verify they work correctly, typically conducted by developers as part of the coding process rather than relying on peer reports. Each of these alternatives has a distinct focus that does not center on subjective evaluations from peers, highlighting why document testing is the correct choice in this scenario.