SOFTWARE TEST REPORT (STR)

SOFTWARE TEST REPORT (STR) Contents

1 Scope

1.1 Identification

1.2 System overview

1.3 Document overview

2. Referenced documents

3. Overview of test results

3.1 Overall assessment of the software tested

3.2 Impact of test environment

3.3 Recommended improvements

4. Detailed test results

4.x (Project-unique identifier of a test)

4.x.1 Summary of test results

4.X.2 Problems encountered

4.x.2.y (Project-unique identifier of a test case) 4.x.3 Deviations from test cases/procedures

4.x.3.y (Project-unique identifier of a test case)

5. Test log

6. Notes

A. Annexes

Software Test Report (STR)

I - Scope. This clause should be divided into the following subclauses.

1.1 Identification. This subclause shall contain a full identification of the system and the

software to which this document applies, including, as applicable, identification number(s), title(s), abbreviations, version number(s), and release number(s).

1.2 System overview. This subclause shall briefly state the purpose of the system and the software to which this document applies. It shall describe the general nature of the system and software; summarize the history of system development, operation, and maintenance; identify the project sponsor, acquirer, user, developer, and maintenance organizations; identify current and planned operating sites; and list other relevant

documents.

1.3 Document overview. This subclause shall summarize the purpose and contents of this document and shall describe any security or privacy protection considerations

associated with its use.

2. Referenced documents. This clause shall list the number, title, revision, date, and source of all documents referenced in this

3. Overview of test results. This clause should be divided into the following subclauses to provide an overview of test results.

3.1 Overall assessment of the software tested. This subclause shall:

a. Provide an overall assessment of the software as demonstrated by the test results in this report

b. Identify any remaining deficiencies, limitations, or constraints that were detected by the testing performed. Problem/change

reports may be used to provide deficiency information.

c. For each remaining deficiency, limitation, or constraint, describe:

1 )Its impact on software and system performance, including identification of requirements not met

2) The impact on software and system design to correct it

3) A recommended solution/approach for correcting it

3.2 Impact of test environment. This subclause shall provide an assessment of the manner in which the test environment may be different from the operational environment

and the effect of this difference on the test results.

3.3 Recommended improvements. This subclause shall provide any recommended improvements in the design, operation, or

recommended improvements are provided, this subclause shall state "None."

4. Detailed test results. This clause should be divided into the following subclauses to describe the detailed results for each test. Note: The word "test' means a related

collection of test cases.

4.x (Protect-unique identifier of a test). This subclause shall identify a test by project- unique identifier and should be divided into the following to describe the test results.

4.x. I Summary of test results. This subclause shall summarize the results of the test.

The summary shall include, possibly in a table, the completion status of each test case associated with the test (for example, 'all results as expected,' "problems encountered," "deviations required'). When the completion status is not 'as expected,' this subclause

shall reference the following subclauses for details.

4.x.2 Problems encountered. This subclause should be divided into subclauses that

identify each test case in which one or more problems occurred.

4.x.2.y (Protect-unique identifier of a test case). This subclause shall identify by project- unique identifier a test case in which one or more problems occurred, and shall provide:

a. A brief description of the problem(s) that occurred

b. Identification of the test procedure step(s) in which they occurred

c. Reference(s) to the associated problem/change report(s) and backup data, as

applicable

d. The number of times the procedure or step was repeated in attempting to correct the problem(s) and the outcome of each

attempt

e. Back-up points or test steps where tests were resumed for retesting

4. x. 3 Deviations from test cases/procedures. This subclause should be divided into sub- clauses that identify each test case in which deviations from test case/test procedures occurred.

4.x.3.y (Protect-unique identifier of a test case). This subclause shall identify by project- unique identifier a test case in which one

a. A description of the deviations) (for example, test case run in which the deviation occurred and nature of the deviation,

such as substitution of required equipment, procedural steps not followed, schedule deviations). (Red-lined test procedures may be used to show the deviations)

b. The rationale for the deviations)

c. An assessment of the deviations' impact on the validity of the test case

5. Test log. This clause shall present, possibly in a figure or annex, a chronological record of the test events covered by this report.

a. The date(s), time(s), and locations) of the tests performed

b. The hardware and software configurations used for each test including, as applicable, part/model/serial number,

manufacturer, revision level, and calibration date of all hardware, and version number and name for the software

components used

c. The date and time of each test-related activity, the identity of the individuals) who performed the activity, and the identities

of witnesses, as applicable

6. Notes. This clause shall contain any general information that aids in understanding this document (e.g., background information, glossary, rationale). This clause shall include an alphabetical listing of all acronyms, abbreviations, and their meanings as used in this document and a list of any terms and definitions needed to understand this document.

A. Annexes. Annexes may be used to provide information published separately for convenience in document maintenance (e.g., charts, classified data). As applicable, each annex shall be referenced in the main body of the document where the data would normally have been provided. Annexes may be bound as separate documents for ease in handling. Annexes shall be lettered alphabetically (A, B, etc.).