Testing Siebel Business Applications > Plan Testing Strategy >

Test Plans

The purpose of the test plan is to define a comprehensive approach to testing. This includes a detailed plan for verifying the stated objectives, identifying any issues, and communicating schedules towards the stated objectives. The test plan has the following components:

• Project scope. Outlines the goals and what is included in the testing project.
• Test cases. Detail level test scenarios. Each test plan is made up of a list of test cases, their relevant test phases (schedule), and relationship to requirements (traceability matrix).
• Business process script inventory and risk assessment. A list of components (business process scripts) that require testing. Also describes related components and identifies high-risk components or scenarios that may require additional test coverage.
• Test schedule. A schedule that describes when test cases will be executed.
• Test environment. Outlines the recommendations for the various test environments (for example, Functional, System Integration, and Performance). This includes both software and hardware.
• Test data. Identifies the data required to support testing.

Business process testing is an important best practice. Business process testing drives the test case definition from the definition of the business process. In business process testing, coverage is measured based on the percentage of validated process steps.

Best Practice

Functional testing based on a required business process definition provides a structured way to design test cases, and a meaningful way to measure test coverage based on business process steps.

Business process testing is described in more detail in the sections that follow.