tag:blogger.com,1999:blog-5569894.post704649791902720592..comments2023-11-08T13:18:07.006+00:00Comments on Distributed Memory: Getting coverage.exe (trunk) to work with nUnit and .net 4Steve Gilhamhttp://www.blogger.com/profile/03622573187942388226noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-5569894.post-88782396703525770942010-04-24T22:34:55.642+01:002010-04-24T22:34:55.642+01:00With old NCover you went something like
%NCOVER% ...With old NCover you went something like<br /><br />%NCOVER% %NUNIT% $(TargetFileName) /noshadow //reg //a "Tinesware.Infrastructure;Tinesware.InfrastructureTests;Tinesware.Rules;Tinesware.TestData;CSharpTests"<br /><br />where the coverage tool listened to the implied instrumentation in the CLR itself. With coverage.exe you would do<br /><br />coverage [list of assemblies] /r /x <br />.\coverage.xml<br />%NUNIT% [unit test assembly]<br /><br />which instruments the code first, then in the second step, executes it.<br /><br />Notionally, you can concatenate the two steps with coverage's /exe command line switch, but I find that doing so can cause nUnit to fault (pretty much every time when running as a post-build step inside Visual Studio, less often at the command line).Steve Gilhamhttps://www.blogger.com/profile/03622573187942388226noreply@blogger.comtag:blogger.com,1999:blog-5569894.post-39379270084321500292010-04-22T22:07:19.386+01:002010-04-22T22:07:19.386+01:00What do you mean by two stage process? I am trying...What do you mean by two stage process? I am trying to get this working, no F# here but would sure like to get some coverage out of my unit tests.Ryanhttps://www.blogger.com/profile/16108673234669129574noreply@blogger.com