Artifacts > Environment Artifact Set > {More Environment Artifacts} > Test Guidelines > rup_tstgd.htm
<Project Name>
Test Guidelines
Version <1.0>
[Note: The following template is provided for use with the Rational Unified Process. Text enclosed in square brackets and displayed in blue italics (style=InfoBlue) is included to provide guidance to the author and should be deleted before publishing the document. A paragraph entered following this style will automatically be set to normal (style=Body Text).]
Revision History
Date |
Version |
Description |
Author |
<dd/mmm/yy> |
<x.x> |
<details> |
<name> |
|
|
|
|
|
|
|
|
|
|
|
|
Table of Contents
1.3 Definitions, Acronyms and Abbreviations
6. Defect Management Guidelines
Test Guidelines
[The introduction of the Test Guidelines should provide an overview of the entire document. It should include the purpose, scope, definitions, acronyms, abbreviations, references, and overview of the Test Guidelines.]
[Specify the purpose of the Test Guidelines.]
[A brief description of the scope of the Test Guidelines; what Project(s) it is associated with, and anything else that is affected or influenced by this document.]
[This subsection should provide the definitions of all terms, acronyms, and abbreviations required to properly interpret the Test Guidelines. This information may be provided by reference to the project Glossary.]
[This subsection should provide a complete list of all documents referenced elsewhere in the Test Guidelines. Each document should be identified by title, report number (if applicable), date, and publishing organization. Specify the sources from which the references can be obtained. This information may be provided by reference to an appendix or to another document.]
[This subsection should describe what the rest of the Test Guidelines contains and explain how the document is organized.]
[A statement to identify why testing is performed and used by the organization.]
[This section identifies and describes all guidelines and standards to be used in the planning, design, implementation, execution, and evaluation activities including:
· Test Case standards: A statement identifying the types of test cases that should be developed for testing, such as valid, invalid, boundary, etc.
· Naming Convention: A description of how each kind of entity, such as test case and test procedure, should be named.
· Design Guidelines: A statement identifying test procedure and script modularity goals, for reuse and maintenance.
· Test Data standards: A statement of how data will be selected or created and restored to support testing.]
[A definition of what kind of measures you will use to determine the progress of test activities (what type of defect counts are going to be used, how to measure successfully executed test cases).]
[A statement identifying recommended completion and evaluation criteria.]
[A statement identifying how defects will be managed.]
[A statement identifying how test artifacts will be managed and maintained.]