Forum Discussion

Bryan_Nahrwold's avatar
Bryan_Nahrwold
Contributor
16 years ago

Global ENDPOINT for manual testing

I have need to execute test cases of individual soap operations manually to verify behavior.  As a result, when I change an endpoint, I have to go to each operation in each test case and point to the new one.  Likewise I have some other properties that need to be defined once and accessed in multiple locations.

I ended up using this for the endpoint:

https://${EndPointProperty#ENDPOINT}:8092/LicensingService/
I tried first to define a Test Property for the LicensingServiceJBIPortBinding TestSuite by highlighting the TestSuite, then highlighting  the "Test Properties" tag, and creating an ENDPOINT property with a value something like 192.168.2.1.  I then tried the following endpoint entry:

https://${LicensingServiceJBIPortBinding TestSuite#ENDPOINT}:8092/LicensingService/
for the endpoint for each testcase.  The operations would all fail with:

Error getting response; java.net.ConnectionException: Connection refused: connect.

I then changed this using an Properties File:
EndPointProperty#ENDPOINT which resulted in an endpoint configuration of:
https://${EndPointProperty#ENDPOINT}:8092/LicensingService/
Where this property file was read from a configuration file containing:
ENDPOINT=192.168.2.1

This works but I can only do this by defining an EndPointProperty property step in each testcase.  Because I am reading from disk, a change in directory means I have to change each ane every EndPointProperty property step for the location of the file to read.

I would really like to be able to define a property value in one location, and then use it across individual test cases.  In fact, I would really like to be able to use this across multiple projects.

Is there a  way to create a properly value that can be accessed from any test case, in any test suite, in any project, and done in a way so that changes to that property and/or the file location of the property value can be made in one location?

Thanks,

Bryan

11 Replies

Sort By
  • omatzura's avatar
    omatzura
    Super Contributor
    16 years ago
    Hi Bryan,

    If you want to define the endpoint globally (accessible from all projects), do this in the "Global Properties" tab in the Preferences dialog. The refer to the property with the property-name only, ie if you define a property named "TheEndpoint", refer to it with ${TheEndpoint}

    If you define properties at the Project, TestSuite or TestCase level, you access them with a scope prefix;

    ${#Project#TheEndpoint}

    or

    ${#TestSuite#TheEndpoint}

    etc.. This means that you can not refer to properties in other Projects or TestSuites (this is intentional).

    When defining properties globally, you can override them with a properties file from the command-line as described at http://www.soapui.org/userguide/propert ... _in_soapUI

    Hope this helps!

    regards,

    /Ole
    eviware.com
  • Bryan_Nahrwold's avatar
    Bryan_Nahrwold
    Contributor
    16 years ago
    Yes, thank you.  That helped immensely.  However, I have on other similar issue not resolved by this suggestion.  I have to transfer a session ID from a TestCase for one Soap Operation to TestCases for soap operations in differnt WSDL components.
    The setup looks like this:
    Authenticate with SESSION ID      (project)
    AuthMgrHttpsBinding                    (Interface)
    AuthMgrHttpsBinding TestSuite
      authenticate TestCase
        authenticate                              (operation)
        SESSIONIDTransfer
        SESSIONIDProperty

    SESSIONIDProperty contains a value SESSIONID

    I have numerous other test cases that I wish to execute manually that require this SESSIONID.  An Example:

    LicensingService with SESSION ID (Project)
    LicensingServiceJBIPortBinding    (Interface)
      LicensingServiceJBIPortBinding    (TestSuite)
      setProxyInfo TC                          (TestCase)
        setProxyInfo                              (operation)

    How do I get the SESSIONIDProperty#SESSIONID from the one project to the setProxyInfo TC testcase where it can be referenced within the setProxyInfo operation?

    Curerntly I am using "Save to" and "Load to" on the properties.  Not only is this very slow, but I can't use property expansions in the "Save to" and "Load to" fields, and these fields will not find a file in the current directory if no path is specified.  I have about 50 TestCases I wish to run, individually.  This means I need to create 50 copies of these properties and if I want to move to another directory, I have to update all 50 properties (51 if you count the source operation property).

    Thanks,

    Bryan
  • omatzura's avatar
    omatzura
    Super Contributor
    16 years ago
    Hi,

    maybe you can create a property-transfer that transfers the session-id to a project-level property, which you can then access from your other testcases?

    regards,

    /Ole
    eviware.com
  • Bryan_Nahrwold's avatar
    Bryan_Nahrwold
    Contributor
    16 years ago
    Thank you.  Sounds like a great idea!  Unfortunately, it is not working.

    I created property SESSIONID in the project "LicensingService with SessionID".  I then modified my Property transfer to transfer the Session id to the target "LicensingService with property SESSIONID. 

    I then modified one of my TestCases in the project, set ProxyInfo, to use the property expansion: "${#LicensingService with SessionID#SESSIONID}" (without the quotes).  It fails with a security exception.

    As a test, I created a Property Transfer and a property and placed these in setProxyInfo, even though the oepration is failing, my test property value SESSIONIDTEST is receiving the session id placed in the project property SESSIONID.

    This leads me to believe there is something wrong with the property expansion:

    ${#LicensingService with SessionID#SESSIONID}

    I also tried:

    ${LicensingService with SessionID#SESSIONID}

    What am I doing wrong?

    Thanks,

    Bryan
  • omatzura's avatar
    omatzura
    Super Contributor
    16 years ago
    Hi Bryan,

    the property-expansion should be just

    ${#Project#SESSIONID}

    ie the "#Project#" tells soapUI in which scope to find the property..

    any better!?

    /Ole
    eviware.com
  • Bryan_Nahrwold's avatar
    Bryan_Nahrwold
    Contributor
    16 years ago
    No, unfortunately, this does not seem to help at all.  I find this very frustrating.  I am sure I am not coying the information incorrectly because I an selecting the Project name and the property, renaming, (then just copying the text instead of renaming) and creating the property transfer.
  • Bryan_Nahrwold's avatar
    Bryan_Nahrwold
    Contributor
    16 years ago
    I have sent a subset of what I am testing with a single value that I am trying to transfer and then retrieve from a TestSuite Property.  I have sent this in an email message to your  email account.

    If I execute authenticate TestCase, then copy the sessionID to activateLicense and execute with the code:


     

       
         
            05a73758-389a-4834-aaa6-969aa4ac7f66
         
       
     

     
         
            A201_5
            lab
            0
         
     


    It works properly.  If I then replace the hardcoded sessionID with:

    ${#licenseTestSuite#SessionID}

    and execute the two testcases again, I get the error:

     
         
            soapenv:Server
            java.lang.SecurityException: Malformed Identifier element - level 1
         
     


    Security errors are only returned if there is a problem with the SessionID.
    If I replace the Property Expansion with  a reference to a local Property such as: ${Property#SessionID}, it works fine.

    Why can't I get Property Expansions to TestSuite Properties to permit transfer of data between testCases?
  • omatzura's avatar
    omatzura
    Super Contributor
    16 years ago
    Hi!

    please replace

    ${#licenseTestSuite#SessionID}

    with

    ${#TestSuite#SessionID}

    and make sure the SessionID property is defined in the containing TestSuite (and not another one)..

    Does that help?

    regards!

    /Ole
    eviware.com
  • Bryan_Nahrwold's avatar
    Bryan_Nahrwold
    Contributor
    16 years ago
    Yes, that works.  However, I don't understand why I would use:

    ${#TestSuite#SessionID}

    instead of:
    ${#licensingTestSuite#SessionID}

    when the test suite is actually named licensingTestSuite.  Can you explain?