Forum Discussion

pkiddie's avatar
pkiddie
Occasional Contributor
15 years ago

Delay test step time (if parameterised) is not respected...

I have a fairly specific scenario here, which I'll try and explain -

I have a large parameterised testcase with a number of delay teststeps which I've set to use a 'thinkTime' parameter on the testcase (e.g. ${#TestCase#thinkTime}).

Now, when I run this test case independantly, the delay teststeps are initialised the the value I've set in the thinkTime parameter as expected (in my case, 5000ms)

The problem is, if I set this test case to run as part of a 'Run TestCase' test step in a seperate testcase (as part of a larger scenario), the delay test steps instead default to 1000ms.

Please let me know if you need any more explanation!

Cheers,
Paul

3 Replies

  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    15 years ago
    Hi Paul,

    I have tested this and get the same result as you. This might be a (usability) bug and I have reported it to the soapUI backlog.

    Thanks for reporting this, have a nice weekend!


    /Henrik
    eviware.com
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    15 years ago
    Hi Paul,

    did you try checking the "Ignore Empty Parameters" option in the Run TestCase TestSteps Options dialog?

    regards,

    /Ole
    eviware.com
  • JimL's avatar
    JimL
    Contributor
    14 years ago
    Hi,

    Sorry to jump into this thread, but I think that I've noticed that this problem is even happening when using property expansion in the Delay teststep per your documentation.

    In my case, I'm trying to us the Variance loadtest strategy, and want to limit the number of requests within each 60 second interval, so I have:

    Threads: 5
    Variance: 0 (so constant 5 threads during interval)
    Interval: 60 seconds
    Limit: 120 seconds

    My test case has:

    - Groovy script step (sets up some properties)
    - SOAP request step (sends request)
    - Delay step (${=30000 + 30000*Math.random()})

    It seems like even in this case, the Delay step is always taking only ~1000 msecs (= ~1 second), whereas I expected it to take 30-60 seconds, and I'm ending up with 200+ requests in the 120 second run, rather than something like 10-20 requests in 120 seconds.

    Any feedback on this, or way to make this work yet?

    Jim