So in this post we are going to focus on the client portion of our environment. How it works and what can possibly go wrong.
As we learnt in part II we need to turn on the ASP.NET Client Proxy for IntelliTrace and Test Impact in order to get Test Impact data collected. Why is this? What does it do? What can go wrong?
After some investigation I have found the following. This setting actually changes your IE (or other browsers) proxy settings in order to intercept and monitor the calls. If you start a test (with Impact Analysis enabled) and then start and new instance (not tab) of IE, go check out the proxy settings and you will see the following:-
IntelliTrace is configured to collect data from IIS, but
no Web request was intercepted during the test. Verify that the "ASP.NET
Client Proxy for IntelliTrace and Test Impact" is selected in the diagnostics
and data page of your test settings, and that "localhost" or "127.0.0.1" is not
being used to contact the server. You can safely ignore this warning if
you are not testing a web application or web service on the IIS server.
Now we cannot safely ignore this because we are testing a web application. So the secret is to uncheck the pac script setting in IE before launching a new IE window to run the test. e.g.
- open a new instance of IE
- uncheck the pac script option
- close the instance
- run test
- open new ie instance to run application under test, this will now have the correct proxy settings.
Happy testing! This leads us on to part 4 - What happens on the web server!