Trouble getting symbol coverage in IIS

Trouble getting symbol coverage in IIS

Hi!

I'm running IIS under ncover, and have a selenium suite running against it.

I'm getting lots of code coverage, but for some reason I can't get symbol coverage for the dlls of our code. I am getting branch coverage and method coverage, but I really want symbol coverage. Also I am getting some symbol coverage from .NET dlls, but not our product DLLs.

We have an in-house publishing system publish code to the iis server. It's release code, but the pdb files are included.

I'm running NCover Complete v3.4.12.6869 x64

Any ideas?

Sam


RE: Trouble getting symbol coverage in IIS

ichc,

Thanks for the question! These other dlls...are they .NET code? NCover only covers managed code.


RE: Trouble getting symbol coverage in IIS

Hi

Yes they are .net code. We have ncover successfully doing code coverage for them in our unit tests. However, when I try to get the code coverage for them while running under IIS, I get branch and method coverage, but no symbol coverage.

Sam


RE: Trouble getting symbol coverage in IIS

Hi, Sam.

Are the PDB files for your dlls in the same folder as the dlls you're calling? We require these files to gather symbol coverage; and I've seen before where folks didn't have these in their folders, causing errors like the one you describe. If you have your PDBs in the folders, please send me a support ticket at support@ncover.com.

Thanks!


RE: Trouble getting symbol coverage in IIS

even i have the same issue.

we do have pdb files in there where dll's are still symbol says N/A.

this is for profiling on IIS.


RE: Trouble getting symbol coverage in IIS

i was able to figure out .

the solution is run ncover.console.exe //iis "dll name"

dll name should not have .dll extension and quoted with "".

example:your dll is xyz.dll

ncover.console.exe //iis "xyz"


RE: Trouble getting symbol coverage in IIS

Fantastic! Thanks for the post, swathi.


RE: Trouble getting symbol coverage in IIS

ncover.console.exe //iis //a "xyz"

my bad..

and by the way if we pass

ncover.console.exe //iis //a "xyz" //l coverage.log //ll "verbose" it will generate you a log.

if we see the error in the log.

Failed to to module ... in (some directory x) (though the pdb ther).

try copying PDB there in hte (direcoryx) and run hte command

you should be able to get symbol coverage.


RE: Trouble getting symbol coverage in IIS

Exactly. NCover always requires PDBs to get symbol coverage. Thanks for the note!