blob: e63ea870d45eadc281d7926147b4b1bcac666df1 [file] [log] [blame]
<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" xmi:id="_uqL2gMM3EdmSIPI87WLu3g" name="test_ideas,_0jnYcMlgEdmt3adZL5Dmdw" guid="_uqL2gMM3EdmSIPI87WLu3g" changeDate="2006-07-20T15:10:39.401-0700">
<mainDescription>&lt;p&gt;
&lt;strong&gt;Test Ideas List&lt;/strong&gt; - A list of brief statements identifying tests that are potentially useful to conduct.
&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;Test Ideas Catalog&lt;/strong&gt; - A catalog of common faults and mistakes done when developing software.
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
Test Ideas will describe any of the elements of an executable test.&amp;nbsp;
&lt;/li&gt;
&lt;li&gt;
Test ideas ensure the important ideas are not forgotten and are detailed later in test cases.&amp;nbsp;&amp;nbsp;
&lt;/li&gt;
&lt;li&gt;
Test Ideas are to be captured at a less-specific level in an intermediate form.
&lt;/li&gt;
&lt;li&gt;
Test ideas are more reviewable and understandable then complete tests.&amp;nbsp; Making the reasoning behind the test
idea clearer.&amp;nbsp;
&lt;/li&gt;
&lt;li&gt;
Test ideas support more powerful test, by not constraining the tester.&amp;nbsp; Making it easier to create tests that
validate more then just the defined requirements.
&lt;/li&gt;
&lt;li&gt;
Test Ideas are often based on explicit and implicit fault modules, to include but not limited to Booleans,
boundaries and method calls.&amp;nbsp; Test Ideas Lists will contain test ideas from many faults models derived for one
or many work products.
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;
Creating test ideas before testing for review and inspection of design work products assists in discovering design or
analysis errors.
&lt;/p&gt;</mainDescription>
</org.eclipse.epf.uma:ContentDescription>