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

Running a BPEL Unit Test in Process Developer

Running a BPEL Unit Test in Process Developer

You can run B-unit tests from an Ant script outside of Process Developer or from the B-unit View within Process Developer. For details on command line execution, see Creating and Running a B-unit Ant Script.
You can run a B-unit test in Process Developer by using the Run As command from several locations, including right-mouse clicking on a B-unit test or test suite in the Project Explorer and selecting
Run As > B-unit
.
The B-unit view opens and runs the test. The following examples show a B-unit with a completed test and a failed test:
You can also run one test from a B-unit suite, as described in Creating and Running BPEL Unit Test Suites.
When you run a test the following events occur:
  • The B-unit view opens to show the progress of the test.
  • The Console shows the output of the test. By default, it includes the trace events and the process execution. For details of these events, see Editing a B-unit File.
  • If a test fails, a failure message displays in the B-unit view. For certain test errors, you can double-click on the test that failed, and a Text Compare Editor opens to show actual and expected results.
  • In the Text Compare Editor, the differences between the expected and actual results are shown. You can use the
    Toggle On/Off Normalized View
    to simplify looking for file differences. You can also set a color preference for the Text Compare Editor, as described in Colors and Fonts Preferences.
When the test completes, you can click on an event in the B-unit view to go directly to that section of the B-unit test in the B-unit editor.
In the B-unit view, use the toolbar icons:
  • Show Failures
    . Select this to filter the view to show only tests that fail.
  • Rerun Test
    . Once you run one test, you can rerun it from the B-unit view.
  • Rerun All Failures
    . Rerun failed tests from the B-unit view.
  • History
    . Remembers the last 15 unit tests run. You can select a test from the list based on the name of the B-unit file.


Updated March 30, 2020