| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:ArtifactDescription xmi:version="2.0" |
| xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.5/uma.ecore" |
| xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.0" xmlns:epf="http://www.eclipse.org/epf" |
| epf:version="1.5.0" xmi:id="_NqYIdKeqEdmKDbQuyzCoqQ" |
| name="test_case,_0ZS-0MlgEdmt3adZL5Dmdw" guid="_NqYIdKeqEdmKDbQuyzCoqQ" changeDate="2008-08-14T12:46:38.070-0400" |
| version="7.2.0"> |
| <mainDescription><p>
 |
| A test case specifies the conditions which need to be validated to enable an assessment of some particular aspects of
 |
| the system under test.&nbsp; A test case is more formal than a test idea and usually takes the form of a
 |
| specification.&nbsp;In less formal environments, test cases can be created by identifying a unique ID, name, associated
 |
| test data, and expected results.&nbsp;
 |
| </p>
 |
| <p>
 |
| Test cases may be derived from&nbsp;many&nbsp;sources but will usually include a subset of both the requirements (such
 |
| as use cases, performance characteristics, reliability concerns) and other types of quality attributes.&nbsp; For more
 |
| information on types of tests and their relationship to quality test attributes, see&nbsp;<a
 |
| class="elementLinkWithType" href="./../../core.tech.common.base/guidances/concepts/types_of_test_CAE80710.html"
 |
| guid="_0aJ6cMlgEdmt3adZL5Dmdw">Concept: Types of Test</a>.
 |
| </p></mainDescription> |
| <purpose><p>
 |
| The purpose of this artifact is to:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| provide a way to capture test inputs, conditions, and expected results for a system
 |
| </li>
 |
| <li>
 |
| systematically identify aspects of the software to test
 |
| </li>
 |
| <li>
 |
| specify whether an expected result has been reached based on verification of a system requirement, set of
 |
| requirements, or scenario
 |
| </li>
 |
| </ul></purpose> |
| <impactOfNotHaving><p>
 |
| <font size="2">Without this artifact it is difficult adequately validate system functionality.&nbsp;&nbsp;Since this
 |
| artifact is also often used&nbsp;to specify the conditions of acceptance between the stakeholders and the developers,
 |
| it is more difficult to establish exit criteria and to demonstrate that the exit criteria have been met without
 |
| it.&nbsp; It is also not possible to do regression testing if the original test cases have not been documented.</font>
 |
| </p></impactOfNotHaving> |
| <reasonsForNotNeeding><p>
 |
| <font size="2">It may not be necessary to create this artifact for maintenance or small enhancements to existing
 |
| systems which will likely have existing test assets that can be utilized.&nbsp; Likewise package applications often
 |
| come with their own set of test cases that would not require a separate instance of this artifact.</font>
 |
| </p></reasonsForNotNeeding> |
| </org.eclipse.epf.uma:ArtifactDescription> |
