Managing the Migration Process

Integration Testing

Once the server has passed unit testing, you’re ready to evaluate it in a larger context of a network or server group during integration testing. Table 2.9 describes some common integration tests. You might want to include additional items in your own test process.

Table 2.9 Integration Tests

Integration Test	Description
Network identification	Verify that the server is correctly identified on the network.
Application integration	Test ASP applications that access backend databases or other remote objects, to verify that they function as expected and that permissions and script settings (such as time-out) are set correctly.
Stress, or load testing	Measure Web site performance, working with a replica of the site in a lab environment with multiple clients to simulate load on the servers. WCAT, a useful tool for this simulation, is provided on the Resource Kit companion CD. You can also check how individual Web sites are using the CPU by using IIS 5.0 process accounting, as described in the IIS 5.0 online product documentation.
Server availability	Measure availability of the server on the network by using the HTTP Monitoring Tool, which is included on the Resource Kit companion CD. It is described in a white paper you can read at http://msdn.microsoft.com/workshop/server/.
Performance monitoring and tuning	Monitor server performance by using the HTTP Monitoring Tool, as described in a white paper you can read at http://msdn.microsoft.com/workshop/server/. See also Monitoring and Tuning Your Server in this book and the “Calculating Connection Performance” topic in the IIS 5.0 online product documentation.
Security functionality	Test the various possible iterations of the system to verify that security performs as expected in each scenario. You can generate tests to exercise these system variations from a matrix that includes: Each secured system component, such as Microsoft® Internet Explorer 5, IIS 5.0, and SQL Server. Variants in the security implementation of each component; for example, browser Secure Sockets Layer (SSL) security (48 bit, 128 bit, or ServerGated 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.
Security against penetration	Test security against intrusion, as described in Security in this book.