QuestionQ78

VerifiedVerifying the Test Automation Solution

You work as a TAE on a project to develop a purchasing system. The system’s principal requirements are to:

  • Enable users to enter details of items they want purchased and use those details to create a purchase request.
  • Route every purchase request through a workflow that lets the requestor’s line manager approve, reject, or return it for clarification / modification.
  • Send approved requests to the Purchasing Department.
  • Enable purchasers to identify the best available supplier and place the request with that supplier as a purchase order.

Requirement 1 has now been delivered and satisfactorily tested manually. In parallel, you have developed a TAS so that functional suitability testing can be automated.

The functional suitability testing for Requirement 1 has now been automated as fully as possible. A change to add audit logging of user activity is planned but has not yet been implemented. Following a small change to the UI code, the latest regression run had a significant number of unexplained test failures and, at the point each test stopped, the actual and expected results showed no differences. In every case, the run could continue with the next test in the suite. Initial investigation found that the points where these tests stopped had nothing obvious in common.

Which option below gives the BEST next steps for investigating this?

Explanation

When a test execution reports a failure even though the actual and expected SUT results match, the likely cause is a defect in the test automation solution or an invisible mismatch. The TAS logs should be analyzed to identify a fault in its test-execution behavior. The ability to proceed to later tests and the absence of a common failure point further make a general test-environment outage less likely.

Learn more

Community Discussion

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