Question

Scenario Testing - Automation Recorder issue

I have found that a recorded scenario test can fail when a recorded scenario spans multiple UI pages and UI page transition lags behind the execution of the steps in the recorded scenario. As an example, I record the following scenario:

  • UI page 1 has a button. I click the button. The click action causes UI page 2 to be displayed.
  • UI page 2 has a button. I click the button. The click action sets the case status to completed.

I playback the recorded scenario.

  • UI page 1 is rendered correctly. The button on UI page 1 is clicked.
  • There is a delay rendering UI page 2. In the meantime the recorded executes the click button action on UI page 2.
  • The case fails since the button action on UI page 2 was not executed properly.

My questions are:

  1. Is this a defect within the playback of a recorded scenario?
  2. If not, then should I assume recorded scenarios should be limited to a single UI page?

Thank you!

***Edited by Moderator Marissa to update platform capability tags****

Comments

Keep up to date on this post and subscribe to comments

Pega
July 16, 2019 - 5:49pm

Recorded scenarios are not really robust enough to be used for all but the simplest of cases. I would recommend creating a more robust automation from the recording to handle the scenario better as it sounds like you might need to wait on more than just the pages being created.

August 7, 2019 - 3:53pm

Scenario Testing does have the ability to slow down the test runner timing. You can find this in Configure > Applications > Quality > Settings.  This can help accommodate slowness in rendering the UI.

 

There have also been quite a number of improvements in the stability and speed of Scenario Testing in 8.3 and more enhancements are planned for 8.4.