| <?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><p> |
| <strong>Test Ideas List</strong> - A list of brief statements identifying tests that are potentially useful to conduct. |
| </p> |
| <p> |
| <strong>Test Ideas Catalog</strong> - A catalog of common faults and mistakes done when developing software. |
| </p> |
| <ul> |
| <li> |
| Test Ideas will describe any of the elements of an executable test.&nbsp; |
| </li> |
| <li> |
| Test ideas ensure the important ideas are not forgotten and are detailed later in test cases.&nbsp;&nbsp; |
| </li> |
| <li> |
| Test Ideas are to be captured at a less-specific level in an intermediate form. |
| </li> |
| <li> |
| Test ideas are more reviewable and understandable then complete tests.&nbsp; Making the reasoning behind the test |
| idea clearer.&nbsp; |
| </li> |
| <li> |
| Test ideas support more powerful test, by not constraining the tester.&nbsp; Making it easier to create tests that |
| validate more then just the defined requirements. |
| </li> |
| <li> |
| Test Ideas are often based on explicit and implicit fault modules, to include but not limited to Booleans, |
| boundaries and method calls.&nbsp; Test Ideas Lists will contain test ideas from many faults models derived for one |
| or many work products. |
| </li> |
| </ul> |
| <p> |
| Creating test ideas before testing for review and inspection of design work products assists in discovering design or |
| analysis errors. |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |