QuestionQ77

VerifiedVerifying the Test Automation Solution

A TAS is being used for automated functional suitability testing of a stock-management system. Several tests have crashed. Even though the SUT produces detailed logs of all its activity, it has been difficult to determine the reason(s) for these crashes using the TAS and SUT test logs.

What actions are MOST likely to help with debugging?

  • a. Ensure that the TAS logs a count of the number of times each test case is executed.
  • b. Ensure that the SUT logs all available configuration data at startup.
  • c. Ensure that the SUT logs all available crash dumps and stack traces when a failure occurs.
  • d. Ensure that the SUT logs all values of randomly generated test-input data.
  • e. Ensure that all test logs are synchronized to the exact same time before any tests are executed.
Explanation

Startup configuration data identifies the conditions under which the SUT ran, while crash dumps and stack traces provide direct diagnostic evidence of the failing code path. Together, these records are the most useful information for investigating SUT crashes.

Community Discussion

No comments yet. Be the first to start the discussion!