Skip to content
Integration between NeoLoad and Worksoft Certify
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
Worksoft.Interfaces.NeoLoad.wsTransferToNeoLoad/wsTransferToNeoLoad
screenshots
.gitignore
LICENSE
NeoLoad-init.map
README.md
Worksoft.Interfaces.NeoLoad.sln

README.md

Worksoft Logo

NeoLoad Integration for Worksoft Certify

Overview

C# extension to integrate Worksoft Certify with NeoLoad for Script maintenance. It allows you to interact with the NeoLoad Design API to convert an SAP GUI or Web Worksoft Certify Process to a NeoLoad User Path or update an existing one.

Property Value
Maturity Experimental
Author Neotys
License BSD 2-Clause "Simplified"
NeoLoad Licensing License FREE edition, or Enterprise edition, or Professional with Integration & Advanced Usage
Supported versions Tested with Worksoft Certify 10 and NeoLoad from version 6.6.0 (version 32 bits for SAP GUI)
Download Binaries See the latest release

Setting up the NeoLoad Integration for Worksoft Certify

  1. Download the latest release

  2. In the Navigation pane, click Interfaces. In the Interfaces Summary pane, right-click the Interfaces node, then Import and select the neoload-interface.xml file from the release.

Import NeoLoad interface

  1. Unzip the file wsTransferToNeoLoad.zip in a folder named NeoLoad in the directory Worksoft\Certify\Interface Client\Worksoft\wsTest directory of the Worksoft Certify installation directory (for example: C:\Program Files (x86)\Worksoft\Certify\Interface Client\Worksoft\wsTest\NeoLoad).

  2. Unblock wsTransferToNeoLoad.dll (Right click the DLL > Properties and tick Unblock).

Unblock

  1. Register the Assembly for COM interop by executing the following command as Administrator: regasm.exe /codebase wsTransferToNeoLoad.dll Executable regasm.exe can be found in %SystemRoot%\Microsoft.NET\Framework\v4.0.30319.

  2. Edit the file Worksoft\Certify\Interface Client\Worksoft\wsTest\wsTest.exe.config in the Worksoft Certify installation directory, and add the following node inside the configuration node:

    <runtime>
        <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
          <dependentAssembly>
            <assemblyIdentity name="Microsoft.Data.OData" publicKeyToken="31bf3856ad364e35" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-5.8.4.0" newVersion="5.8.4.0" />
          </dependentAssembly>
    	  <dependentAssembly>
            <assemblyIdentity name="Microsoft.Data.Edm" publicKeyToken="31bf3856ad364e35" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-5.8.4.0" newVersion="5.8.4.0" />
          </dependentAssembly>
    	  <dependentAssembly>
            <assemblyIdentity name="System.Spatial" publicKeyToken="31bf3856ad364e35" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-5.8.4.0" newVersion="5.8.4.0" />
          </dependentAssembly>
        </assemblyBinding>
    </runtime>
  1. Relaunch Worksoft Certify.

Warning: You might need to launch both Certify and SAP Logon as administrator in order to convert the Certify Process to NeoLoad.

Modify the Worksoft application to allow the conversion with the NeoLoad interface.

  1. In the Navigation pane, click Applications.

  2. In the Applications pane, on the version of the application that contains the process that you want to convert to a NeoLoad User Path, right click and select Edit.

Edit Application

  1. In Edit Application Version window, select the NeoLoad interface in the Interfaces section and click OK.

Select NeoLoad

  1. Right click again on the version and select New Window.

  2. In the New Window dialog, enter a Name, a Physical Name and select the NeoLoad Interface. Click OK.

Add Window

Modify a Worksoft Certify Process to convert it to a NeoLoad User Path.

  1. In the Navigation pane, click Processes.

  2. In the Applications pane, select the process that you want to convert to a NeoLoad User Path, right click and select Edit.

  3. At the beginning of the Process, add a new Step associated with the NeoLoad window with the StartRecording Action.

Start Recording

  1. If identification is required by the NeoLoad API, use the apiKey parameter.

  2. Enter the User Path name, you can use the Process Name built-in System Variable.

  3. Enter the record Mode:

    • SAP GUI & WEB to record both SAP GUI and the Web traffic (the System proxy will be updated).
    • SAP GUI to record only SAP GUI.
    • WEB to record only Web traffic (the System proxy will be updated).
  4. At the end of the Process, add a new Step associated with the NeoLoad window with the StopRecording Action.

Process

Tip : Once the conversion is done, you can comment the Steps associated with the NeoLoad interface with the Comment button.

Comment

Running the process will transfer it to NeoLoad.

Important: if UAC is enabled on Windows, Worksoft Certify and SAP Login need to run as Administrator to transfer a SAP GUI Process to NeoLoad.

Add NeoLoad Transactions

In the Edit Process dialog, add a new Step associated with the NeoLoad window with the StartTransaction Action each time you want to start a NeoLoad Transaction.

Transaction

Advanced Configuration

StartRecording

The advanced parameter of the StartRecording Action allows defining the following options:

  • designApiUrl: The URL of the NeoLoad design API, by default it is http://localhost:7400/Design/v1/Service.svc/.
  • updateUserPath: Used to automatically update the User Path with the same name. Default value is "true".
  • isHttp2: Used to record or not HTTP/2. Default value is "true".
  • addressToExclude: List of addresses separated by a semicolon. Requests and responses through these addresses will not be taken into account by NeoLoad when recording (for example: 10.0.0.5:7400;10.3.1.15;localhost:9100)
  • userAgent: Used to specify the user agent.

If you want to define multiple options, the options must be separated by a carriage return. For example:

Advanced

StopRecording

The advanced parameter of the StopRecording Action allows defining the following options:

  • frameworkParameterSearch: Default value is "true".
  • genericParameterSearch: Default value is "false".
  • deleteRecording: Default value is "true".
  • includeVariablesInUserPathUpdate: Default value is "true".
  • updateSharedContainers: Default value is "false".
  • matchingThreshold: Default value is "60".

ChangeLog

  • Version 1.0.0 (February 18, 2019): Initial release.
You can’t perform that action at this time.