Bookshelf Home | Contents | Index | Search | PDF | ![]() ![]() ![]() ![]() |
Siebel Field Service Guide > Release Manager > Quality Assurance End-User Procedures for Release Manager >
Creating Test Plans and Linking Features
After the features for a release have been identified, QA can begin revising existing test plans or developing new ones to exercise new product functionality. Test plan development is tracked in Release Manager, with the test plan available as an attachment to the record. Parties such as product marketers who are associated with the development of the test plan are linked to the record, and their approvals are recorded.
For each test plan, the fraction completed and the target completion dates are logged so that potential issues will be flagged before they become critical. The QA manager decides whether they need to run a particular test plan against one or more test strategies, and if so, specifies those strategies.
To add a test plan and link features
- Navigate to Site Map > Release > Test Plan Administration.
The QA Test Plans view appears.
- Add a new test plan record.
- In the Related Features field, select the features you want to link to this test plan.
- Complete the other fields, as needed. Some fields are described in the following table.
Field Comments % Auto Percent of the test that is automated. % Auto Horizontal Percent of the horizontal version of the product that the test is automated on. % Auto International Percent of the international version of the product that the test is automated on. % Auto Platforms Percent of platforms that the test is automated on. Auto Complete Date Date the automated test is completed. Automated If selected, indicates this test is automated. Complete % Portion of the test plan that has been completed to date. Product Line Automatically populated based on the values selected in the Area and Subarea fields. QA Owner Person responsible for doing the testing. Release Name or number of the product release with which this test plan is associated. Special Tag Tags defined by your company for convenience in grouping or querying tests. You can specify multiple tags. For information about defining special tags, see Adding Special Tag LOVs. Suggested Strategies Test strategies to apply to this test plan. Available selections come from test strategy records entered in the Strategy Administration view. See Creating Test Strategies. Tag Summary Expanded area field that makes multiple tags visible in the view. For convenience in querying tags that are selected in, but that might not appear on the view in, the Special Tag field. Target Date Date when the test plan is expected to be completed. Test Plan Owner Individuals associated with the test plan. The author of the test plan should be set as Primary. Test Set Indicates what grouping of tests this test belongs to. Groupings may reflect, for example, parts of the product being exercised through multiple tests. Tools Software used to automate this test.Adding Activity Plans to Test Plans
An activity plan derives from a predefined activity template. An activity template contains multiple "canned" activities that can be associated with a release item. This saves end users from having to enter each activity manually, and helps to standardize activities for QA teams.
To add an activity plan to a test plan
- Navigate to Site Map > Release > QA Test Plans.
- In the QA Test Plans list, select a test plan to which you want to add activities.
- Click the Activity Plans view tab.
- In the Activity Plans list, add a new record.
- In the Template field, select an activity template on which to base this activity plan.
- Complete other fields as needed.
When you have associated the activity plan with the test plan, all the activities in the activity plan become associated with the test plan and appear in the Activities view tab.
Bookshelf Home | Contents | Index | Search | PDF | ![]() ![]() ![]() ![]() |
Siebel Field Service Guide Published: 21 April 2003 |