Hello Some,
There are a few possible solutions using the approach you have in mind. All of them involve using the Execution Delay test step. A 15 minute delay equates to 900,000 milliseconds, which is what the Execution Delay test step uses. With this you could:
1) Create a data driven test, not really use the data, add a 15 minute execution delay. I would put it as the first step because if the test ever fails it won't reach the last test step thus skipping your intended 15 minute delay
2) A test list won't really work nicely because you can't add the same test more than once to a test list.
3) You could surround the main steps of your test in a Loop, including the Execution Delay. If the test ever runs into an error, it will step the loop and the test.
All the best,
Cody
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Public Issue Tracking
system and vote to affect the priority of the items