| <?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.5/uma.ecore" |
| xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.0" xmi:id="_y-_PIMPdEdmbOvqy4O0adg" |
| name="types_of_test,_0aJ6cMlgEdmt3adZL5Dmdw" guid="_y-_PIMPdEdmbOvqy4O0adg" changeDate="2007-05-30T10:59:45.281-0700"> |
| <mainDescription><h3>
 |
| Introduction
 |
| </h3>
 |
| <p>
 |
| There's much more to testing software-oriented solutions than simply evaluating functions, interfaces, and
 |
| response-time characteristics. Additional tests should focus on other requirements attributes, such as:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| integrity (resistance to failure)
 |
| </li>
 |
| <li>
 |
| ability to be installed and executed on different platforms
 |
| </li>
 |
| <li>
 |
| ability to handle many requests simultaneously
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| To achieve this, testers develop different types of tests.&nbsp;Each test type has a specific objective and support
 |
| technique.&nbsp;Each technique focuses on testing one or more characteristics or attributes of the solution.
 |
| </p>
 |
| <p>
 |
| <em>Team members apply these types of tests at different scopes.</em> While <a class="elementLinkWithUserText" href="./../../../openup/roles/tester_9859B590.html" guid="_0ZM4MclgEdmt3adZL5Dmdw">Testers</a> are concerned with the
 |
| end-to-end solution,&nbsp;<a class="elementLinkWithUserText" href="./../../../openup/roles/developer_C633AB7.html" guid="_0YDosMlgEdmt3adZL5Dmdw">Developers</a> are usually focused on a specific unit or component of the <a class="elementLink" href="./../../../openup/workproducts/implementation_917CA61E.html" guid="_0YoQcMlgEdmt3adZL5Dmdw">Implementation</a>.
 |
| </p>
 |
| <h3>
 |
| Quality Dimension: Functionality
 |
| </h3>
 |
| <p>
 |
| <strong>Function test:</strong> Tests focused on validating the solution functions as intended, providing the required
 |
| services, methods, or use cases. This test is implemented and executed against different targets-of-test, including
 |
| units, integrated units, applications, and systems.
 |
| </p>
 |
| <p>
 |
| <strong>Security test:</strong> Tests focused on ensuring the target-of-test data (or systems) are accessible only to
 |
| those actors for which they are intended. This test is implemented and executed on various targets-of-test.
 |
| </p>
 |
| <p>
 |
| <strong>Volume test:</strong> Tests focused on verifying the target-of-test's ability to handle large amounts of data,
 |
| either as input, output, or persistent. Volume testing includes test strategies such as creating queries that would
 |
| return the entire contents of a database, or that would have so many restrictions that no data is returned, or where
 |
| the data entry has the maximum amount of data for each field.
 |
| </p>
 |
| <h3>
 |
| Quality Dimension:&nbsp;Usability
 |
| </h3>
 |
| <p>
 |
| <strong>Integrity test:</strong> Tests that focus on assessing the target-of-test's robustness (resistance to failure),
 |
| and technical compliance to language, syntax, and resource usage. This test is implemented and executed against
 |
| different targets, typically implementation units and components.
 |
| </p>
 |
| <p>
 |
| <strong>Structure test</strong>: Tests that focus on assessing the target-of-test's adherence to its design and
 |
| formation. For example, with web applications, theses tests might ensure that all links are connected, appropriate
 |
| content is displayed, and no content is orphaned.
 |
| </p>
 |
| <h3>
 |
| Quality Dimension: Reliability
 |
| </h3>
 |
| <p>
 |
| <strong>Stress test:</strong> A type of reliability test that focuses on evaluating how the system responds under
 |
| abnormal conditions. Stresses on the system could include extreme workloads, insufficient memory, unavailable services
 |
| and hardware, or limited shared resources. These tests are often performed to gain a better understanding of how and in
 |
| what areas the system will break, so that contingency plans and upgrade maintenance can be planned and budgeted for
 |
| well in advance.
 |
| </p>
 |
| <p>
 |
| <strong>Benchmark test:</strong> A type of performance test that compares the performance of a new or unknown
 |
| target-of-test to a known reference-workload.
 |
| </p>
 |
| <p>
 |
| <strong>Contention test:</strong> Tests focused on validating the target-of-test's ability to acceptably handle
 |
| multiple actor demands on the same resource (data records, memory, and so on).
 |
| </p>
 |
| <h3>
 |
| Quality Dimension: Performance
 |
| </h3>
 |
| <p>
 |
| <strong>Load test:</strong> A type of performance test used to assess the operational limits of a system under varying
 |
| workloads while the system-under-test remains constant. In some variants, the workload remains constant and the
 |
| configuration of the system-under-test is varied. Measurements are usually taken based on the workload throughout and
 |
| transaction response time. The variations in workload usually include emulation of average and peak workloads that
 |
| occur within normal operational tolerances.
 |
| </p>
 |
| <p>
 |
| <strong>Performance profiling:</strong> A test in which the target-of-test's timing profile is monitored, including
 |
| execution flow, data access, function and system calls to identify and address both performance bottlenecks and
 |
| inefficient processes.
 |
| </p>
 |
| <p>
 |
| <strong>Configuration test:</strong> Tests focused on ensuring the target-of-test functions as intended on different
 |
| hardware and software configurations. This test might also be implemented as a system performance test.
 |
| </p>
 |
| <h3>
 |
| Quality Dimension: Supportability
 |
| </h3>
 |
| <p>
 |
| <strong>Installation test:</strong> Tests focused on ensuring the target-of-test installs as intended on different
 |
| hardware and software configurations, and under different conditions (such as insufficient disk space or power
 |
| interruptions). This test is implemented and executed against applications and systems.
 |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
