OpenUP/OpenUP_baseline_EN/exported_HTML_0_9/openup_basic/guidances/concepts/types_of_test.html - epf/org.eclipse.epf.nl-libraries - Git at Google

 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE html PUBLIC "-//W3C/DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd">
 <!-- VERSION rmc:7.1.0 -->
 <html xmlns="http://www.w3.org/1999/xhtml">
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
 <!-- START NON-TRANSLATABLE -->
 <title>\openup_basic\guidances\concepts\types_of_test.xmi</title>
 </head>
 <!-- WARNING: do not modify the generated comments in this file below this line.  They are used as markers for the import process. -->
 <body>
 Element Name: types_of_test.xmi<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: presentationName<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:presentationName,_0aJ6cMlgEdmt3adZL5Dmdw CRC: 3180024288 -->Types of Test<!-- END:presentationName,_0aJ6cMlgEdmt3adZL5Dmdw -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: briefDescription<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:briefDescription,_0aJ6cMlgEdmt3adZL5Dmdw CRC: 2205558808 -->Testing is applied to different types of targets, in different stages or levels of work effort. This Concept introduces various types of test.<!-- END:briefDescription,_0aJ6cMlgEdmt3adZL5Dmdw -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: mainDescription<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:mainDescription,_y-_PIMPdEdmbOvqy4O0adg CRC: 2487706777 --><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 <strong>quality dimensions</strong> they
     address.
 </p>
 <h3>
     Quality Dimension: Functionality
 </h3>
 <h4>
     Types of Test
 </h4>
 <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>
     Quality Dimension:&nbsp;Usability
 </h3>
 <h4>
     Types of Test
 </h4>
 <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>
     Quality Dimension: Reliability
 </h3>
 <h4>
     Types of Test
 </h4>
 <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>
     Quality Dimension: Performance
 </h3>
 <h4>
     Types of Test
 </h4>
 <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>
     Quality Dimension: Supportability
 </h3>
 <h4>
     Types of Test
 </h4>
 <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><!-- END:mainDescription,_y-_PIMPdEdmbOvqy4O0adg -->
 </body>
 </html>
	<?xml version="1.0" encoding="UTF-8"?>
	<!DOCTYPE html PUBLIC "-//W3C/DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd">
	<!-- VERSION rmc:7.1.0 -->
	<html xmlns="http://www.w3.org/1999/xhtml">
	<head>
	<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
	<!-- START NON-TRANSLATABLE -->
	<title>\openup_basic\guidances\concepts\types_of_test.xmi</title>
	</head>
	<!-- WARNING: do not modify the generated comments in this file below this line. They are used as markers for the import process. -->
	<body>
	Element Name: types_of_test.xmi<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: presentationName<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:presentationName,_0aJ6cMlgEdmt3adZL5Dmdw CRC: 3180024288 -->Types of Test<!-- END:presentationName,_0aJ6cMlgEdmt3adZL5Dmdw -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: briefDescription<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:briefDescription,_0aJ6cMlgEdmt3adZL5Dmdw CRC: 2205558808 -->Testing is applied to different types of targets, in different stages or levels of work effort. This Concept introduces various types of test.<!-- END:briefDescription,_0aJ6cMlgEdmt3adZL5Dmdw -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: mainDescription<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:mainDescription,_y-_PIMPdEdmbOvqy4O0adg CRC: 2487706777 --><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. 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. Each test type has a specific
	objective and support technique. 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 <strong>quality dimensions</strong> they
	address.
	</p>
	<h3>
	Quality Dimension: Functionality
	</h3>
	<h4>
	Types of Test
	</h4>
	<p>
	<strong>Function test:</strong> 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> 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 and output or resident within the database. 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>
	Quality Dimension: Usability
	</h3>
	<h4>
	Types of Test
	</h4>
	<p>
	<strong>Usability test:</strong> 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> 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-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. 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>
	Quality Dimension: Reliability
	</h3>
	<h4>
	Types of Test
	</h4>
	<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 and system.
	</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>
	<h4>
	Types of Test
	</h4>
	<p>
	<strong>Load test:</strong>  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. 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 in-line 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 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>  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>
	<h4>
	Types of Test
	</h4>
	<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><!-- END:mainDescription,_y-_PIMPdEdmbOvqy4O0adg -->
	</body>
	</html>