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

What is BPEL Unit Testing

What is BPEL Unit Testing

Create individual B-unit test cases manually, or save each simulation path you run as a B-unit test file.
BPEL unit (B-unit) testing is a framework that tests BPEL processes in the Process Server engine. B-unit testing validates process execution of invokes, receives, and replies. You can use B-unit testing to perform automated regression tests on processes.
When a B-unit test runs, the following steps occur:
  • The SendMessage command sends XML data to process. You provide this data as part of editing or generating a B-unit test.
  • The response comes back from the process
  • An assert expression determines what the response must have
  • The result is compared to the assert
An effective test is to compare entire chunks of XML to see the parts that don't match.
You can create individual B-unit test cases manually, but it is recommended that you save each simulation path you run as a B-unit test file. You can then rerun files as needed as you refactor your process. Readily available B-unit tests make it easy for you to check whether a component of your process is still working properly.
You can design unit tests to produce test cases that cover all paths through a process so you can test various scenarios. You can save a group of files into a suite, or suite of suites, to rerun. You can run B-unit tests outside of Process Developer, as part of your automated build procedures.
For details, see:


Updated March 30, 2020