Ramiro Martinez admin

About

Username
Ramiro Martinez
Joined
Visits
453
Last Active
Roles
Admin, Staff
Points
40
Posts
46
Badges
5
  • Setting Project File Format Without GUI

    SOATest supports three different file formats for tsts.

    Normally, this configuration is made through the SOATest GUI Preferences:
    Parasoft>Preferences>MISC>>> Save Settings>Project File Format

    Normally, it is best to leave the default Compressed XML format because of the overall effectiveness of the format, https://docs.parasoft.com/display/SOAVIRT9103/Forward+Compatibility

    But if your team requires a different format, please see below.

    For use cases where it is needed to quickly change this feature for many machines or possibly headlessly, then you can change the SOATest Workspace preference file directly.

    The Preference file can be found in the workspace's .metadata folder.
    To change the File format, make one of the following changes to the file:
    ${SOA/Virt_workspace}.metadata.plugins\org.eclipse.core.runtime.settings\com.parasoft.xtest.common.eclipse.core.web.prefs"

    For XML add the property as follows:misc_test_file_format=1

    For Compressed XML completely remove the property:misc_test_file_format=
    Compressed XML is the default File format for SOA/Virt 9.10, therefore a property is not necessary.

    For Binary add the following property:misc_test_file_format=0

    With this information, you can create a simple command for terminal to quickly make the change.
    For example:
    echo "misc_test_file_format=1" >> "C:\Users\rmartinez\parasoft\soavirt_workspace\.metadata\.plugins\org.eclipse.core.runtime\.settings\com.parasoft.xtest.common.eclipse.core.web.prefs"

  • Integrating SOATestcli with Jenkins

    INVOKING SOATESTCLI THROUGH JENKINS
    Navigate to the Jenkins Dashboard and create a New Item to create your automated test case. Once named and created click the drop-down near the Name of your test Item.

    Next Add a new "Execute Windows batch command" Build Step

    Input your SOAtestcli commands:

    Here is an example CLI command:
    Here’s a sample .bat script I ran in Jenkins:
    "C:\Program Files\Parasoft\SOAtest\9.9\soatestcli.exe" -config "user://Example Configuration" -data
    "C:\Users\kholland\parasoft\Jenkinsworkspace993" -resource
    "\TestfromWSDL_Jenkins\testfromwsdl.tst"

    Once your script is added you can test this by running the Build Now feature from the Dashboard.

  • Re: Can a Proxy be set to go to priimary Real endpoint and Failover to secondary Virtual Asset?

    Hi Curtis,

    Yes, this can be done with a message proxy.
    You would create a message proxy and configure a Secondary Connection:

    The fail over triggers when the proxy receives a Error status code 4XX or 5XX.

    Clip of the Virtualize user guide in regards to this feature:

  • Re: How to use system properties feature in CTP??

    Hi Rahul157,

    The System properties are specifically for configuring the Eclipse and internal Parasoft configurations for SOATest and Virtualize instances. These settings are not needed in CTP, therefore a localsettings file is not necessary or available for CTP.

    If you would like to configure CTP settings, you would deploy a CTP instance, add a license, and navigate to the "Administration" drop-down for the configurations webpages.

  • Re: Accessing JSON data bank from Jython

    Hi aa_dfw,

    You can save the values in to a test suite variable and then using the Parasoft api methods:
    context.getValue("variable_name") and context.setValue("variable_name","new_value"); to pull and set the new values.

    Example script:
    import com.parasoft.api.*;

    public void exampleScript(Object input, ExtensionToolContext context){
    
        //Application.showMessage(string) 
    
        //This is grabbing the variable x(If the varible exist) from the test suite variables and displays it in the console window. 
        Application.showMessage(context.getValue("x"));
    
        //This will set a new value for x test suite variable named x
        context.setValue("x","1000");
        Application.showMessage(context.getValue("x"));
    
        //This will print out the input in this example the input was set in the extension tool
        //If chaining from another tool such as a messaging client the output of the tool will be the Object input
        Application.showMessage(input.toString());
    }