Comments on: Continuous Testing for Visual Studio

By: Håvard

Håvard — Wed, 09 Mar 2011 20:59:37 +0000

@Tony Thanks for reporting. Technically this is not a bug, since the error list reference points to where the exception originated. We do however understand the expectation that you should end up at the line in the test from which the exception originated, and we will consider changing this behavior.

By: Tony Wang

Tony Wang — Wed, 09 Mar 2011 20:34:10 +0000

I think I may have come across a bug with reporting the correct file in the Error List window. We have written extension methods around the NUnit Assert class to make our tests more "fluent." When an assert fails, the file reference in the Error List is not the file containing the test, but rather the file of the extension method containing the Assert.

I have prepared a sample project that illustrates this issue. Thanks!

By: Håvard

Håvard — Mon, 07 Feb 2011 20:13:13 +0000

@necip Thanks for reporting. This is a general issue relating to Visual Studio add-in installations (prior to VS 2010). You'll need to work around by temporarily pointing your My Documents folder to a local drive, and then copying the add-in folder contents back to your network location after installing. See here for a tutorial.

By: Necip Karakas

Necip Karakas — Mon, 07 Feb 2011 17:39:47 +0000

Hi, As I wrote in my twit, could not install this tool for VS2008. I have XP on my computer an get the following error. “Could not access network location: \\mydomainname\users\myusername\\Visual Studio 2008\Addins.” I have my Addin folder on a network drive. I think the problem happens because of the double backslashes after username . Thanks necip

By: James Bradt

James Bradt — Thu, 13 Jan 2011 18:24:15 +0000

Fatal unit testing error

Good day, I'm attempting to try out this add-in (vs2010).

1) create a new vb command line project 2) add a class 3) create a new vb test project 4) add a new test 5) build the solution

At the bottom of the IDE, the following message flashes quickly

Fatal unit testing error: Unable to cast COM object of type 'System._ComObject' to interface type 'VSLangProj.VSProject'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{2CFBB26F-F6BF-480D-A546-95A0381CC411}' failed due to the following error: No such interface supported (Excepti...

That is all I can capture.

Manually clicking the 'Run All Tests in the Solution' button on the toolbar does work (and the simple default mstest passes).

Any suggestions on how to correct this?

Thanks, JB

By: Håvard

Håvard — Wed, 22 Dec 2010 22:50:42 +0000

@Rick Minerich For reference, I reply here as well. As we discussed on Twitter, the reason for your problem is that your project contains folders. The current version has issues with projects with folders in them. We have a fix upstream which will be in the next version. Thanks for reporting!

By: Rick Minerich

Rick Minerich — Wed, 22 Dec 2010 19:11:53 +0000

It appears that the comment system mangled my submission. Let's try again with html formatting:

module XunitTest

open Xunit

[] let newtest () = Assert.Equal (null, null)

By: Rick Minerich

Rick Minerich — Wed, 22 Dec 2010 19:08:55 +0000

Tests don't seem to run in my F# projects using xUnit 1.6.1. There's no error, I don't think it's even getting triggered. Here's an example of a simple F# test assembly:

module XunitTest

open Xunit

[] let newtest () = Assert.Equal (null, null)

By: Håvard

Håvard — Sat, 11 Dec 2010 00:41:54 +0000

@Robert Hanson:

Thank you for reporting this issue.

It is a known bug, which will be fixed in the next version.

The bug causes Continuous Testing to fail for solutions containing web sites to fail. Until the next version is released, you need to avoid working with solutions containing web sites to use Continuous Testing.

Obviously, this is not a great solution for you. The next version, which fixes the bug, is just around the corner, so we hope you will bear with us until then, and give us a new chance! Until then, you can disable Continuous Testing simply by unchecking "Run tests on successful build" under Tools > Options > Test Tools > Continuous Testing.

By: Robert Hanson

Robert Hanson — Fri, 10 Dec 2010 20:21:36 +0000

No unit tests run under the following scenario 1) Create a ASP.NET website. 2) Follow instructions here (http://msdn.microsoft.com/en-us/library/ms182526(v=vs.80).aspx) to add unit tests 3) Compile and run unit tests using visual studio 4) Build website – no unit tests apparently run; I tried creating a failing test too just to demonstrate that it is not working.

Does the CT runner work with a website build? or do I need to build the test project separately?