BPEL Test Exceptions ORABPEL 20000 - 20299

BPEL Test Exceptions ORABPEL 20000 - 20299
Test Exceptions 20000 - 20299

ORABPEL-20000
severity: 10
type: error
name: Assertion execution error.
description: The variable assertion xpath \"{0}\" at activity \"{1}\" failed to execute.
fix: Please ensure the xpath query is valid and namespace qualified.

ORABPEL-20001
severity: 10
type: error
name: Assertion execution error.
description: A problem occurred while converting the assertion value \"{0}\" to a number at activity \"{1}\".
fix: Please change the value to be a number or do a string comparison.

ORABPEL-20002
severity: 10
type: error
name: Assertion execution error.
description: The variable assertion xpath \"{0}\" at activity \"{1}\" failed to select a value.
fix: Please ensure the xpath query is valid and namespace qualified.

ORABPEL-20003
severity: 10
type: error
name: Test results missing.
description: The test results for this process instance could not be located.
fix: Please try to re-run the test case or contact your system administrator.

ORABPEL-20004
severity: 10
type: error
name: Assertion execution error.
description: The specified comparison type \"{0}\" at activity \"{1}\" is not valid.
fix Please specify a valid comparison type

ORABPEL-20005
severity: 10
type: error
name: An external call failed.
description: An error occurred attempting to notify call \"{0}\" at activity \"{1}\".
fix Please examine the log file and make the necessary changes or contact your system administrator.

ORABPEL-20006
severity: 10
type: error
name: The test driver could not be located.
description: An error occurred while reading the test case for suite \"{0}\", test \"{1} \".
fix Please ensure the test was deployed successfully. If the problem persists, please try to re-deploy the test case.

ORABPEL-20007
severity: 10
type: error
name: The test driver could not be parsed.
description: An error occurred while trying to parse the test driver for suite \"{0}\", test \"{1}\". {2}
fix Please ensure the file is valid. Please attempt to redeploy the test case to view any errors.

ORABPEL-20008
severity: 10
type: error
name: An included message could not be parsed.
description: An error occurred while trying create the initiation payload for test \"{0}\" in suite \"{1}\". {2}
fix Please ensure the test is valid and has been deployed correctly.

ORABPEL-20009
severity: 10
type: error
name: An error occurred while generating the initiation message.
description: An error occurred while trying to parse an included message \"{0}\" in suite \"{1}\".
fix Please ensure the test is valid and has been deployed correctly. If you are using message updates, please make sure they have been defined correctly.

ORABPEL-20010
severity: 10
type: error
name: Invalid operation.
description: The operation \"{0}\" is not valid for process \"{1}\", revision \"{2}\".
fix Please ensure the operation exists and corresponds to a createInstance receive activity in the BPEL process.

ORABPEL-20011
severity: 10
type: error
name: Instance initiation error.
description: An error occurred while launching an instance for suite \"{0}\", test \"{1} \".
fix Please examine the log file for details or contact the system administrator.

ORABPEL-20012
severity: 10
type: error
name: Test run data retrieval error.
description: An error occurred while retrieving data for the test run.
fix Please examine the log file for details or contact the system administrator.

ORABPEL-20013
severity: 10
type: error
name: Invalid results document.
description: An error occurred while parsing the results document.
fix Please examine the log file for details or contact the system administrator.

ORABPEL-20014
severity: 10
type: error
name: Partner Emulation Failed.
description: An error occurred while emulating partner \"{0}\", role \"{1}\", operation \"{2} \".
fix Please ensure the partner details are correct in the test driver specified in test suite \"{2}\", location \"{3}\" and examine the log file for details.,

ORABPEL-20015
severity: 10
type: error
name: Partner Emulation Failed.
description: An error occurred while construcing the partner emulation for activity \"{0}\". Message part \"{1}\" could not be created
Fix Please examine the test case driver specified in test suite \"{2} \", location \"{3}\" for errors.

ORABPEL-20016
severity: 10
type: error
name: The test run timed out.
description: This happens when test instances do not complete within the allotted time.
fix Please go to the BPEL Console to determine why some tests have not completed.

ORABPEL-20017
severity: 10
type: error
name: The specified duration is invalid.
description: The duration \"{0}\" is invalid. {1}
fix Please correct the test driver specified in test suite \"{2}\", location \"{3}\" and redeploy the test case,

ORABPEL-20018
severity: 10
type: error
name: The specified message content is invalid.
description: At activity \"{0}\", the emulated message content is invalid.
fix Please redeploy the test case specifid in test suite \"{1}\", location \"{2}\" to view driver errors.

ORABPEL-20019
severity: 10
type: error
name: The expected xml content file was not found.
description: At activity \"{0}\", the expected xml file \"{1}\" could not be found.
fix Please ensure this file has been deployed under the \"messages\" directory.

ORABPEL-20020
severity: 10
type: error
name: XML comparison error.
description: At activity \"{0}\", an unexpected error occurred while executing an XML assertion.
fix Please ensure your test driver file is specified correctly.

ORABPEL-20021
severity: 10
type: error
name: Invalid XPath.
description: At activity \"{0}\", the xpath expression \"{1}\" did not select an element.
fix When doing XML comparsions, please ensure the specified xpath selects an element, or the entire document.

ORABPEL-20022
severity: 10
type: error
name: Driver Generation Error.
description: An unexpected error occurred while generating the test driver.
fix Please ensure the process instance has completed and is valid. Also ensure that the audit trail logging level is set to \"development\".

ORABPEL-20023
severity: 10
type: error
name: Driver Generation Error. Instance still in progress.
description: An error occurred while generating the test driver. Test drivers may only be generated when the instance has completed.
fix Please wait for the instance to complete and then try again.

ORABPEL-20024
severity: 10
type: error
name: Remote deployment failed due to validation errors.
description: Test suite \"{0}\" failed to deploy:\n{1}

ORABPEL-20025
severity: 10
type: error
name: Invalid partner emulation settings.
description Error occurred in test suite \"{0}\", location \"{1}\". While emulating\n" + "activity \"{2}\", the \"testSuite\" or \"testLocation\" parameter was not set.
fix Please set both the testSuite and testLocation attributes of the \"emulate\" element in the test case.

ORABPEL-20026
severity: 10
type: error
name: Test Details not found.
description No test information was found for instance {0}
fix Please ensure the instance is a test case before trying to retrieve test case information.

ORABPEL-20027
severity: 10
type: error
name: Expected XML content not found.
description At activity \"{0}\", no XML content was found while performing an XML assertion.
fix Please ensure that the expected XML content is provided inline or the assertion points to a valid file.

ORABPEL-20028
severity: 10
type: error
name: An error occurred while loading test details.
description An I/O error occurred while loading test details using the where condition {0}. The reported error is {1}.
fix Please examine the error and ensure the data-source is operating properly.

ORABPEL-20029
severity: 10
type: error
name: An error occurred while loading test details.
description An XML parsing error occurred while loading test details for instance {0}. The reported error is {1}.
fix Please do not modify the test_results table manually.

ORABPEL-20030
severity: 10
type: error
name: No initiation operation.
description No initiation section could be found for test defined in suite \"{0}\", file \"{1)\".
fix An initiation section must be provided in a test case or included test driver.

ORABPEL-20200
severity: 10
type: error
name: Deployment failed.
description The attribute \"{0}\" is mandatory.\n Please set this attribute in the task.
fix Please provide this attribute.

ORABPEL-20201
severity: 10
type: error
name: Deployment failed.
description No process deployment could be found for \"{0}\", revision \"{1}\" in domain \"{2}\".
fix Please deploy the process and then try to deploy the tests again. /* { "DEPLOYTEST_suitedir_creation_error", "Deployment failed. The deployment directory \n{0}\n could not be created. { "DEPLOYTEST_suitedir_writable_error", "Deployment failed. The deployment directory \n{0}\n is not a directory or is not writable. */

ORABPEL-20202
severity: 10
type: error
name: Deployment failed.
description Deployment directory \"{0}\" could not be created.
fix Please ensure the parent directory is writable.

ORABPEL-20203
severity: 10
type: error
name: Deployment failed.
description The test files could not be copied to directory \"{0} \".
fix Error message: {1}

ORABPEL-20296
severity: 10
type: error
name: Message update error.
description An error occurred while applying message updates. The XPath \"{0}\" did not select at least one element or attribute.
fix lease check the message namespace and structure to be sure the XPath will select a node.

ORABPEL-20297
severity: 10
type: error
name: An error occurred while deploying the test suite.
description An XML parsing error occurred while storing the test definition for process \"{0}\", revision \"{1}\", test suite \"{2}\". The reported error is {3}.
fix Please ensure the data source is configured correctly. Examine the error message for more details.

ORABPEL-20298
severity: 10
type: error
name: An error occurred while loading test definition.
description An XML parsing error occurred while loading the testdefinition for process \"{0}\", revision \"{1}\", test suite \"{2}\", location \"{3}\". The reported error is {4}."},
Please do not modify the test_results table manually."

ORABPEL-20299
severity: 10
type: error
name: The test suite could not be located.
description: An error occurred while locating the test suite \"{2}\" for process \"{0}\", revision \"{1}\".
fix Please ensure the test suite has been deployed to the server for this process.