Have you tried this snippet? This is what I have used in the past to get the current test step name.
def teststepName = context.testCase.getTestStepAt(context.getCurrentStepIndex()).getLabel() return teststepName;
Hello msiadak,
Thank you so much for your fast reply.
My DataGen testStep name is "MyDataGen".
My SOAP operation testStep name is "checkAccessControl".
It contains: <context>${MyDataGen#context}</context>
The 'context' property of the MyDataGen DataGen TestStep is of type Script/READ and contains this:
def teststepName = context.testCase.getTestStepAt(context.getCurrentStepIndex()).getLabel()
return teststepName;
Upon execution of the checkAccessControl testStep, the variable evaluates to MyDataGen as seen in the Raw tab:
<context>MyDataGen</context>
I was in a hurry to come to the office this morning to test your suggestion :-(
Unfortunatelly, this does not address my issue.
zorglups: Can you show me a screenshot of what your tests look like? What SHOULD be shown in the <context></context> element?
Well... Yes and no.
But first : A big thank you to @msiadak for his time spent on trying to understand my case and propose something.
I will try to explain my challenge.
Each soap operation has an xml node <dossier></dossier>
I wanted my user to be able to define somehow a specific dossier for each operation, without modifying the operation itself.
This dossier node should be set to :
Still with me ;-)
Well. The solution proposed by groovyguy did not help me because the Groovy script is executed from the script part of a DataGen Test Step. I always got as "TestStep name" the name of the DataGen test step although the variable substitution was made in my test step "operation1".
I then tried another route, mainly because this project will be used as a template and I can't afford having to correct my future Groovy bugs in plenty DataGen Test Step duplicates.
My current route is to implement this in an external Groovy Library.
Here below is a dump of what I tried so far, hoping this may save some hours to others:
package mypackage
class MyClass
{
def static hello()
{
return "hello world!"
}
}
Now, my next steps will be to implement the logic to access the TestSuite property "dossier".
I plan to have a TestStep of type "Properties" containing:
This Properties TestStep could be autogenerated by the TestCase setup script amongst other things.
To be able to read the TestCase property related to the current TestStep name (or better based on the real soap operation name), I still had to determine programmatically the Current TestStep name...
I was therefore back to the beginning ;-)
I found that I can access to the current TestStep context by passing the context object when calling my class method. Same goes to be able to log messages, one need to pass the log object.
Here is an example:
package mypackage
import com.eviware.soapui.SoapUI
class MyClass
{
def static getCurrentStepName(log, context)
{
String currentStepName = context.getCurrentStep().getLabel()
log.info(currentStepName)
return(currentStepName)
}
}
To fill my dossier with the current TestStep name, I can call:
<dossier>${=mypackage.MyClass.getCurrentStepName(log,context)}</dossier>
Well. This is far from finished but I wanted to give some feedback to groovyguy
I will be 2 weeks off starting in a few minutes and it was better to have a dump of what I found before going on holidays anyhow ;-)
Here are a few links that helped me a lot :
https://support.smartbear.com/readyapi/docs/testing/scripts/library.html
https://support.smartbear.com/readyapi/docs/configure/logs.html
http://www.ou-ryperd.net/soapui.html
https://www.soapui.org/extension-plugins/old-style-extensions/developing-old-style-extensions.html
