My Oracle Support Banner

Impossible Determine What AssertionCount Mismatch Occurred During Unit Testing (Doc ID 1955981.1)

Last updated on APRIL 23, 2019

Applies to:

Oracle SOA Suite - Version to [Release 11gR1 to 12c]
Information in this document applies to any platform.


On : version, BPEL Service Engine

When creating a unit test for a BPEL component you can specify an assertion count, like:

<bpelTest componentName="QueryPrintJob" xmlns="">
    <assertActivityExecuted activityName="callbackTimeout" executionCount="1"/>
    <assertActivityExecuted activityName="callbackFautVar" executionCount="0"/>

When the unit test is run in FWM EM you get a list of passed and failed tests, where it mentions an Activity Execution count mismatch.  

There's no way to know what activity assertion count mismatch occurred, nor where it happened in the BPEL flow.  





To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.