Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The Int4 Suite webMethods Robot is a report which simplifies and accelerates the mass test case creation process. With the Robot, you have the option to create a large number of test cases for different webMethods flows at once.

...

To access the Test Case Robot for Boomi open the Test Case Robot for webMethods tile.

TO DO Add screenshot once webMethods Tile is available

How to configure the Test Case Robot for webMethods

Panel
panelIconIdatlassian-info
panelIcon:info:
bgColor#FFFAE6

Please note that using Int4 Suite with webMethods requires additional, customer specific, webMethods developments. These will have impact on the naming convention and specifics of webMethods Service Interface / Process name.

  1. In Environment Selection, please select the environment from which you want to create test cases:

    Image Modified

  2. In the next section, called Message Selection Criteria, you can specify all the criteria considered by Robot during message selection.

...

  1. Image Added


    Prerequisite for Robot usage is the completion of Extended Configuration:

    Extended Configuration contains a list of processes scanned by Robot, including mapping to Int4 Suite Automation Objects and additional configuration options. You can add interface names in the “Service Interface Name” column.

    Image Modified
    1. After listing the processes, there are three options to configure the Automation Objects:

      1. Manually - Fill the Automation Object Name

      2. Propose Automation Object - The program will look into the Int4 Suite Automation Object Database for already existing Process configuration. Based on the name, it will populate the Int4 Suite Automation Object.

      3. Generate Object IDs - If the system doesn’t find existing automation objects, you can create them automatically by clicking on the Generate Object IDs button.
        The system will propose the automation object names for interfaces that are not yet configured in Int4 Suite. 
        You can keep names proposed by Int4 Suite or overwrite them with your names, for example, based on WRICEF Numbers.

    2. Lastly, in the Extended Configuration, you may set a folder in which test cases should be created:

      Image Modified


      In a column Level 1. Subfolder Name, you can enter the main folder where test cases created by Robot should be located. It’s possible to leave this column empty and forward this task to Robot.

      You can also specify a subfolder name - Test Cases Folder (2). In this case, Robot will create test cases in a new folder from this column.It means that this test case folder will be located either as a child of Level 1 Subfolder Name or - if you won’t specify the main folder here - under the folder entered in the main screen.

    3. Save this configuration, and you can go back to the main screen.

  2. You can filter the Extended Configuration object list providing either Int4 Suite Automation Objects or Process Names.

  3. Specify a Time Range for message search.

    Image Modified

  4. In the next section, you can specify Execution Parameters:

    • Image Modified

      Test Run - Robot will search for messages and list out the results without creating any test cases

    • Log Level Debug - this option enables detailed logging, which might be helpful during troubleshooting.

  5. The last section covers Test Case Creation Parameters:

    Image Modified

    • Firstly, specify Target Folder where test cases created by Robot should be located (use the F4 input help if needed).
      Suppose you didn't specify Automation Object ID in Extended Configuration, or Robot won't find a given object. In that case, you can select a checkbox to force the creation of an automation object during execution (checkbox Create Automation Objects if ID from Extended Configuration is missing).

    • Define rules about Test Case folders in case folder was not maintained in Extended Configuration. You can ask Robot to search for an existing folder or create a new one using a search pattern. For more information about possible Search Patterns, please open the F1 help.

    • maximum number of test cases per folder (including already existing ones),

    • Select Skip duplicates in the same folder in case you don't want to have more than one test case with the same MessageID,

    • Randomize message selection Suppose there is a bigger number of messages in Dell Boomi, for example, 200. In that case, you can select this option to pick up messages randomly instead of picking ten messages in a row.

  6. After specifying all the criteria, the report can be executed either in the foreground or background.
    Based on the parameters, Robot automatically downloads the messages from the Boomi platform, creates the folders and test cases. 
    After each detailed execution report is presented with information about created test cases.

    Image Modified