| Unhandled wrote: |
|---|
The problem with your approach is that even if you do access the property, it is dynamic and your UUID will be different each time you read the value of the property.
...
Instead you might want to replace your Properties test step with a Groovy test step (alternatively, use the Setup Script of the Test Case). In the Groovy script, generate your UUID and then store the UUID to a TestCase scope property. Each time your test case executes, a new UUID will be generated. Then future test steps may access this static test case level property. |
It was very helpful, thanks a lot!
