Test Plan Template

Note: Substitute with test plan name and link to the github testplan issue.

Test Plan Name

Note: This is meant to be only a guideline, the paragraphs can be removed or added as they fit.

• Test Plan Template
• Test Plan Name
• General Information
  • Abstract
  • Stakeholders
  • Requirements
  • Acceptance criteria
  • Risks
  • Tools
• ACC framework
  • Attributes
  • Components
  • Capabilities
• Unit tests
  • Unit tests strategy
  • Unit test cases
• Functional tests
  • Functional tests strategy
  • Functional test cases
• Regression tests
  • Regression tests strategy
  • Regression test cases
• Integration tests
  • Integration tests strategy
  • Integration test cases
• End-to-end tests
  • End-to-end tests strategy
  • End-to-end test cases

General Information

Abstract

Note: Describe the design and architecture of the system in a way that highlights possible points of failure

Stakeholders

Note: Insert the relevant stakeholders that need to understand, review and approve the test plan

Role/Name	Contact	Approval
Product-Owner
Developers
Admin
SRE
Testers

Requirements

Note: Business requirements, insert links to relevant Github or JIRA tickets, list what platforms are supported, what will not be tested, etc

Acceptance criteria

Note: List the acceptance criteria for this feature

Risks

Note: Describe what risks can affect the accomplishment of the testplan. For example documentation is missing, not enough resources etc

Tools

Note: Describe what tools will be needed for the testing, if new tools are needed to be developed

ACC framework

Note: Use the ACC framework to help you define the test cases

Attributes

Note: The adverbs and adjectives that describe the high level concepts testing is meant to ensure. Attributes such as fast, usable, secure, accessible and so forth. The quality metrics document in this repo should and can be used as a guideline

Components

Note: The nouns that define the major code chunks that comprise the product. These are classes, module names and features of the application.

Capabilities

Note: The verbs that describe user actions and activities. Every capability should be testable.

Unit tests

Unit tests strategy

Note: Evaluate new features and bug fixes introduced in this release, and the extent of the unit tests

Unit test cases

#	OBJECTIVE	INPUT	EXPECTED RESULTS	TO BE AUTOMATED
1

Functional tests

Functional tests strategy

Note: Evaluate new features introduced in this release, and the extent of the functional tests

Functional test cases

#	OBJECTIVE	INPUT	EXPECTED RESULTS	TO BE AUTOMATED
1

Regression tests

Regression tests strategy

Note: Ensure that previously developed and tested software still performs after change.

Regression test cases

#	OBJECTIVE	INPUT	EXPECTED RESULTS	TO BE AUTOMATED
1

Integration tests

Integration tests strategy

Note: Evaluate all integrations with other functions, services etc.

Integration test cases

#	OBJECTIVE	INPUT	EXPECTED RESULTS	TO BE AUTOMATED
1

End-to-end tests

End-to-end tests strategy

Note: Evaluate how will test infrastructure, systems under test, and other dependencies be managed? How will they be deployed? How will persistence be set-up/torn-down? How will you handle required migrations from one data center to another?

End-to-end test cases

#	OBJECTIVE	INPUT	EXPECTED RESULTS	TO BE AUTOMATED
1