| <?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.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="_y-_PIMPdEdmbOvqy4O0adg" name="testing_qualitative_rqmts,_0aJ6cMlgEdmt3adZL5Dmdw" guid="_y-_PIMPdEdmbOvqy4O0adg" changeDate="2008-10-14T10:51:17.000-0700" version="7.2.0"> |
| <mainDescription><h3>
 |
| Introduction
 |
| </h3>
 |
| <p>
 |
| There is much more to testing computer software than simply evaluating the functions, interface, and response-time
 |
| characteristics of a target-of-test.&nbsp;Additional tests must focus on characteristics and attributes, such as the
 |
| target-of-test.
 |
| </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, many different types of tests are implemented and executed.&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 target-of-test.
 |
| </p>
 |
| <p>
 |
| The following sections list the types of test based on the most obvious quality&nbsp;attributes they address.
 |
| </p>
 |
| <h3>
 |
| Types of test for&nbsp;Functionality
 |
| </h3>
 |
| <p>
 |
| <strong>Function test:</strong>&nbsp;Tests focused on validating the target-of-test 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>&nbsp;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>&nbsp;Tests focused on verifying the target-of-test's ability to handle large amounts of
 |
| data, either as input and output or resident within the database.&nbsp;Volume testing includes test strategies such as
 |
| creating queries that would return the entire contents of the 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>
 |
| Types of test for&nbsp;Usability
 |
| </h3>
 |
| <p>
 |
| <strong>Usability test:</strong>&nbsp;Tests that focus on:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| human factors
 |
| </li>
 |
| <li>
 |
| esthetics
 |
| </li>
 |
| <li>
 |
| consistency in the user interface
 |
| </li>
 |
| <li>
 |
| online and context-sensitive help
 |
| </li>
 |
| <li>
 |
| wizards and agents
 |
| </li>
 |
| <li>
 |
| user documentation
 |
| </li>
 |
| <li>
 |
| training materials
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| <strong>Integrity test:</strong>&nbsp;Tests that focus on assessing the target-of-test's robustness (resistance to
 |
| failure), and technical compliance to language, syntax, and resource usage.&nbsp;This test is implemented and executed
 |
| against different targets-of-tests, including units and integrated units.
 |
| </p>
 |
| <p>
 |
| <strong>Structure test</strong>: Tests that focus on assessing the target-of-test's adherence to its design and
 |
| formation.&nbsp;Typically, this test is done for Web-enabled applications ensuring that all links are connected,
 |
| appropriate content is displayed, and no content is orphaned.
 |
| </p>
 |
| <h3>
 |
| Types of test for&nbsp;Reliability
 |
| </h3>
 |
| <p>
 |
| <strong>Stress test:</strong>&nbsp; A type of reliability test that focuses on evaluating how the system responds under
 |
| abnormal conditions.&nbsp;Stresses on the system could include extreme workloads, insufficient memory, unavailable
 |
| services and hardware, or limited shared resources.&nbsp;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>&nbsp; A type of performance test that compares the performance of a new or unknown
 |
| target-of-test to a known reference-workload and system.
 |
| </p>
 |
| <p>
 |
| <strong>Contention test:</strong>&nbsp; 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>
 |
| Types of test for Performance
 |
| </h3>
 |
| <p>
 |
| <strong>Load test:</strong>&nbsp; A type of performance test used to validate and assess acceptability of the
 |
| operational limits of a system under varying workloads while the system-under-test remains constant.&nbsp;In some
 |
| variants, the workload remains constant and the configuration of the system-under-test is varied.&nbsp; Measurements
 |
| are usually taken based on the workload throughout and in-line transaction response time.&nbsp;The variations in
 |
| workload usually include emulation of average and peak workloads that occur within normal operational tolerances.
 |
| </p>
 |
| <p>
 |
| <strong>Performance profile:</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>&nbsp; Tests focused on ensuring the target-of-test functions as intended on
 |
| different hardware and software configurations.&nbsp;This test might also be implemented as a system performance test.
 |
| </p>
 |
| <h3>
 |
| Types of test for Supportability
 |
| </h3>
 |
| <p>
 |
| <strong>Installation test:</strong>&nbsp; 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).&nbsp;This test is implemented and executed against applications and systems.
 |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
