nerdexam
iSQI

CTAL-TAE · Question #57

The last few runs for a suite of automated keyword-driven tests on an SUT were never completed. The test where the run was aborted was not the same between runs. Currently, it is not possible to…

The correct answer is C. Log all expected logging data in the final test execution log file, not only for keywords that fail, but. To identify the root cause of the aborts, you first need complete visibility into all keyword executions. By logging all expected data for both successful and failing keywords, you can analyze the full execution flow and detect patterns leading to the exceptions. This detailed…

Verifying the Test Automation Solution

Question

The last few runs for a suite of automated keyword-driven tests on an SUT were never completed. The test where the run was aborted was not the same between runs. Currently, it is not possible to identify the root cause of these aborts, but only determine that test execution aborted when exceptions (e.g., NullPointer, OutOfMemory) occurred on the SUT by analyzing its log files. Test execution log files are currently generated, in HTML format, by the TAS as follows:

all expected logging data is logged for each keyword in intermediate log files. This data is then inserted into the final log file only for keywords that fail, while only a configurable subset of that data is logged for keywords that execute successfully. Which of the following actions (assuming it is possible to perform all of them) would you take FIRST to help find the root cause of the aborts?

Options

  • ALog the stack trace and amount of memory available to the SUT at the start and end of each test
  • BSplit the generated log file into smaller parts, load them into external files that are loaded into the
  • CLog all expected logging data in the final test execution log file, not only for keywords that fail, but
  • DUse appropriate colors to effectively visually highlight different types of information in the test

How the community answered

(54 responses)
  • A
    24% (13)
  • B
    6% (3)
  • C
    59% (32)
  • D
    11% (6)

Explanation

To identify the root cause of the aborts, you first need complete visibility into all keyword executions. By logging all expected data for both successful and failing keywords, you can analyze the full execution flow and detect patterns leading to the exceptions. This detailed logging provides the necessary information to diagnose the issue reliably.

Topics

#keyword-driven testing#test execution logs#exception handling#log analysis

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full CTAL-TAE Practice