|
Hi Chris, That seemed to work. I had to
back track quite a bit though ..\.. In the end I created two .testrunconfig
files, one for the local tests, and one for the build. Although now my unit
test is failing, for some reason WatiN is spawning two IE instances and one is
locking up!!! From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Chris Burrows Mitch, I did a bit more investigation
into this issue and it looks like I might nearly have it cracked.
The issue is definitely to do with the location of where the dll is being
executed. I changed the binary file and the pdb file location of
the webapplication project and it seems to have started to give code coverage
results. However, I need to do some further investigation to ensure that
this was actually the fix. I edited the .testrunconfig file
manually. However, I suspect if you open up the solution from the
build\<BuildTypeName>\Sources directory on the build machine and add the
dll from the binaries\<Configuration Type>\_PublishedWebSite\<WebSiteName>\bin
directory in the code coverage section and then check it in as well it should
work. I only had the opportunity to
try one thing before I had to leave tonight so I’m going to try a couple
more things out tomorrow to confirm that what I’m seeing is correct. From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mitch
Denny Do we know if it even attaches
to the Cassini process? From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Chris Burrows Mitch, I
have the same problem and don't have an answer yet. The issue lies
in the fact that when you run the test, the web site is being run from the
...\_PublishedWebSite\ directory where as the instrumented DLL's is siting
in the \TEST\OUT directory. Therefore, you don't get any code
coverage. I'm playing around to see if I can add in a DLL in
the output directory by modifying the code coverage directory in the
.testrunconfig file (see below). I'll let you know how this goes but my
gut feeling is that it will not work. <codeCoverageItems
type="System.Collections.Generic.List`1[[Microsoft.VisualStudio.TestTools.Common.CodeCoverageItem,
Microsoft.VisualStudio.QualityTools.Common, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a]]"> Cheers Chris From: [EMAIL PROTECTED] on behalf of Mitch
Denny Hi all, Has anyone managed to get code coverage working in Team
Build with Web Application Projects? I spent about eight hours the other night
trying to get this working, but for whatever reason it wouldn’t pick up
the coverage stats from a Web Application Project (the replacement project time
for WebSite Projects that shipped out of the box). Has anyone else tried this? OzTFS.com
- to unsubscribe from this list, send a message back to the list with
'unsubscribe' as the subject. OzTFS.com
- to unsubscribe from this list, send a message back to the list with
'unsubscribe' as the subject. OzTFS.com
- to unsubscribe from this list, send a message back to the list with
'unsubscribe' as the subject. OzTFS.com
- to unsubscribe from this list, send a message back to the list with
'unsubscribe' as the subject. Powered by mailenable.com - List managed by www.readify.net |
- [OzTFS] Has anyone managed to get code coverage working in T... Mitch Denny
- RE: [OzTFS] Has anyone managed to get code coverage wor... Chris Burrows
- RE: [OzTFS] Has anyone managed to get code coverage... Mitch Denny
- RE: [OzTFS] Has anyone managed to get code cove... Chris Burrows
- RE: [OzTFS] Has anyone managed to get code ... Mitch Denny
