It is worth noting that if you are recording ADO traffic then you usually require just one type library called msado15.dll. This is usually located in PROGRAM FILES | COMMON FILES | SYSTEM | ADO. If you are recording non-ado COM traffic then you should ask the developers of your COM application which type libraries are required. This is usually the fastest and most reliable way to ensure you get all the required type libraries for COM testing. If you do not have access to the developers then you can use SilkPerformer to log any missing type libraries during the recording phase. To do this simply do the following: Set up the application profile for the client application and add any interfaces which you are aware of. Choose SETTINGS | ACTIVE PROFILE | RECORD | COM Icon Here you will see some additional logging options, please check the "Show missing type information" checkbox and click OK. Record your client again. After recording close the client, stop the recorder and save the script. At this point you need to add the attached script to your SilkPerformer project. This script will parse the record.log of the script you just recorded and will write out to a .wrt file, all paths to .dll, .exe or .tlb files that may contain type library information. You must edit the LOGFILE constant in the script to point to the .record.log of the script you just recorded in the previous step. RegistryChecker.bdf NOTE - Not all files contain valid type libraries and not all type libraries are necessary for load testing. There are also type libraries responsible for defining client side GUI interfaces (such as ActiveX components). You can usually ignore any files that have an ocx extension when adding type libraries. NOTE: Since the introduction of GUI-level testing in SilkPerformer 2006 Release 2, it may be possible to loadtest applications that cannot be recorded successfully on the protocol- or API-levels by recording on the GUI level. Please refer to the GUI-Level Testing Support section of the Other Supported Environments chapter in the SilkPerformer User Guide for full details. Related documents: RegistryChecker.bdf Old KB# 18862
↧