- Last Active
It turned out to be a soatest issue and my lead is going to file a ticket for it.
I'm using context.setValue("xxx", xxx) to set the variable value in my script and I see the variable value is set from logging. It's just not passed to my next soap call somehow. Here is the example for my next soap call trying to use the variable. …
Yes. My test scenario setup tests use datasource value for username and password to get tokens for the regular tests to use. I found the only working workaround for my case is to create a subfolder and put everything (setup tests, tests) under it.
I think it's a bug of the tool. In my test, I use data source and setup tool, the datasource in setup tool always duplicate itsself. And I do see the test runs werid behavior (fail at setup test) many times.
In the screenshot, I don't have any data source defined currently, but in Setup Test, look at the right up corner for the request. It has "Data Source" and shows "TestAccount" in the dropdown. "TestAccount" data source does not actually exist.