I must be missing something here. I have read through the docs quite intensively and I also tried the suggested code snippets, but when I enter a code-snippet like
def name = testRunner.testCase.testSuite.project.name
into the script assertion entry field and then execute that I get an error "can not call testCase on a null-object". So, the object "testRunner" seems undefined or null.
The other usage that my question was referrring to:
there is the option to define an assertion by using the "Contains" option and then enter a string that has to be contained in the response into the input fields.
These strings can contain "placeholders" like "...${#Project#some_property}..." or "...${#TestCase#other_property}..." etc.. However, that machanism seems to work only with user definable customer properties. If I enter the project property "${#Project#Name}" here or ${#Project#Service} or ${#Project#Endpoint} or any other default property's name) I get an error only. What name or prefix do I need to use for the Project/Test Suite/Test Case/Test Step's default properties?
Hi,
So in terms of why that first snippet deosn't work, what you were missing is that I said to run it from a Groovy script, not a script Assertion, they provide different variables to the script - see the comparison below:
Whereas, the Script Assertion is not run in the context of a test runner hence no testRunner variable (it gets messageExchange instead):
Ok, I think the problem here might be that the syntax for inserting the result of script type expressions is not the same as that for the property expansion syntax that is applied to properties of different scopes - consider the following example:
${=java.util.UUID.randomUUID()}
(also taken from that tricks and tips page, but basically this syntax allows execution of one or more lines of code, can provide more complicated examples if necessary)
Is this what you wanted?
Hope this helps,
Cheers,
Rupert
