Troubleshooting Data Diagnostic Adapters
Note: Cross posted from Rubel’s Blog.
Permalink
As I had mentioned in my earlier posts that you can enable a number of Diagnostic Data Adapters in test setting so as to collect various types of data while running tests in Test Runner. Sometimes it is confusing if you don’t get any log from a diagnostic data adapter though you’ve enabled it in test setting. There can be many reasons for this behavior like data collector is not expected to generate log in that particular scenario, data collector pre-reqs are not met successfully, that particular data collector is not expected to generate log at all e.g Network Emulation. This post intends to explain various reasons for log generation failure from each data diagnostic adapter. This is NOT an advanced guide for troubleshooting all data diagnostic adapters’ warnings / errors but you can quickly refer to it if you are not seeing logs from a data diagnostic adapter.
IntelliTrace and Test Impact
Both IntelliTrace and Trace Impact data collectors have a number of pre-reqs:
1) They work only for applications written with managed code
2) AuT process need to be started after launching the Test Runner as they needs to instrument modules, binaries or executables that are loaded into a process.
3) ASP .NET Client Proxy for IntelliTrace and Test Impact needs to be enabled in test setting for client role while collecting test data from ASP. NET applications hosted on remote boxes.
4) Computer’s IP address / hostname need to be used instead of “127.0.0.1” “local host” while collecting data from locally hosted ASP.NET apps e.g. please use http://microsof-7f734b/webapplication1/default.aspx instead of http://localhost/webapplication1/default.aspx
5) AuT Process / required modules are included for data collection in configuration settings of collectors. Please check articles mentioned below for details on configuring IntelliTrace and Test Impact:
a. Configuring IntelliTrace
b. Configuring Test Impact
So if
