Bookshelf Home | Contents | Index | Search | PDF

Testing Siebel eBusiness Applications > Execute Siebel Functional Tests >

Overview of Executing Siebel Functional Tests

---

The process of executing Siebel functional tests is designed to provide for delivery of a functionally validated Siebel application into the system environment. For many customers the Siebel application is one component of the overall system, which may include other backend applications, integration infrastructure, and network infrastructure. Therefore, the objective of the Execute Siebel Functional Tests process is to verify that the Siebel application functions properly before inserting it into the larger system environment. This process is illustrated in Figure 16.

Figure 16.  Diagram of the Execute Siebel Functional Tests Process

There are three phases to this process:

Unit Test. The unit test validates the functionality of a single component (for example, an applet or a business service).
Module Test. The module test validates the functionality of a set of related components that make up a module (for example, Contacts or Activities).
Process Test. The process test validates that multiple modules can work together to enable a business process (for example, Opportunity Management or Quote to Order).

Application developers test their individual components for functional correctness and completeness before checking component code into the repository. The unit test cases should have been designed to test the low-level details of the component (for example: control behavior, layout, data handling).

Typical unit tests include structural tests of components, negative tests, boundary tests, and component-level scenarios. The unit test phase allows developers to fast track fixes for obvious defects before checking in. A developer must demonstrate successful completion of all unit test cases before checking in their component. In some cases, unit testing identifies a defect that is not critical for the given component; these defects are logged into the defect tracking system for prioritization.

Once unit testing has been completed on a component, that component is moved into a controlled test environment, where the component can be tested along side others at the module and process level.

Bookshelf Home | Contents | Index | Search | PDF