Slowing down the whole test

Hi Lowres,

It might not be the best option but one approach you could use is to create a listener file and use a simple end_keyword with a sleep in it, this will add a sleep to every keyword (or use the end_user_keyword or end_library_keyword variations if you prefer). then you can still run locally with no delay and just include the listener that adds the delay when you need it.

Best part of this option is no change to your tests, so when you’ve had the discussion with the security team you can stop including the listener, and in the meantime you can easily turn it on and off as needed.

I’ll be interested to see what other suggestions you get :crossed_fingers:

Dave.