NOT TESTED is used when what occurs in the Trusted Tester process?

• A. The Trusted Tester process does not provide a way to evaluate some Test Conditions
• B. NOT TESTED means the test was skipped due to time constraints
• C. NOT TESTED means the site passed
• D. NOT TESTED is never used

Answer: (A)

In Trusted Tester work, NOT TESTED means there isn’t a way to evaluate that Test Condition within the current test setup. It signals that there’s no measurable method or data available to determine whether the condition is met, so a pass or fail can’t be declared for it. It’s not about running out of time, and it isn’t a declaration that the site passed. It also isn’t a statement that this never happens—there are legitimate cases where a condition can’t be evaluated due to the testing environment or the way the feature is implemented.

For example, if a Test Condition depends on a scenario or user interaction that isn’t present in the test build, there may be no way to assess it, so it would be marked as NOT TESTED.