信息管理方向的CRM系统的相关文档

        enhanced to increase the number of times each function is executed to
        simulate several different users over a specified period.</li>
      <li>All time or date sensitive functions will be executed using valid and
        invalid dates or time periods.</li>
      <li>All functions that occur on a periodic schedule will be executed /
        launched at the appropriate time.</li>
      <li>Testing will include using valid and invalid data, to verify the
        following:</li>
      <li>The expected results occur when valid data is used.</li>
      <li>The appropriate error / warning messages are displayed when invalid
        data is used.</li>
      <li>Each business rule is properly applied.</li></font>
    </ul>
    </td>
  </tr>
  <tr>
    <td width="34%" valign="TOP"><font size="2">Completion Criteria:</font></td>
    <td width="66%" valign="TOP">
    <ul>
      <font size="2">
      <li>All planned tests have been executed.</li>
      <li>All identified defects have been addressed.</li></font>
    </ul>
    </td>
  </tr>
  <tr>
    <td width="34%" valign="TOP"><font size="2">Special Considerations:</font></td>
    <td width="66%" valign="TOP">
    <ul>
      <font size="2">
      <li>System dates and events may require special support activities</li>
      <li>Business model is required to identify appropriate test requirements
        and procedures.</li></font>
    </ul>
    </td>
  </tr>
</table>
</center></div>

<blockquote>
  <font size="2">
  <p><strong>4. <a name="_Toc327254065"></a><a name="_Toc327255030"></a><a name="_Toc327255099"></a><a name="_Toc327255338"></a><a name="_Toc433104447"></a><font face="Arial" size="2"><i><a name="_Toc447185695">User
  Interface Testing</a></i></font></strong></p>
  </font>
</blockquote>
<blockquote>
  <blockquote>
    <font size="2">
    <p><a name="_Toc327254066"></a><a name="_Toc327255031"></a><a name="_Toc327255100"></a><a name="_Toc327255339">User
    Interface testing verifies a user's interaction with the software. The
    goal of UI Testing is to ensure that the User Interface provides the user
    with the appropriate access and navigation through the functions of the
    applications. In addition, UI Testing ensures that the objects within the UI
    function as expected and conform to corporate or industry standards.</a></p></font>
  </blockquote>
</blockquote>
<a name="_Toc327255339"></a>
<p align="center">&nbsp;</p>
<div align="center"><center>

<table cellspacing="0" border="0" cellpadding="7" width="90%">
  <tr>
    <td width="34%" valign="TOP"><font size="2">Test Objective:</font></td>
    <td width="66%" valign="TOP"><font size="2">Verify the following:
    </font><ul><font size="2">
      <li>Navigation through the application properly reflects business
        functions and requirements, including window to window, field to field,
        and use of access methods (tab keys, mouse movements, accelerator keys)</li>
      <li>Window objects and characteristics, such as menus, size, position,
        state, and focus conform to standards.</li></font>
    </ul>
    </td>
  </tr>
  <tr>
    <td width="34%" valign="TOP"><font size="2">Technique:</font></td>
    <td width="66%" valign="TOP">
    <ul>
      <font size="2">
      <li>Create / modify tests for each window to verify proper navigation and
        object states for each application window and objects.</li></font>
    </ul>
    </td>
  </tr>
  <tr>
    <td width="34%" valign="TOP"><font size="2">Completion Criteria:</font></td>
    <td width="66%" valign="TOP"><font size="2">Each window successfully
    verified to remain consistent with benchmark version or within acceptable
    standard</font></td>
  </tr>
  <tr>
    <td width="34%" valign="TOP"><font size="2">Special Considerations:</font></td>
    <td width="66%" valign="TOP">
    <ul>
      <font size="2">
      <li>Not all properties for custom and third party objects can be accessed.</li></font>
    </ul>
  </td>
</tr>
</table>
</center></div>

<blockquote>
  <p>
  <font size="2"><strong>5. <a name="_Toc433104448"></a></strong></font><font face="Arial" size="2"><i><strong><a name="_Toc447185696">Performance
  Testing</a></strong></i></font></p>
  
</blockquote>
<blockquote>
  <blockquote>
    <font size="2">
    <p>Performance testing measures response times, transaction rates, and other
    time sensitive requirements. The goal of Performance testing is to verify
    and validate the performance requirements have been achieved. Performance
    testing is usually executed several times, each using a different
    &quot;background load&quot; on the system. The initial test should be
    performed with a &quot;nominal&quot; load, similar to the normal load
    experienced (or anticipated) on the target system. A second performance test
    is run using a peak load.</p>
    <p>Additionally, Performance tests can be used to profile and tune a system's
    performance as a function of conditions such as workload or hardware
    configurations.</p>
    <p>NOTE: Transactions below refer to &quot;logical business
    transactions.&quot; These transactions are defined as specific functions
    that an end user of the system is expected to perform using the application,
    such as add or modify a given contract.</p></font>
  </blockquote>
</blockquote>
<p align="center">&nbsp;</p>
<div align="center"><center>

<table cellspacing="0" border="0" cellpadding="7" width="90%">
  <tr>
    <td width="34%" valign="TOP"><font size="2">Test Objective:</font></td>
    <td width="66%" valign="TOP"><font size="2">Validate System Response time
    for designated transactions or business functions under a the following two
    conditions:
    <p>- normal anticipated volume</p>
    <p>- anticipated worse case volume</font></td>
  </tr>
  <tr>
    <td width="34%" valign="TOP"><font size="2">Technique:</font></td>
    <td width="66%" valign="TOP">
    <ul>
      <font size="2">
                  <li>Use Test Scripts developed for Business Model Testing (System 
                    Testing).</li>
      <li>Modify data files (to increase the number of transactions) or modify
        scripts to increase the number of iterations each transaction occurs.</li>
      <li>Scripts should be run on one machine (best case to benchmark single
        user, single transaction) and be repeated with multiple clients (virtual
        or actual, <i>see special considerations below).</i></li></font>
    </ul>
    </td>
  </tr>
  <tr>
    <td width="34%" valign="TOP"><font size="2">Completion Criteria:</font></td>
    <td width="66%" valign="TOP">
    <ul>
      <font size="2">
      <li>Single Transaction / single user: Successful completion of the test
        scripts without any failures and within the expected / required time
        allocation (per transaction)</li>
      <li>Multiple transactions / multiple users: Successful completion of the
        test scripts without any failures and within acceptable time allocation.</li></font>
    </ul>
    </td>
  </tr>
  <tr>
    <td width="34%" valign="TOP"><font size="2">Special Considerations:</font></td>
    <td width="66%" valign="TOP">
    <ul>
      <font size="2">
      <li>Comprehensive performance testing includes having a
        &quot;background&quot; load on the server. There are several methods
        that can be used to perform this, including:</li>
      <ul>
        <li>&quot;Drive transactions&quot; directly to the server, usually in
          the form of SQL calls.</li>
        <li>Create &quot;virtual&quot; user load to simulate many (usually
          several hundred) clients. Remote Terminal Emulation tools are used to
          accomplish this load. This technique can also be used to load the
          network with &quot;traffic.&quot;</li>
        <li>Use multiple physical clients, each running test scripts to place a
          load on the system.</li>
      </ul>
      <li>Performance testing should be performed on a dedicated machine or at a
        dedicated time. This permits full control and accurate measurement.</li>
      <li>The databases used for Performance testing should be either actual
        size, or scaled equally.</li></font>
    </ul>
    </td>
  </tr>
</table>
</center></div>

<blockquote>
  <font size="2">
  <p>6. <a name="_Toc417790796"></a><a name="_Toc433104449"></a><font face="Arial" size="2"><i><strong><a name="_Toc447185697">Load
  Testing</a></strong></i></font></p>
  </font>
</blockquote>
<blockquote>
  <blockquote>
    <font size="2">
    <p>Load testing measures subjects the system-under-test to varying workloads
    to evaluate the system's ability to continue to function properly under
    these different workloads. The goal of load testing is to determine and
    ensure that the system functions properly beyond the expected maximum
    workload. Additionally, load testing evaluates the performance
    characteristics (response times, transaction rates, and other time sensitive
    issues).</p>
    <p>NOTE: Transactions below refer to &quot;logical business
    transactions.&quot; These transactions are defined as specific functions
    that an end user of the system is expected to perform using the application,
    such as add or modify a given contract.</p></font>
  </blockquote>
</blockquote>
<div align="center"><center>

<table cellspacing="0" border="0" cellpadding="7" width="90%">
  <tr>
    <td width="34%" valign="TOP"><font size="2">Test Objective:</font></td>
    <td width="66%" valign="TOP"><font size="2">Verify System Response time for
    designated transactions or business cases under varying workload conditions.</font></td>
  </tr>
  <tr>
    <td width="34%" valign="TOP"><font size="2">Technique:</font></td>
    <td width="66%" valign="TOP">
    <ul>
      <font size="2">
      <li>Use tests developed for Business Cycle Testing.</li>
      <li>Modify data files (to increase the number of transactions) or the
        tests to increase the number of times each transaction occurs.</li></font>
    </ul>
    </td>
  </tr>
  <tr>
    <td width="34%" valign="TOP"><font size="2">Completion Criteria:</font></td>
    <td width="66%" valign="TOP">
    <ul>
      <font size="2">
      <li>Multiple transactions / multiple users: Successful completion of the
        tests without any failures and within acceptable time allocation.</li></font>
    </ul>
    </td>
  </tr>
  <tr>
    <td width="34%" valign="TOP"><font size="2">Special Considerations:</font></td>
    <td width="66%" valign="TOP">
    <ul>
      <font size="2">
      <li>Load testing should be performed on a dedicated machine or at a
        dedicated time. This permits full control and accurate measurement.</li>
      <li>The databases used for load testing should be either actual size, or
        scaled equally.</li></font>
    </ul>
    </td>
  </tr>
</table>
</center></div>

<blockquote>
  <font size="2">
  <p><strong>7. <a name="_Toc327254067"></a><a name="_Toc327255032"></a><a name="_Toc327255101"></a><a name="_Toc327255340"></a><a name="_Toc433104450"></a><font face="Arial" size="2"><i><a name="_Toc447185698">Stress
  Testing</a></i></font></strong></p>
  </font>
</blockquote>
<blockquote>
  <blockquote>
    <font size="2">
    <p><a name="_Toc314978540"></a>Stress testing is intended to find errors due to
    low resources or competition for resources. Low memory or disk space may
    reveal defects in the software that aren't apparent under normal conditions.
    Other defects might results from competition for shared resource like
    database locks or network bandwidth. Stress testing identifies the peak load
    the system can handle.</p>
    <p>NOTE: References to transactions below refer to logical business
    transactions.</p></font>
  </blockquote>
</blockquote>
<a name="_Toc314978540"></a>
<div align="center"><center>

<table cellspacing="0" border="0" cellpadding="7" width="90%">
  <tr>
    <td width="34%" valign="TOP"><font size="2">Test Objective:</font></td>
    <td width="66%" valign="TOP"><font size="2">Verify that the system and
    software function properly and without error under the following stress
    conditions:
    <ul>
      <li>little or no memory available on the server (RAM and DASD)</li>
      <li>maximum (actual or physically capable) number of clients connected (or
        simulated)</li>
      <li>multiple users performing the same transactions against the same data