Table of Contents

Search

  1. Preface
  2. Welcome to Informatica Process Developer
  3. Using Guide Developer for the First Time
  4. Getting Started with Informatica Process Developer
  5. About Interfaces Service References and Local WSDL
  6. Planning Your BPEL Process
  7. Participants
  8. Implementing a BPMN Task or Event in BPEL
  9. Implementing a BPMN Gateway or Control Flow
  10. Using Variables
  11. Attachments
  12. Using Links
  13. Data Manipulation
  14. Compensation
  15. Correlation
  16. What is Correlation
  17. What is a Correlation Set
  18. Creating Message Properties and Property Aliases
  19. Adding a Correlation Set
  20. Deleting a Correlation Set
  21. Adding Correlations to an Activity
  22. Rules for Declaring and Using Correlation Sets
  23. Correlation Sets and Engine-Managed Correlation
  24. Event Handling
  25. Fault Handling
  26. Simulating and Debugging
  27. Deploying Your Processes
  28. BPEL Unit Testing
  29. Creating POJO and XQuery Custom Functions
  30. Custom Service Interactions
  31. Process Exception Management
  32. Creating Reports for Process Server and Central
  33. Business Event Processing
  34. Process Central Forms and Configuration
  35. Building a Process with a System Service
  36. Human Tasks
  37. BPEL Faults and Reports

2. Designer

2. Designer

Tips on Using Parameterized XSL for Input and Assert Data

Tips on Using Parameterized XSL for Input and Assert Data

You can build efficiency into your B-unit tests in cases where you want to assert a small difference in the same data across multiple tests. The efficiency comes in the form of parameterized XSL.
Consider the following example.
In an XML data file, there is the following element:
<ns:status>CREATED</ns:status>
Instead of creating different XML files, each with a different status value, you can write an XSL file such as:
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:ns="http://schemas.active-endpoints.com/b4p /wshumantask/2007/10/aeb4p-task-rt.xsd"> <xsl:import href="common.xsl"/> <xsl:param name="state"/> <xsl:template match="ns:status/text()" priority="2"> <xsl:value-of select="$state" /> </xsl:template> </xsl:stylesheet>
In the Source view of your B-unit file, you can then add a parameter, such as:
<abu:part href="../data/getTaskInstanceResponse-minimal.xml" name="taskInstance" xsl="../xsl/change-task-instance-state.xsl"> <abu:params> <abu:param name="state" value="COMPLETED"/> </abu:params>
For each B-unit test, you use the same imported data and the same XSL file. You need only change the parameter value to get a different result.


Updated March 30, 2020