blob: 69061ed3f7f338eed1c1d211432f8acee8974e53 [file] [log] [blame]
<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:ArtifactDescription xmi:version="2.0" xmlns:xmi="" xmlns:org.eclipse.epf.uma="" epf:version="1.0.0" xmi:id="_NqYIdKeqEdmKDbQuyzCoqQ" name="test_case,_0ZS-0MlgEdmt3adZL5Dmdw" guid="_NqYIdKeqEdmKDbQuyzCoqQ" changeDate="2006-09-20T16:57:14.165-0700">
A test case specifies the conditions which need to be validated to enable an assessment of some particular aspects of
the system under test.&amp;nbsp; A test case is more formal than a test idea and usually takes the form of a
specification.&amp;nbsp;In less formal environments, test cases can be created by identifying a unique ID, name, associated
test data, and expected results.&amp;nbsp;For an example of this type of test case, see&amp;nbsp;&lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../openup_basic/guidances/templates/test_case,_0dT8IMlgEdmt3adZL5Dmdw.html&quot; guid=&quot;_0dT8IMlgEdmt3adZL5Dmdw&quot;&gt;Template: Test Case&lt;/a&gt;.
Test cases may be derived from&amp;nbsp;many&amp;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.&amp;nbsp; For more
information on types of tests and their relationship to quality test attributes, see&amp;nbsp;&lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../openup_basic/guidances/concepts/types_of_test,_0aJ6cMlgEdmt3adZL5Dmdw.html&quot; guid=&quot;_0aJ6cMlgEdmt3adZL5Dmdw&quot;&gt;Concept: Types of Test&lt;/a&gt;.
The purpose of this artifact is to:
provide a way to capture test inputs, conditions, and expected results for a system
systematically identify aspects of the software to test
specify whether an expected result has been reached based on verification of a system requirement, set of
requirements, or scenario