UiPath Autopilot provides requirements quality evaluation capabilities within Test Manager, helping testers identify deficiencies that could compromise test design and coverage.

Option C is correct because requirements should be revised to address unclear acceptance criteria and missing expected results before proceeding with test generation.

Autopilot evaluates requirements against quality characteristics such as clarity, completeness, and consistency. It generates recommendations that testers can review and incorporate into the requirement.

A requirement with ambiguous acceptance criteria creates uncertainty about the application's intended behavior. This uncertainty can lead to incorrect assertions, incomplete test scenarios, and conflicting interpretations of successful execution.

The appropriate remediation is to define the operating conditions, expected outcomes, validation rules, and measurable success criteria.

For example, a requirement describing successful payment processing should identify the expected payment status, transaction reference, and relevant failure behavior rather than merely stating that the payment should succeed.

UiPath allows users to track improvement suggestions and update their implementation status. After revising the requirement, a further evaluation can assess whether the identified deficiencies have been addressed.

Option A confuses requirements coverage with requirements quality. Option B repeats evaluation without addressing the underlying defects. Option D prematurely converts an incomplete requirement into a test case.

Official UiPath Reference(s): Autopilot User Guide — Quality-check requirements; Best practices and limitations.