AMF session credentials are not instantiated with Virtual Us
Description: When using loadUI to generate Virtual Users to run a soapUI runner, all VU's are using the same AMF session credentials set in the testCase Options.
Expected result:
"It's important to note that each Virtual User that passes a soapUI Runner gets its own isolated copy of the soapUI TestCase, but actually shares the rest of the soapUI Project with all other VUs running a soapUI TestCase belonging to the same soapUI Project. This means that you should avoid writing to TestSuite or Project Properties, as they are shared between all VUs and will likely cause a ConcurrentModificationException, if not synchronized."
Actual result: AMF Session Credentials are shared between Virtual Users.
Steps to Reproduce:
1. Create a groovy testStep that sets the the AMF Session credentials.
2. Make an AMF Request that creates a database object the "belongs" to the current AMF Session credentials (e.g. cant be accessed by other AMF Session credentials.
3. Create a delay testStep.
4. Make an AMF request that attempts to access the object in step 2.
5. Create a loadUI soap Runner that uses a fixed rate generator to create users at such a rate that a new user is generated during the delayStep.
Notice: Step 4 will fail because the credentials no longer match.
Expected result:
"It's important to note that each Virtual User that passes a soapUI Runner gets its own isolated copy of the soapUI TestCase, but actually shares the rest of the soapUI Project with all other VUs running a soapUI TestCase belonging to the same soapUI Project. This means that you should avoid writing to TestSuite or Project Properties, as they are shared between all VUs and will likely cause a ConcurrentModificationException, if not synchronized."
Actual result: AMF Session Credentials are shared between Virtual Users.
Steps to Reproduce:
1. Create a groovy testStep that sets the the AMF Session credentials.
2. Make an AMF Request that creates a database object the "belongs" to the current AMF Session credentials (e.g. cant be accessed by other AMF Session credentials.
3. Create a delay testStep.
4. Make an AMF request that attempts to access the object in step 2.
5. Create a loadUI soap Runner that uses a fixed rate generator to create users at such a rate that a new user is generated during the delayStep.
Notice: Step 4 will fail because the credentials no longer match.