Bookshelf Home | Contents | Index | Search | PDF

Testing Siebel eBusiness Applications > Develop Tests > Test Case Authoring >

Functional Test Cases

---

Functional test cases test a common business operation or scenario. Table 1 shows some examples of functional test cases.

Table 1.  Common Functional Test Cases

Test Phase	Example
Unit Test	Test common control-level navigation through a view. Test any field validation or default logic. Invoke methods on an applet.
Module Test	Test common module-level user scenarios (for example, create an account and add an activity). Verify correct interaction between two related Siebel components (for example, Workflow Process and Business Service).
Process Test	Test proper support for a business process.

A functional test case may verify common control navigation paths through a view. Functional test cases typically have two components, test paths and test data.

Test Path

Test paths describe the actions and objects to be tested. A path is presented as a list of steps and the expected behavior at the completion of a step. Figure 12 shows an example of a test path. Notice that in the Test Case Step column, there are no data values in the path; instead you see a parameter name in italics as a place holder. This parameterization approach is a common technique used with automation tools and is helpful for creating reusable test cases.

Figure 12.  Sample Test Path

Test Data

Frequently, a single path can be used to test many scenarios by simply changing the data that is used. For example, you can test the processing of both high-value and low-value opportunities by changing the opportunity data entered, or you can test the same path on two different language versions of the application. For this reason, it can be helpful to define the test path separate from the test data.

Bookshelf Home | Contents | Index | Search | PDF