| <?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-15T12:50:34.375-0700" |
| version="7.2.0"> |
| <mainDescription><p>A
 |
| test case specifies the conditions that must be validated to enable an assessment
 |
| of aspects of the system under test. A test case is more formal than a test
 |
| idea; typically, a test case takes the form of a specification. In less formal
 |
| environments, you can create test cases by identifying a unique ID, name,
 |
| associated test data, and expected results. </p> <p> Test cases can be derived
 |
| from many sources, and typically include a subset of the requirements (such
 |
| as use cases, performance characteristics, and reliability concerns) and other
 |
| types of quality attributes. For more information on types of tests and their
 |
| relationships to quality test attributes, see <a class="elementLinkWithType"
 |
| href="./../../core.tech.common.extend_supp/guidances/concepts/testing_qualitative_rqmts_CAE80710.html"
 |
| guid="_0aJ6cMlgEdmt3adZL5Dmdw">Concept: Testing Qualitative Requirements</a>. </p></mainDescription> |
| <purpose><p
 |
| > Use this artifact for the following purposes: </p> <ul>
 |
| <li> To provide a way to capture test inputs, conditions, and expected
 |
| results for a system </li>
 |
| <li> To systematically identify aspects of the software to test 
 |
| </li>
 |
| <li> To specify whether an expected result has been reached, based
 |
| on the verification of a system requirement, set of requirements,
 |
| or scenario </li>
 |
| </ul></purpose> |
| <impactOfNotHaving><p> 
 |
| Without this artifact, it is difficult to validate system functionality.
 |
| Because this artifact specifies the conditions of acceptance between the stakeholders
 |
| and the developers, without the artifact, it is difficult to establish exit
 |
| criteria and to demonstrate that the exit criteria have been met. If the original
 |
| test cases have not been documented, it is impossible to do regression testing. </p></impactOfNotHaving> |
| <reasonsForNotNeeding><p
 |
| > It might not be necessary to create this artifact to maintain or make small
 |
| enhancements to existing systems, which likely have existing test assets that
 |
| you can use. You also might not need this artifact if you use a package application
 |
| that has its own set of test cases. </p></reasonsForNotNeeding> |
| </org.eclipse.epf.uma:ArtifactDescription> |
