Forum Discussion

xavjer's avatar
xavjer
New Contributor
11 years ago

Improving SoapUI TestStep PropertyExpansion

I have two suggestions for the PropertyExpansion

 

1. TestStep expansion

It is currently possible to use this property expansion ${#TestCase#MyTestCaseValue} but this one is not possible yet: ${#TestStep#MyCurrentTestStepValue}

 

2. TestStep expansion by name change

Let's assume my TestStep is called: Step1

It has a parameter with name: Value1

 

So to access it, I currently use: ${#Step1#Value1}

 

Now, when renaming a teststep or cloning it (and giving it a new name), all existing property expansions should also be renamed to reference the new name (In HTTP TestStep for example it should check the endpointURL, the content, the assertions).

 

This could of course be extended to also do this within all TestSteps when a TestCase/Suite/Project name changes, but I think starting with the TestStep only will already have a huge benefit as many of my Steps have a similar layout and I always clone them

3 Replies

  • nmrao's avatar
    nmrao
    Community Hero
    11 years ago
    Isn't both #1, #2 are contradicting? at least for me.
    If I understand right, #1 is not possible from description.

    I think expansion for TestStep does not make sense not all steps does not support custom properties.
    • xavjer's avatar
      xavjer
      New Contributor
      11 years ago

      Well I don't think they are contradicting, these are just two features, some may prefer one more than the other

       

      Implementing both would make the usage very flexible