For instructions on using this template, please see Notes to Author/Template Instructions on page 14.

Notes on accessibility: This template has been tested and is best accessible with JAWS 11.0 or higher.
For questions about using this template or to request changes to the template, please contact CMS IT
Governance (IT_Governance@cms.hhs.gov).

<Project Name/Acronym>
Test Case Specification
Version X.X
MM/DD/YYYY

TCS Version X.X 1 <Project and release name>

CMS TLC List of Tables

Table of Contents
1. Introduction.................................................................................................................1
1.1 Overview..............................................................................................................1
2. Test Case Summary...................................................................................................2
3. Test Case-To-Requirements Traceability Matrix.....................................................3
4. Test Case Details........................................................................................................4
4.1 <Test Case/Script Identifier>...............................................................................4
4.1.1 Test Objective...............................................................................................4
4.1.2 Inter-Case Dependencies.............................................................................4
4.1.3 Test Items.....................................................................................................4
4.1.4 Prerequisite Conditions.................................................................................4
4.1.5 Input Specifications.......................................................................................5
4.1.6 Expected Test Results..................................................................................5
4.1.7 Pass/Fail Criteria...........................................................................................6
4.1.8 Test Procedure.............................................................................................6
4.1.9 Assumptions and Constraints.......................................................................7
4.2 <Test Case/Script Identifier>...............................................................................7
4.2.1 Test Objective...............................................................................................7
4.2.2 Inter-Case Dependencies.............................................................................7
4.2.3 Test Items.....................................................................................................7
4.2.4 Prerequisite Conditions.................................................................................8
4.2.5 Input Specifications.......................................................................................8
4.2.6 Expected Test Results..................................................................................8
4.2.7 Pass/Fail Criteria...........................................................................................8
4.2.8 Test Procedure.............................................................................................8
4.2.9 Assumptions and Constraints.......................................................................8
Appendix A: Test Case-to-Requirements Traceability Matrix.....................................9
Appendix B: Record of Changes..................................................................................10
Appendix C: Glossary...................................................................................................11
Appendix D: Referenced Documents..........................................................................12
Appendix E: Approvals.................................................................................................13
Appendix F: Notes to the Author/Template Instructions...........................................14

List of Figures
No table of figures entries found.

TCS Version X.X 2 <Project and release name>

CMS TLC List of Tables

List of Tables
Table 1 - Test Case Summary...........................................................................................3
Table 2 - Test Procedure Steps for Given Test Case/Script Identifier..............................8
Table 8 - Test Case-To-Requirements Traceability Matrix..............................................10
Table 3 - Record of Changes...........................................................................................11
Table 5 - Glossary............................................................................................................12
Table 6 - Referenced Documents....................................................................................13
Table 7 - Approvals..........................................................................................................14

TCS Version X.X 3 <Project and release name>

CMS TLC Test Case Details

1. Introduction
Instructions: Provide full identifying information for the automated system, application,
or situation for which the Test Case Specification applies, including as applicable,
identification number(s), title(s)/name(s), abbreviation(s)/acronym(s), part number(s),
version number(s), and release number(s). Summarize the purpose of the document,
the scope of activities that resulted in its development, the intended audience for the
document, and expected evolution of the document. Also describe any security or
privacy considerations associated with use of the Test Case Specification.

1.1 Overview
Instructions: Briefly describe the purpose and context for the system or situation, and
summarize the history of its development. Include the high-level context diagram(s) for
the system and subsystems previously provided in the High-Level Technical Design
Concept/Alternatives, Requirements Document, and/or System Design Document
(SDD), updated as necessary to reflect any changes that have been made based on
more current information or understanding. If the high-level context diagram has been
updated, identify the changes that were made and why.

(NOTE: This section maybe replaced by the System Design Document.)

TCS Version X.X 1 <Project and release name>

CMS TLC Test Case Details

2. Test Case Summary

Instructions: Provide an overview of the test cases/scripts that will be executed. List
each test case/script by its project-unique identifier and title. Test cases/scripts may be
grouped by test function (e.g., user acceptance testing, Section 508 testing, system
testing, regression testing, etc.). If test case/script information is maintained in an
automated tool, this information may be exported or printed from the tool and included
as an appendix to this document that is referenced here.
Table 1 - Test Case Summary
Test Case/Script Identifier Test Case/Script Title Execution Priority
<Test Case/Script <Test Case/Script <Execution
Identifier> Title> Priority>

TCS Version X.X 2 <Project and release name>

CMS TLC Test Case Details

3. Test Case-To-Requirements Traceability Matrix

Instructions: Provide a table that maps all of the requirements contained within the
Requirements Document to their corresponding test cases/scripts. Reference the
Appendices section of this document for a sample template for a Test Case-to-
Requirements Traceability Matrix. The completed traceability matrix should be inserted
here or a reference made to its inclusion as a separate appendix. If test case/script
information is maintained in an automated tool, the matrix may be exported or printed
from the tool for inclusion in this document.

TCS Version X.X 3 <Project and release name>

CMS TLC Test Case Details

4. Test Case Details

Instructions: Provide details for each test case/script identified in the Test Case
Summary section. There should be a separate detail section for each test case/script. If
test case/script information is maintained in an automated tool, the information
described in the following sub-sections should be collected for each test case/script.
This information may be printed from the tool and included as an appendix to this
document that is referenced here. The test case/script details may also be printed in a
tabular format to allow groupings of test cases/scripts with similar characteristics to
reduce the volume of reported information and make it easier to review the content.

4.1 <Test Case/Script Identifier>

Instructions: Provide a project-unique identifier and descriptive title for the test case or
test script. Identify the date, number, and version of the test case/script and any
subsequent changes to the test case/script specification. The number of the test
case/script may identify its level in relation to the level of the corresponding software to
assist in coordinating software development and test versions within configuration
management.

4.1.1 Test Objective

Instructions: Describe the purpose of the test case/script and provide a brief description.
Also, identify if the test case/script may be used by multiple test functions.

4.1.2 Inter-Case Dependencies

Instructions: List any prerequisite test cases/scripts that would create the test
environment or input data in order to run this test case/script. Also, list any post-
requisite test cases/scripts for which the running of this test case/script would create the
test environment or input data.

4.1.3 Test Items

Instructions: Describe the items or features (e.g., requirements, design specifications,
and code) to be tested by the test case/script. Keep in mind the level for which the test
case/script is written and describe the items/features accordingly. The item description
and definition can be referenced from any one of several sources, depending on the
level of the test case/script. It may be a good idea to reference the source document as
well (e.g., Requirements Document, System Design Document, User Manual,
Operations & Maintenance Manual, Installation Instructions from Version Description
Document, etc.)

4.1.4 Prerequisite Conditions

Instructions: Identify any prerequisite conditions that must be established prior to
performing the test case/script. The following considerations should be discussed, as
applicable:

TCS Version X.X 4 <Project and release name>

CMS TLC Test Case Details

o Environmental needs (e.g., hardware configurations, system software

(e.g., operating systems, tools), other software applications, facilities,
training);
o Stubs, drivers, flags, initial breakpoints, pointers, control parameters, or
initial data to be set/reset prior to test commencement;
o Preset hardware conditions or states necessary to run the test case/script;
o Initial conditions to be used in making timing measurements;
o Conditioning of the simulated environment; and
o Other special conditions (e.g., interfaces) peculiar to the test case/script.

4.1.5 Input Specifications

Instructions: Describe all inputs required to execute the test case/script. Keep in mind
the level for which the test case/script is written and describe the inputs accordingly. Be
sure to identify all required inputs (e.g., data (values, ranges, sets), tables, human
actions, conditions (states), files (databases, control files, transaction files), and
relationships (timing)). The input can be described using text, a picture of a properly
completed screen, a file identifier, or an interface to another system. It is also
acceptable to simplify the documentation by using tables for data elements and values.
Include, as applicable, the following:
o Name, purpose, and description (e.g., range of values, accuracy) of each
test input;
o Source of the test input and the method to be used for selecting the test
input;
o Whether the test input is real or simulated;
o Time or event sequence of test input; and
o The manner in which the input data will be controlled to:
o Test the item(s) with a minimum/reasonable number of data types and
values.
o Exercise the item(s) with a range of valid data types and values that test for
overload, saturation, and other “worst case” effects.
o Exercise the item(s) with invalid data types and values to test for appropriate
handling of irregular inputs.
o Permit retesting, if necessary.

4.1.6 Expected Test Results

Instructions: Identify all expected test results for the test case/script, including both
intermediate and final results. Describe what the system should look like after the test
case/script is run by examining particular screens, reports, files, etc. Identify all outputs
required to verify the test case/script. Keep in mind the level for which the test
case/script is written and describe the outputs accordingly. Be sure to identify all
outputs (e.g., data (values, sets), tables, human actions, conditions (states), files

TCS Version X.X 5 <Project and release name>

CMS TLC Test Case Details

(databases, control files, transaction files), relationships, timing (response times,

duration)). The description of outputs can be simplified by using tables, and may even
be included in the same table as the associated input to further simplify the
documentation and improve its usefulness.

4.1.7 Pass/Fail Criteria

Instructions: Identify the criteria to be used for evaluating the intermediate and final
results of the test case/script, and determining the success or failure of the test
case/script. For each test result, the following information should be provided, as
applicable:
o The range or accuracy over which an output can vary and still be
acceptable;
o Minimum number of combinations or alternatives of input and output
conditions that constitute an acceptable test result;
o Maximum/minimum allowable test duration, in terms of time or number of
events;
o Maximum number of interrupts, halts, or other system breaks that may
occur;
o Allowable severity of processing errors;
o Conditions under which the result is inconclusive and re-testing is to be
performed;
o Conditions under which the outputs are to be interpreted as indicating
irregularities in input test data, in the test database/data files, or in test
procedures;
o Allowable indications of the control, status, and results of the test and the
readiness for the next test case/script (may be output of auxiliary test
software); and
o Other criteria specific to the test case/script.

4.1.8 Test Procedure

Instructions: Describe the series of individually numbered steps that are to be
completed in sequential order to execute the test procedure for the test case/script. For
convenience in document maintenance, the test procedures may be included as an
appendix and referenced in this paragraph. The appropriate level of detail in the test
procedure depends on the type of software being tested. For most software, each step
may include a logically-related series of keystrokes or other actions, as opposed to
each keystroke being a separate test procedure step. The appropriate level of detail is
the level at which it is useful to specify expected results and compare them to actual
results. The following should be provided for the test procedure, as applicable:
o Test operator actions and equipment operation required for each step,
including commands, as applicable, to:
o Initiate the test case/script and apply test inputs

TCS Version X.X 6 <Project and release name>

CMS TLC Test Case Details

o Inspect test conditions

o Perform interim evaluations of test results
o Record data
o Halt or interrupt the test case/script
o Request diagnostic aids
o Modify the database/data files
o Repeat the test case if unsuccessful
o Apply alternate modes as required by the test case/script
o Terminate the test case/script.
o Expected result and evaluation criteria for each step.
o If the test case/script addresses multiple requirements, identification of
which test procedure step(s) address which requirements.
o Actions to follow in the event of a program stop or indicated error, such
as:
o Recording of critical data from indicators for reference purposes
o Halting or pausing time-sensitive test-support software and test apparatus
o Collection of system and operator records of test results
o Actions to be used to reduce and analyze test results to accomplish the
following:
o Detect whether an output has been produced
o Identify media and location of data produced by the test case/script
o Evaluate output as a basis for continuation of test sequence
o Evaluate test output against required output.
Table 2 - Test Procedure Steps for Given Test Case/Script Identifier
Step # Action Expected Results/Evaluation Criteria Requirement(s) Tested
<#> <Action <Expected Results/Evaluation <Requirement(s)
> Criteria> Tested>

4.1.9 Assumptions and Constraints

Instructions: Identify any assumptions made and constraints or limitations imposed in
the description of the test case due to system or test conditions (e.g., limitations on
timing, interfaces, equipment, personnel, and database/data files. If waivers or
exceptions to specified limits and parameters are approved, they are to be identified
and their effects and impacts upon the test case/script described.

4.2 <Test Case/Script Identifier>

4.2.1 Test Objective

TCS Version X.X 7 <Project and release name>

CMS TLC Test Case Details

4.2.2 Inter-Case Dependencies

4.2.3 Test Items

4.2.4 Prerequisite Conditions

4.2.5 Input Specifications

4.2.6 Expected Test Results

4.2.7 Pass/Fail Criteria

4.2.8 Test Procedure

4.2.9 Assumptions and Constraints

TCS Version X.X 8 <Project and release name>

CMS TLC Appendix F: Notes to the Author/Template Instructions

Appendix A: Test Case-to-Requirements Traceability Matrix

Instructions: Below is an example of a test case-to-requirements traceability matrix. The
table below should be modified appropriately to reflect the actual identification and
mapping of test cases to requirements for the given system/project.
Table 3 - Test Case-To-Requirements Traceability Matrix
Test Case Test Case Test Case Test Case Test Case Test Case
Requirement
01 02 03 04 05 06
Requirement <Identify <Identify <Identify <Identify <Identify <Identify
1.0 traceability> traceability> traceability> traceability> traceability> traceability>
Requirement <Identify <Identify <Identify <Identify <Identify <Identify
1.1 traceability> traceability> traceability> traceability> traceability> traceability>
Requirement <Identify <Identify <Identify <Identify <Identify <Identify
1.2 traceability> traceability> traceability> traceability> traceability> traceability>
Requirement <Identify <Identify <Identify <Identify <Identify <Identify
2.0 traceability> traceability> traceability> traceability> traceability> traceability>
Requirement <Identify <Identify <Identify <Identify <Identify <Identify
2.1 traceability> traceability> traceability> traceability> traceability> traceability>

TCS Version X.X 9 <Project and release name>

CMS TLC Appendix F: Notes to the Author/Template Instructions

Appendix B: Record of Changes

Instructions: Provide information on how the development and distribution of the Test
Case Specification will be controlled and tracked. Use the table below to provide the
version number, the date of the version, the author/owner of the version, and a brief
description of the reason for creating the revised version.
Table 4 - Record of Changes
Version Number Date Author/Owner Description of Change
<X.X> <MM/DD/ CMS <Description of
YYYY> Change>
<X.X> <MM/DD/ CMS <Description of
YYYY> Change>
<X.X> <MM/DD/ CMS <Description of
YYYY> Change>

TCS Version X.X 10 <Project and release name>

CMS TLC Appendix F: Notes to the Author/Template Instructions

Appendix C: Glossary
Instructions: Provide clear and concise definitions for terms used in this document that
may be unfamiliar to readers of the document. Terms are to be listed in alphabetical
order.
Table 5 - Glossary
Term Acronym Definition
<Term <Acronym <Definition
> > >
<Term <Acronym <Definition
> > >
<Term <Acronym <Definition
> > >

TCS Version X.X 11 <Project and release name>

CMS TLC Appendix F: Notes to the Author/Template Instructions

Appendix D: Referenced Documents

Instructions: Summarize the relationship of this document to other relevant documents.
Provide identifying information for all documents used to arrive at and/or referenced
within this document (e.g., related and/or companion documents, prerequisite
documents, relevant technical documentation, etc.).
Table 6 - Referenced Documents
Document Name Document Location and/or URL Issuance Date
<Document <Document Location and/or <MM/DD/
Name> URL> YYYY>
<Document <Document Location and/or <MM/DD/
Name> URL> YYYY>
<Document <Document Location and/or <MM/DD/
Name> URL> YYYY>

TCS Version X.X 12 <Project and release name>

CMS TLC Appendix F: Notes to the Author/Template Instructions

Appendix E: Approvals
The undersigned acknowledge that they have reviewed the Test Case Specification and agree
with the information presented within this document. Changes to this Test Case Specification
will be coordinated with, and approved by, the undersigned, or their designated representatives.
Instructions: List the individuals whose signatures are desired. Examples of such
individuals are Business Owner, Project Manager (if identified), and any appropriate
stakeholders. Add additional lines for signature as necessary.
Table 7 - Approvals
Document Approved By Date Approved

Name: <Name>, <Job Title> - <Company> Date

Name: <Name>, <Job Title> - <Company> Date

Name: <Name>, <Job Title> - <Company> Date

Name: <Name>, <Job Title> - <Company> Date

TCS Version X.X 13 <Project and release name>

CMS TLC Appendix F: Notes to the Author/Template Instructions

Appendix F: Notes to the Author/Template Instructions

This document is a template for creating a Test Case Specification for a given
investment or project. The final document should be delivered in an electronically
searchable format. The Test Case Specification should stand on its own with all
elements explained and acronyms spelled out for reader/reviewers, including reviewers
outside CMS who may not be familiar with CMS projects and investments.
This template was designed based on best practices and information to support CMS
governance and IT processes. Use of this template is not mandatory, rather programs
are encouraged to adapt this template to their needs by adding or removing sections as
appropriate. Programs are also encouraged to leverage these templates as the basis
for web-based system development artifacts.
This template includes instructions, boilerplate text, and fields. The author should note
that:
 Each section provides instructions or describes the intent, assumptions, and
context for content included in that section. Instructional text appears in blue
italicized font throughout this template.
 Instructional text in each section should be replaced with information specific to
the particular investment.
 Some text and tables are provided as boilerplate examples of wording and
formats that may be used or modified as appropriate.
When using this template, follow these steps:
1. Table captions and descriptions are to be placed left-aligned, above the table.

2. Modify any boilerplate text, as appropriate, to your specific project.

3. All documents must be compliant with Section 508 requirements.

4. Figure captions and descriptions are to be placed left-aligned, below the

figure. All figures must have an associated tag providing appropriate
alternative text for Section 508 compliance.

5. Delete this “Notes to the Author/Template Instructions” page and all

instructions to the author before finalizing the initial draft of the document.

TCS Version X.X 14 <Project and release name>