What outcomes can the Tester produce?

What outcomes can the Tester produce?

• A. Pass/Fail
• B. Yes/No
• C. Pass/Fail or Yes/No
• D. Inconclusive

Answer: (C)

Testing a condition on each feature provides a decision point in the workflow. The Tester reports the result of that condition and can drive downstream logic in different ways. It can yield a standard Pass/Fail outcome, which is the typical way to indicate whether a feature meets the test and should continue or be flagged. It can also provide a Yes/No result, which functions as a boolean indicator for downstream decisions or for setting attributes that reflect the test outcome. This flexibility lets you choose how you want to represent the result—either as a pass/fail gate or as a boolean Yes/No signal—depending on how you want to route features or record results. Inconclusive isn’t a built-in, fixed output of the Tester; the usual outputs are Pass/Fail or Yes/No, making option C the best match.

Testing a condition on each feature provides a decision point in the workflow. The Tester reports the result of that condition and can drive downstream logic in different ways. It can yield a standard Pass/Fail outcome, which is the typical way to indicate whether a feature meets the test and should continue or be flagged. It can also provide a Yes/No result, which functions as a boolean indicator for downstream decisions or for setting attributes that reflect the test outcome. This flexibility lets you choose how you want to represent the result—either as a pass/fail gate or as a boolean Yes/No signal—depending on how you want to route features or record results. Inconclusive isn’t a built-in, fixed output of the Tester; the usual outputs are Pass/Fail or Yes/No, making option C the best match.