You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On 4.13 it is possible to set a timeout for a specific step (new functionality). It is not working. The value inserted is not respected, timeout is inherited from general definition of testcase execution/campaign.
Please refer to images:
The text was updated successfully, but these errors were encountered:
Hello @akatmiranda. Sorry but we could not reproduce.
It is working on the test I just made using BrowserStack.
Can you please detail or reproduce using prod.cerberus-testing ?
With a timeout parameter to 15000 (not overwrite):
Result:
With the overwrite parameter to 5000:
Result:
Maybe you forgot to save the script after changing the overwrite options.
We changed the confirmation button from Save to OK in order to make it easier to understand that you need to save the testcase in order to apply the new settings.
vertigo17
changed the title
[Cerberus4.13] Setting timeout for a particular step doesn’t work
[Cerberus4.13] Support timeout overwrite for Appium (IPA and APK) applications.
Feb 2, 2022
On 4.13 it is possible to set a timeout for a specific step (new functionality). It is not working. The value inserted is not respected, timeout is inherited from general definition of testcase execution/campaign.
Please refer to images:
The text was updated successfully, but these errors were encountered: