Contains Assertion with property
Hi,
I am running sopaUI 4.5.1. I have a test case with serveral HTTP requests. Test simulates logging to web site. I have a contain assertions in step which sends POST request with loggin credentials to verify if user is logged in. I simple check this by looking for property ${#TestCase#username}
When I run this test as functional it works fine.
To be able to simulate more realistic load I add groovy script with such content as the first step in the test case
users = ["patient21200","patient21201","patient21202","patient21203","patient21204"]
testRunner.testCase.setPropertyValue("username", users[context.ThreadIndex])
testRunner.testCase.setPropertyValue("password", users[context.ThreadIndex]+'}')
This leads to the unexpected errors observed from time to time. With test steps I am able to log in but during the loging request property ${#TestCase#username} is changed and assertion fails. This looks like some property isolation problem. I would be grateful for explenation for this problem however in my opinion it is a bug.
Best Regards
Jacek
I am running sopaUI 4.5.1. I have a test case with serveral HTTP requests. Test simulates logging to web site. I have a contain assertions in step which sends POST request with loggin credentials to verify if user is logged in. I simple check this by looking for property ${#TestCase#username}
When I run this test as functional it works fine.
To be able to simulate more realistic load I add groovy script with such content as the first step in the test case
users = ["patient21200","patient21201","patient21202","patient21203","patient21204"]
testRunner.testCase.setPropertyValue("username", users[context.ThreadIndex])
testRunner.testCase.setPropertyValue("password", users[context.ThreadIndex]+'}')
This leads to the unexpected errors observed from time to time. With test steps I am able to log in but during the loging request property ${#TestCase#username} is changed and assertion fails. This looks like some property isolation problem. I would be grateful for explenation for this problem however in my opinion it is a bug.
Best Regards
Jacek
