Siebel Business Process Framework: Task UI Guide > Implementing Task UI > Scenario for Iterative Development of a Task UI Implementation >

Unit Testing

Finally, the phrase Submit Expense Report shows up in the Context pane, and clicking its link causes the first view of that task to be displayed. User C is excited, but her joy is spoiled by the fact that she forgot to include an Expense Description field in the Expense Header Applet.

Several iterations later, she is ready to demo the submission task to User A, who is quite pleased, but who notes there are a few details that could use some touch-up. Finally, version 16 of the submission task coupled with version 22 of the SRF seems to comprise the iteration that is ready for integration testing.

The review task is somewhat harder to test in isolation, as it requires tight integration with a long-running workflow. Since the task itself is fairly simple, User C decides to defer its unit testing until it is integrated with the long-running workflow.