When executing automated tests, it is often the case that the test script will run too quickly and fail to keep up with the screen transitions, etc., to be tested. MagicPod provides a mechanism to prevent this by automatically waiting for screen transitions and elements to appear or change.
However, as the system may seem to wait for a long time in some cases, even when a case is clearly identified as a failure, you have the ability to configure the wait time using the Wait policy setting. Wait policy can be set in the Advanced settings tab of the panel where the test content is configured. Three different values are available.
Put emphasis on stability | If you encounter an issue, for example, if an element to be operated cannot be found or the confirmation command fails, it will wait while attempting to retry for a maximum of 10 to 30 seconds (the length of time depends on the problem type). This value is set to the default value in the batch execution settings. This value is also used when no value is specified in the Web API or when the test is run from the command line. |
Standard | If a problem occurs, it will wait for approx. 10 seconds while retrying. This value is set to the default value on the test case creation screen. |
Stop on error immediately | If a problem occurs, it will wait for approx. 5 seconds while retrying. |
- If you wish to set a longer wait time, such as 60 seconds, for individual operations rather than for the entire test, set conditions while using the command "Wait until ~~" .
- The behavior of “Put emphasis on stability” is the same as before MagicPod 0.76.0 (before adding the Wait policy function).