Testing the Task

This task is a step in Task Development Example.

This task includes validating and testing the task to ensure there are no errors and that the task is working as required. The application developer begins with unit testing, then performs integration testing, and finally system testing.

Unit Testing

Siebel CRM displays the Submit Expense Report link in the context pane. If the user clicks this link, then Siebel CRM displays the first view of this task. The application developer notices that the developer failed to include an Expense Description field in the Expense Header Applet. Several iterations later, the developer demonstrates the submission task to the business analyst who notes that there are a few details that require refinement.

The review task is more difficult to unit test because it requires tight integration with a long-running Workflow Process. The task is relatively simple, so the application developer defers unit testing for the review task until the team integrates it with the long-running Workflow Process.

Next, the application developer performs integration testing.

Integration Testing

To test the configuration in the development environment, the application developer inspects the Workspace in which the work is being performed in a Siebel client, such as the Call Center application. The developer can leverage the Task Debugger to analyze any defects that exist in the task logic.

Next, the application developer performs system testing.

System Testing

One the configuration satisfies the business requirements, the application developer delivers the changes to the parent Integration Workspace and the changes are migrated to the test environment, where further testing can be performed.