Confirm that any validation or extraction rules are attached to the correct request.
You run your Web test by using the Web test engine, and view the results in the Web Test Viewer. The Web Test Viewer contains a tab that displays the HTTP response for each of the requests in your Web test. The HTTP response is the data of your Web test, that is, the data that tells you if your Web application is working correctly or not.
Validation and extraction rules that you add to your test are executed against the HTTP response.
You can also add validation rules to determine whether your Web test is working correctly.
ActiveX controls in your Web application will fall into three categories, depending on how they work at the HTTP level.
Your ActiveX control is not doing any work at the HTTP level, and is just displaying something visual on the page. In this case, you will not have to add any special handling to your Web test.
Your ActiveX control is not doing any work at the HTTP level, but you want to test it. For example if you have a very large ActiveX control, you might want to test it in a load test to see whether it is affecting the speed of your Web application. In this case, add the ActiveX control as a dependent request to the page, and it will be downloaded during the test run.
Your ActiveX control is doing work at the HTTP level, for example retrieving data from a Web service. In this case, you must convert your test to a coded Web test and add the HTTP requests manually, or use the Fiddler tool that is described next.
The Fiddler Tool
The disadvantages of Fiddler are that it does not currently support SSL, it does not automatically track hidden fields, such as ViewState, and it does not filter out dependent requests.
Fiddler is available at http://www.fiddlertool.com. For more information about how to use Fiddler, see http://go.microsoft.com/fwlink/?linkid=56113.