QuestionQ24

VerifiedImplementation and Deployment Strategies for Test Automation

You are working as a TAE on a project to build a purchasing system. The main requirements for the system are to:

  • Allow users to enter details of items they want purchased and, using those details, create a purchase request.
  • Take each purchase request through a workflow that allows the requestor’s line manager to approve the request, reject it, or return it for clarification / modification.
  • Forward approved requests to the Purchasing Department.
  • Allow purchasers to find 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. You have just run a pilot of the TAS on the implementation of Requirement 1, and several things went wrong:

One test failed because required reference data was missing, and this failure plus several others were difficult to diagnose. Another test failed unexpectedly because an old version of the script was used.

Which THREE measures could mitigate these risks during deployment?

Explanation

Trace-level test logging provides detailed execution information for diagnosing failures. Automatically creating and loading test data establishes the required preconditions, including reference data. Careful packaging under thorough configuration management controls testware versions and helps ensure that the intended script version is deployed.

Learn more

Community Discussion

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