In a Catchpoint multi-step test (Transaction, Playwright, or Puppeteer), you may come across a test timeout failure - [50107] - Too much time elapsed to run the test - even though the webpage response is lower than the test time threshold. This may be caused by a pause() or waitForNoRequest() exceeding the test time threshold behind the scenes.
Example
Consider a Transaction Test with two steps (Time threshold = 60 seconds / [2 Steps X 30 Seconds per step])
- Webpage Response for Step 1 takes 40 seconds.
- Step 2 can take up to 20 seconds, at which point the overal time threshold is exceeded.
- If Document Complete for Step 2 equals 10 seconds and there is a
pause(10000), the test will reach the 60 seconds time threshold even though the actual test time measures 50 seconds.
There are also some situations where a test will result in this error due to exceeding the time threshold while waiting for Document Complete to occur.
You can change the time-out threshold for the test to mitigate this issue. The options are 5, 10, 20, 30, 60, 90 or 120 seconds per step. Note that any time above the default time threshold may impact point usage.