Intermediate Test Plan Template

Overview

· Introduce readers to test approach

· What is testing dollars “buying”?

· Concise explanation of goals

· Mention system under test architecture, decomposition methods, dependencies, and disclaimers.

Bounds

· What you will and will not test

· Establishing resources relative to test environments

· How test effort dovetails into software process

Scope

· “extent of treatment, activity, or influence; the range of operation” – Webster

· is/is not table

Definitions

· Start with project specific language then general testing terms

Setting

· Environmental requirements, network topology, web, client/server

Quality Risks

Quality is “features [that] are decisive as to product performance and as to ‘product satisfaction’…the word quality also refers to freedom from deficiencies…[that] result in complaints, claims, returns, rework, and other damage.” - Juran

Proposed Schedule of Milestones

Table or project plan (Gantt chart) of activities

Stick to high-level, measurable, visible milestones

Transition

Entry Criteria

· What happens when system moves into a particular test phase

· Think about requiring necessary documentation, specifications, and requirements

· Or the supporting utilities, accessories, and prerequisites available in forms that testers can use?

· Is the system at the appropriate level of quality?

· Is the test environment-lab, hardware, software, and system administrations support-ready?

Stopping Criteria

· Define conditions or events that would lead to suspension of test execution

Exit Criteria

· address the issue: how to determine when testing has completed

Test Configurations and Environments

· Hardware, software, networks and lab space

· Acceptance test or beta test requirements

Test Execution

Address important factors affecting test execution; you must make your data presentable to your team, piers, and management.

Resources

· People, tools, systems, software, hardware, network, and other resources

Test Case and Bug Tracking

· Systems that help track and manage test execution and discovered bugs

Bug Isolation and Classification

· Degree you intend to isolate bugs

· Method you’ll use to classify bug reports

Release Management

· Mandate versioning

· Establish new release format

· Expectations around release acceptance (partial builds between test cycles)

Test Cycles

· use numeric scheme 3.1, 3.1.1, 3.1.1.1…

· define test suite

Risks and Contingencies

Topics might include training needs, will there be additional development support for debugging, number of bugs in product, etc.

Change History

Record changes and revisions that have been made to test plan itself.

Referenced Documents

Specifications, requirements, configuration tables, automation scheme, templates and examples.