QuestionQ85
VerifiedTest Automation Reporting and MetricsThe last several executions of a suite of automated keyword-driven tests on an SUT did not complete. The test at which execution was aborted differed between runs. At present, the root cause of these aborts cannot be identified; analysis of the SUT log files can only establish that test execution aborted when exceptions (for example, NullPointer or OutOfMemory) occurred on the SUT.
The TAS currently produces HTML test-execution log files as follows: all expected logging data for each keyword is written to intermediate log files. That data is inserted into the final log file only for keywords that fail, whereas only a configurable subset is logged for keywords that execute successfully.
Which of the following actions, assuming all are possible, would you take FIRST to help identify the root cause of the aborts?
Community Discussion