User:Mevans/TCMEntityExample
From MozillaWiki
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.
Attributes
| Attribute Name | Description | Type | Value |
| Title | The title of the test case | STRING | char[100] |
| Creation Date | The date of test case creation | DATE | System-Date |
| Last Modification Date | The date the test case was last modified | DATE | System-Date |
| Author | User who created the test case | STRING | Valid system user name |
| Status | The current state of the test case | ENUM | [DRAFT,APPROVED,BLOCKED,ACTIVE] |
| Version | The version number of the test case | SYSTEM-VERSION-NUMBER | <major>.<minor> |
| Tags | List of one or more tags that aid in test case searches and assignments | SYSTEM-LIST | Array of strings |
| Attachments | List of one or more attachments | SYSTEM-LIST | Array of attachment objects |
Business Rules
- General
- 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.
- 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.
- Test Cases – Tags
- Each test case could have multiple Tags, which could be used for searching and reporting.
- Tags are associated with the main test case entity and apply to all versions of a test case.
- Test Cases – Modifying
- When users modify a test case what essentially happens is that a new test case version is created as a completely new entity. This new version of the test case will not, by default, be included in existing test suites and test runs. It will be in “Draft” status, but TM would have an ability to approve it.
- Once approved, this version of a Test Case will become an official Latest Version and will be included in newly created Test Runs and/or Test Suites, which were explicitly marked as such and are still in “Draft” mode themselves.
- Test Cases – Copying
- When users copy a test case a new test case with a new version .0.1 is created as a completely new entity. All steps could be copied as well, or UI can have a feature to ask the user to select steps he would like to copy.
- There could be an option to specify which Tags and Attachments should be copied too.
