Performing system tests

This topic provides information about performing system tests on Microsoft Provisioning System.

With system testing, also called integration testing, you can evaluate the functioning of your servers or your code in the larger context of a network or server group. The following table describes some common system tests. You might want to include additional testing elements in your own test process.

System Test Description
Network identification Verify that the server is correctly identified on the network.
Domain controller configuration It is recommended that you use the DCDiag tool to test your domain controller. You should run DCDiag on each domain controller to verify domain configuration. For more information about using DCDiag, see article Q265706 "DCDiag and NetDiag in Windows 2000 Facilitate Domain Join and DC Creation" in the Microsoft Knowledge Base and "Chapter 10: Active Directory Diagnostics and Recovery" at the Microsoft Web site. (http://www.microsoft.com/) Follow the procedures outlined in these articles to verify that your domain controller is correctly configured.
Domain controller communication It is recommended that you use the NetDiag tool to verify that the computers in your deployment can communicate with your domain controller and network. For more information about using this tool, see article Q265706 "DCDiag and NetDiag in Windows 2000 Facilitate Domain Join and DC Creation" in the Microsoft Knowledge Base and "Chapter 10: Active Directory Diagnostics and Recovery" at the Microsoft Web site. (http://www.microsoft.com/)
Application integration Test applications that access databases or other remote objects to verify that the applications function as expected and that permissions and script settings (such as time-outs) are set correctly.
Namespace integration Test the functioning of new or modified namespaces to verify that they operate as expected and desired.
Stress testing or load testing Measure server performance, working with a replica of the system in a lab environment with multiple clients to simulate load on the servers.
Server availability Measure availability of the server on the network.
Performance monitoring Monitor server performance.
Security functionality Test the various possible iterations of the system to verify that your security measures perform as expected in each scenario. Generate tests to exercise these system variations using a matrix that includes the following:
  • Each secured system component, such as Microsoft Internet Explorer 5.0, IIS 5.0, and SQL Server 2000.
  • Variants in the security implementation of each component; for example, browser Secure Sockets Layer (SSL) security (48 bit, 128 bit, or Server­Gated Cryptography [SGC]), IIS 5.0 authentication (none, Basic, or integrated Windows authentication), and so forth.
  • Communication protocols between system components, such as named pipes and TCP/IP sockets.