perakerberg
13 years agoOccasional Contributor
Assertion test step - GetData
The new assertion test step is a great idea! It fits very well into my effort of trying to keep a Given-When-Then style of test steps.
However, I ran in to some trouble that someone might be able to help me with.
When I added a new assertion step to assert the contents of a soap response, I used the "GetData" function to set the expected value.
I pointed to the property of another testcase.
In the expected field, the syntax appeared as: ${MyTestStep#Myproperty}
But, when running the assertion, it doesn't seem to parse the value of the property, it compares the actual value against the "${MyTestStep#Myproperty}" value.
So, the value of ${MyTestStep#Myproperty} matched, but the string "${MyTestStep#Myproperty}" clearly does not.
Am I doing something incorrectly or is this a bug?
Thanks again for a great product and this awesome new feature.
Keep it up!
However, I ran in to some trouble that someone might be able to help me with.
When I added a new assertion step to assert the contents of a soap response, I used the "GetData" function to set the expected value.
I pointed to the property of another testcase.
In the expected field, the syntax appeared as: ${MyTestStep#Myproperty}
But, when running the assertion, it doesn't seem to parse the value of the property, it compares the actual value against the "${MyTestStep#Myproperty}" value.
So, the value of ${MyTestStep#Myproperty} matched, but the string "${MyTestStep#Myproperty}" clearly does not.
Am I doing something incorrectly or is this a bug?
Thanks again for a great product and this awesome new feature.
Keep it up!