Forum Discussion
pkitkows
10 years agoOccasional Contributor
Rao,
Thank you for quick response.
How delay will resolve this kind of issue ?
Doesn't occurrence of this issue still be time("luck") randomized ?
I have tried this:
- Test Suite ( Property LIST - contains some entities)
-- Test Case
--- Test Step - groovy script which:
---- get LIST from SUITE
---- take first entity
---- remove first entity from LIST
---- save new LIST on the SUITE level
--- Test step - some REST request based on data from groovy
--- Test step - delay (randomized in range 0-50 ms) -> Added as you suggested
--- Test step - groovy - do loop - jump to the first test step as long as LIST is not empty
Unfortunately, this didn't help at all
I tough that variables on case level are independent when you are using LoadTest, while a variables on the test suite/project level are shared between threads during LoadTEst execution.
Does "PRO" version has some WA/solution ?
Regards,
Piotr
Thank you for quick response.
How delay will resolve this kind of issue ?
Doesn't occurrence of this issue still be time("luck") randomized ?
I have tried this:
- Test Suite ( Property LIST - contains some entities)
-- Test Case
--- Test Step - groovy script which:
---- get LIST from SUITE
---- take first entity
---- remove first entity from LIST
---- save new LIST on the SUITE level
--- Test step - some REST request based on data from groovy
--- Test step - delay (randomized in range 0-50 ms) -> Added as you suggested
--- Test step - groovy - do loop - jump to the first test step as long as LIST is not empty
Unfortunately, this didn't help at all
I tough that variables on case level are independent when you are using LoadTest, while a variables on the test suite/project level are shared between threads during LoadTEst execution.
Does "PRO" version has some WA/solution ?
Regards,
Piotr
Related Content
Recent Discussions
- 2 days agoemoya
- 2 days agoMyBalanceNow