14 years ago
LoadUI/SoapUI TestCase Property Scope Problem
I think I've been over this about every which way.
I need to be able to spit data out into a table, as here: http://www.loadui.org/Load-Testing-soap ... rty-values
Looks like a few other people have had the same issue:
(he was unable to reproduce later) - viewtopic.php?t=7284
(He found a workaround in assigning to context) - viewtopic.php?t=7218
Unfortunately, my problem isn't going away, and the workaround from storing to context isn't doing it for me (I need to get it into loadui, and right now that's not happening properly). I'm attempting to use loadui beta now, but I'm not holding out a lot of hope. Seems like I should be able to do exactly what's in the documentation, but I don't know how that was able to be done. The sessions in the screenshot would show duplicates, and have missing sessions IDs from the test runs, at any volume above 1 concurrent request.
Reproduce via the following:
I need to be able to spit data out into a table, as here: http://www.loadui.org/Load-Testing-soap ... rty-values
Looks like a few other people have had the same issue:
(he was unable to reproduce later) - viewtopic.php?t=7284
(He found a workaround in assigning to context) - viewtopic.php?t=7218
Unfortunately, my problem isn't going away, and the workaround from storing to context isn't doing it for me (I need to get it into loadui, and right now that's not happening properly). I'm attempting to use loadui beta now, but I'm not holding out a lot of hope. Seems like I should be able to do exactly what's in the documentation, but I don't know how that was able to be done. The sessions in the screenshot would show duplicates, and have missing sessions IDs from the test runs, at any volume above 1 concurrent request.
Reproduce via the following:
- Create a test case that has:
- a groovy step, generates a random number between 1 and 10000, and stores it to both a variable in the current runner context, and a test case property, as well as returning the result from the step.
- a delay for 1000 ms
- a property transfer from the result of the groovy step, to the test case level (in a second property)
- another delay for 1000 ms
- a groovy script that pulls the random number from the runner context, and assigns it to the test case level (in a third property) then pulls all test level properties, and logs them out.
- Run the test case in soapui (even as a load test with 100 threads/VUs)
- Results in the log being filled with rows of properties that match. Each set of properties is an identical trio, and no duplicates (or at least only 2 in 10001)
- Run the test case in loadui (as a load test with 3 requests per second), and dumping out the properties via the method above into table log.
- Results in most of the properties being different on the same line. Also results in duplicates appearing in clumps (across lines), since it's pulling from a global test case property across threads/testcaserunners.
Edit: Editing to check the "notify me" box.