Int4 Suite: Automatic test case creation using IDocs Robot

Int4 Suite IDoc Robot is a functionality thanks to which test case creation process is much faster than before. There is no need to manually search for IDoc messages for a specified interface, sender partner or receiver partner.

How to access the Test Case Robot for IDoc

To access the Test Case Robot for IDocs open the Test Case Robot for IDocs tile.

How to configure the Test Case Robot for IDocs

Steps:

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

RFC connection for reading IDocs is determined based on combination of Environment from selection screen and System Line from Automation Object.

Open

2. In the next section, called Message Selection Criteria, you can specify all the needed criteria which the Robot should consider during message selection. 
   Please note that first, you must complete the configuration under Open Extended Configuration:
   
   

   Open

   

   In the beginning, the list will be empty. To import IDocs from the remote system, click on Import from rem. system button. 
   
   

   
   Enter additional criteria, like Environment and System Line.
   In addition specify the Analysis Start Date and Direction of the IDoc.
   Based on the Analysis Start Date the robot will find all variations of the IDoc messages based on the IDoc Basic Type, IDoc Message Type, IDoc Direction, IDoc Extension and IDoc Sender and Receiver Partner.
   
   

   Select required rows and transfer entries to Robot by Transfer selected button. You may import IDoc interfaces multiple times. The results will be appended to the current robot configuration list.
   
   As a next step, we need to specify an automation object for imported entries. We can do it either manually or automatically by click on the button Propose Automation Objects.
   
   

   
   This function will look for existing automation objects for particular service Interfaces and their namespaces. Result:
   
   

    

   
   Here, Robot found an existing automation objects, which meets the criteria.
   
   

3. Please notice that if there is more than one automation object in the Int4 Int4 Suite database for the message type and basic type, the system will propose only the first one. If the proposal is not correct, please change it according to your needs.

   Suppose the system doesn't find an existing automation object for selected Interface & Namespace. In that case, you can automatically create them by clicking on the Generate Object IDs button.
   The system will propose the automation object names for interfaces that are not configured yet in Int4 Int4 Suite:
   
   

   You can keep names proposed by Int4 Suite or overwrite them with your names, for example, based on WRICEF Numbers.

4. You may set a folder in which test cases should be created:
   
   

   
   In a column Level 1 Subfolder Name (1), 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 (refer to point 7).

   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 subfolder will be located either as a child of Level 1 SubFolder (1) or, if you won't specify the main folder, under the folder entered in the main screen (please refer to point 7).
   
   

5. Next, in the main IDoc Test Cases Robot you should specify a period for which Robot should search IDocs in the remote system
   
   

   
   
   

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

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

   • Log Level Debug - you can select this option to obtain log messages during execution.

7. The last section covers information about Test Case Creation Parameters:
   
   
   

   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 could select a checkbox to force the creation of an automation object during execution (checkbox Create Automation Objects if ID from Extended Configuration is missing).
   
   

8. 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. In our example, we want to create folders for each combination of the Message Type/Basic Type/Extension and IDoc Sender and Receiver, so that pattern will look like this:
   
   
   

   
   For more information about possible Search Patterns, please open the F1 help.
   
   

9. Enter additional data:

   • 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 for a specific IDoc type there are a lot of messages - in that case, you can select this option to pick up messages randomly instead of picking ten messages in a row.

   
   And at the end, fill in the Name Pattern for test cases created by Robot (you can also use the F1 help for more information). 
   
   

10. After you specify all the criteria, execute the report.
    IDoc Robot automatically fetched messages from your remote system and created a folder with test cases based on criteria from the selection screen. You can find a summary at the end of the list:
    
    

    
    
    

11. When you open Int4 Int4 Suite Cockpit from the API Tester tiles, you should find test cases in the specified folder with subfolders for each interface like this: