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

Creating a B-unit Ant Script

Creating a B-unit Ant Script

Use the following procedure to create a B-unit Ant script:
  1. Ensure your orchestration projects contains one or more B-unit tests or suites, as described in Creating a BPEL Unit Test File.
  2. Select one B-unit test or suite and right mouse-click to select
    New > BUnit Ant Script
    .
  3. In the Export B-unit Ant Script wizard, select a folder, such as the
    test
    folder, and enter a filename. Select Next.
  4. Select the B-unit tests and suites to include. You can select multiple tests from multiple projects. Also, after you create the script, you can edit it to add more folders of tests.
  5. Select the B-unit options as desired:
    • Enable Tracing
      . Controls console logging output for B-unit-specific execution commands.
    • Enable Process Logging
      . Controls the amount of process execution data to log. The default is
      none
      . Enabling the checkbox turns on
      execution
      level. If desired, you can manually edit the Ant script to enable
      execution-data
      (execution with data) or
      full
      logging.
  6. Select
    Finish
    to generate the
    filename
    .ant.xm
    l file.
The ant script opens in an editor for you to view or edit. Follow the instructions in the ant script to set the B-unit runtime classpath if you wish to execute this script outside of Process Developer.
You can create a code coverage report when you run a B-unit ant script on the command line. For details, see Generating a Code Coverage Report.


Updated March 30, 2020