Test Your Mappings

Once you complete designing your mappings, you can test them by entering sample content of the message to process in the mapping tester. When you execute the test, output is generated from the sample content.

To test a mapping:

Note:

Custom JavaScript functions cannot be tested.

Two elements are generated when the element is defined as repeating. This is useful for generating payloads containing at least two repeating elements to test for-each loops in the mapper.

1. In the mapper toolbar, click Test.
   The mapping tester appears. The names of the source data structures for your mapping are displayed at the top. Two instances are also generated and displayed for repeating nodes.
   

   
   Description of the illustration mapper_test.png

   
   
2. In the Input panel, you can manually enter the payload, copy and paste the payload, or click Generate Inputs to automatically generate and test the payload. Payloads for scalar parameters are not created.
   
   
   Description of the illustration mapper_gen_inputs.png
   
   

   If your mapping includes multiple source data structures, both names are displayed. Payloads for both sources can be generated.

   Note:

   If the payload is very large, it is not automatically generated and you receive the following error message:

   Payload could not be generated for the ''$SourceApplicationObject'' schema due to excessive size and a lack of system memory

3. Scroll through the input payload and note the following details:

   • Unbounded, repeating elements are displayed multiple times.

   • Schemas of up to 20 levels in depth can be displayed.

   • Random values are automatically generated for payload elements. Based on the data type of the element, the correct values (for example, numerical or string values) are generated.

   • You can manually edit the randomly-generated values, as necessary.

4. Click Execute to generate results in the Target panel.
5. Review the results in the Target panel to ensure that your input payload was processed correctly.
   
   
   Description of the illustration mapper_execute.png
   
   
6. Test your mapping and, as necessary, return to the mapper to make mapping changes, such as changing the XSLT statements or functions used.
7. To clear the Input and Target panels, click Clear.
8. When testing is complete, click Designer to return to the mapper.

   Multiple entries are generated for template parameters. There should be only be one instance of each template parameter. This is the expected behavior. For example, /subscriptions/{SubscriptionPUID}/child/products/{SubscriptionProductPUID} generates repeating elements for template parameters SubscriptionPUID and SubscriptionProductPUID.