With which of the following categories is a test comparator tool USUALLY associated?

Question

Options

• ATool support for performance and monitoring.
• BTool support for static testing.
• CTool support for test execution and logging.
• DTool support for the management of testing and tests.

• A
  14% (4)
• B
  4% (1)
• C
  75% (21)
• D
  7% (2)

Explanation

A test comparator tool automatically compares actual test outputs against expected results, which is a core activity during test execution - making it squarely part of Tool support for test execution and logging (C). Without execution producing actual output, there is nothing to compare.

Why the distractors are wrong:

• A (Performance and monitoring) - those tools measure metrics like response time and resource usage, not output comparison.
• B (Static testing) - static tools (linters, code analyzers) examine code without running it; a comparator requires the test to have run.
• D (Management of testing) - management tools handle planning, tracking, and reporting (e.g., test management systems), not the mechanics of comparing outputs.

Memory tip: Think of the comparator as the "judge" sitting at the finish line of execution - it can only do its job after the test has run and produced output to evaluate.

No community discussion yet for this question.