Good test data design: which of the following is NOT a characteristic of effective preliminary test data for validating a system?

Introduction / Context:
High-quality test data ensures that systems are validated against real-world scenarios. Involving users early and aiming for comprehensive coverage reduce production defects.

Given Data / Assumptions:

• Goal: identify the statement that is not a characteristic of good test data.
• Good practices include coverage breadth and execution of all logic where practical.

Concept / Approach:
Users provide domain scenarios, edge cases, and acceptance criteria. Test data should be comprehensive (positive, negative, boundary, and exception) and strive for high code/branch coverage to exercise every statement or path feasibly.

Step-by-Step Solution:

Verification / Alternative check:
User acceptance testing and shift-left QA emphasize earlier user engagement to refine data sets and reduce defects.

Why Other Options Are Wrong:
Comprehensive datasets and high execution coverage are hallmarks of effective testing; dismissing user involvement degrades realism and acceptance.

Common Pitfalls:
Using only synthetic data that misses real edge cases; not anonymizing production-like data; ignoring negative and boundary conditions.

Final Answer:
users do not participate at this preliminary stage