Share via

Test process

  • Article

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

Test process

Test your service profiles to ensure that all planned functionality is implemented and working as planned.

Install and use each of your service profiles on each target operating system. If you distribute the service profile on disk and by e-mail, test each method. If you are providing multiple language versions, test each one on the operating system with the appropriate national language.

Note

  • If you have users with previous versions of your service profile, test Connection Manager on computers on which your previous service profiles are installed, as well as on computers that have not had previous versions installed.

Following are basic testing steps:

For each service profile and scenario, use Connection Manager to do all of the following:

To test your service profile

  1. Install the service profile, as described in a readme or other documentation that you provide to the user.

  2. Provide the required user data (user name, user password, and so on) needed to connect.

  3. Select a Point of Presence (POP) from the phone book and establish a connection.

  4. View network resources while connected to your service (check connection while viewing URL).

  5. Disconnect from your service.

  6. Uninstall the service profile.

Test criteria

As you install and use Connection Manager, ensure that each service profile has the appearance, features, functionality, and usability that you want:

  • Do the screens contain the appropriate titles, text, and graphics, and does each screen appear completely and correctly?

  • Are all of the required programs included in the service profile? If not, are all required programs available on all target operating systems?

  • Do all menu items for the notification area shortcut function appropriately?

  • Do you have appropriate Help topics, including troubleshooting Help, for all functions and features? Do these Help files match the service profile? If you customized any Help topics, do they appear as expected?

  • Is everything formatted and spelled correctly, including the license agreement, the screen text, the text in the Connection Manager dialog box, and other user information?

  • Is all the information needed to install and use Connection Manager and the service profile available when and where it is needed?

  • If you provided custom dial-up entries (especially scripts), do they work as intended?

  • If you support such connections, can you establish both direct and VPN connections?

  • If you included any pre-connect, pre-tunnel, post-connect, pre-dial, on-error, on-cancel, or disconnect custom actions or monitored applications, do they work as expected?

  • If you edited your .cms and other service-profile files, do your custom entries perform as expected?

  • If you use code signing, does it display the authentication notice as expected?

  • Can you connect using POPs in the phone book for each of the service types you support?

  • If you use a firewall, are the firewall proxy settings correct?

  • Do the components of Connection Point Services provide the required functionality, as described in the Connection Point Services documentation?

Note

  • You must build profiles on a server operating system that is designed for the same processor set as the client computers on which users will install the profile. For example, if you want to build a profile for users running Windows XP Professional x64 Edition, you must build that profile on a server that is running an x64-based version of Windows Server 2003.