A simple test plan document in markdown format

test-plan.md

Test Plan Document

• IDENTIFICATION INFORMATION SECTION
  • PRODUCT
  • PROJECT DESCRIPTION
  • TEST PERSONNEL
  • PROGRAMMERS
• UNIT TEST SECTION
  • UNIT TEST STRATEGY / EXTENT OF UNIT TESTING:
  • UNIT TEST CASES
• REGRESSION TEST SECTION
  • REGRESSION TEST STRATEGY
  • REGRESSION TEST CASES
• INTEGRATION TEST SECTION
  • INTEGRATION TEST STRATEGY AND EXTENT OF INTEGRATION TESTING
  • INTEGRATION TEST CASES
• USER ACCEPTANCE TEST SECTION (To be completed by the business office)
  • USER ACCEPTANCE TEST STRATEGY
  • USER ACCEPTANCE TEST CASES
• Appendix

IDENTIFICATION INFORMATION SECTION

PRODUCT

• Product Name: {product name}
• Product Line Portfolio: Insurance

PROJECT DESCRIPTION

A short concise project description

TEST PERSONNEL

• {list of test personnel}

PROGRAMMERS

• {test of programmers}

UNIT TEST SECTION

UNIT TEST STRATEGY / EXTENT OF UNIT TESTING:

Evaluate new features and bug fixes introduced in this release

UNIT TEST CASES

#	OBJECTIVE	INPUT	EXPECTED RESULTS	TEST DELIVERABLES
1

REGRESSION TEST SECTION

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

REGRESSION TEST STRATEGY

Evaluate all reports introduced in previous releases

REGRESSION TEST CASES

#	OBJECTIVE	INPUT	EXPECTED RESULTS	OBSERVED
1

INTEGRATION TEST SECTION

Combine individual software modules and test as a group.

INTEGRATION TEST STRATEGY AND EXTENT OF INTEGRATION TESTING

Evaluate all integrations with locally developed shared libraries, with consumed services, and other touch points.

INTEGRATION TEST CASES

#	OBJECTIVE	INPUT	EXPECTED RESULTS	TEST DELIVERABLES
1

USER ACCEPTANCE TEST SECTION (To be completed by the business office)

Verify that the solution works for the user

USER ACCEPTANCE TEST STRATEGY

{Explain how user acceptance testing will be accomplished}

USER ACCEPTANCE TEST CASES

#	TEST ITEM	EXPECTED RESULTS	ACTUAL RESULTS	DATE
1

Appendix