Objectives and Checkpoints

It is important to establish objectives and checkpoints in testing. This permits periodic examination of the testing process to make sure it is progressing suitably.

Objectives

Establishment of objectives is really taking the goals of the testing and setting up specific items to be met. For example, in the accounting process, an objective may be to run x monthly cycles and a yearly cycle. In the student area, an objective may be to go through a complete quarterly schedule.

Unlike general project objectives, testing objectives can be quite specific. Certain items, reports and processes may need to be tested. These can be specified as objectives. However, it is probably better to specify broader testing objectives, e.g., make sure the "xxx" process effectively handles "yyy".

Some general guidelines for testing objectives:

• Try to avoid being overly specific. This will lead to an abundance of objectives. It is better to incorporate the more detailed objectives as part of the testing plan.
• Avoid being overly broad, as it makes evaluation of objectives more difficult. Too broad of objectives can probably be better handled by formulating a different testing goal.
• Objectives may include dates for certain accomplishments. Generally this is better handled in the testing plan, but can be used in objectives to emphasize certain timetables.
• Objectives should be attainable. An objective too loosely defined can cause difficulty in evaluating whether it has been met.

Checkpoints

Part of the testing plan should be to establish checkpoints. At these checkpoints, a review should be done to make sure objectives are being met. Normally, the testing plan specifies a timetable. The checkpoints should be set in such a fashion to be a logical breakpoint in the testing process.

At the checkpoint, the following should be done. This is a guide, and is not intended to be an exhaustive list.

• Examination of the testing schedule to determine testing progress
• Examination of goals and objectives to make sure
  • They are being met
  • They are still appropriate and not in need of revision
• Review of problems encountered and their disposition
• Review of the upcoming schedule leading up to the next checkpoint
• Review of general responsibilities to make sure no adjustments are necessary

If, during the checkpoint review, adjustments to the plan are necessary, they should be made. The testing plan is not a document set in stone. It should be flexible to adapt to changing criteria, needs and conditions. The purpose of the checkpoint is to be able to review the timeliness and effectiveness of the plan and to adjust it as necessary.

OIT Applications Support

Last Modified:

©2001 All Rights Reserved