User:Mevans/TCMEntityExample: Difference between revisions
| Line 3: | Line 3: | ||
== Name: <b>Test Case</b> == | == Name: <b>Test Case</b> == | ||
=== Description === | === Description === | ||
A Test Case is a specific test intended to verify one particular aspect of a Product under test. A test case will contain information entered by the user which covers objectives and requirements for the test. | |||
Each test case has one or more steps. Each step has instructions to execute it, expected result of an execution and estimated time to complete. Each test case version will be related to a single product version (latest version - by default). | |||
Newly created Test Case will have a status “Draft”. Testing Managers will have Permission to “Approve Test Case” or “Activate”, but Testers will not. Saving “Draft” Test Case will not result in versioning and UI should not prompt users to increment version numbers. | |||
=== Attributes === | === Attributes === | ||
{| class="fullwidth-table" | {| class="fullwidth-table" | ||
Revision as of 04:33, 12 August 2010
Below is a proposed format for describing a TCM enitity
Name: Test Case
Description
A Test Case is a specific test intended to verify one particular aspect of a Product under test. A test case will contain information entered by the user which covers objectives and requirements for the test.
Each test case has one or more steps. Each step has instructions to execute it, expected result of an execution and estimated time to complete. Each test case version will be related to a single product version (latest version - by default).
Newly created Test Case will have a status “Draft”. Testing Managers will have Permission to “Approve Test Case” or “Activate”, but Testers will not. Saving “Draft” Test Case will not result in versioning and UI should not prompt users to increment version numbers.
Attributes
| Attribute Name | Description | Type | Value |
| Title | The title of the test case | STRING | char[100] |