nunit4teambuild Work Item Rss Feed

Commented Issue: Add Support For Inconclusive Tests [5282]

MrKWatkins — Sun, 18 Oct 2009 17:12:02 GMT

Both NUnit and MSTest have a concept of inconclusive tests; make sure they are transformed correctly.
Comments: ** Comment from web user: MrKWatkins **

Turns out there isn't anything like inconclusive="True" in the NUnit output to make this nice and easy. Inconclusive tests have success="False" on their test-case element just like failures; however they lack a child failure element. Details of inconclusive messages (from Assert.Inconclusive(string)) are not included in the XML. I have raised a bug with NUnit (https://bugs.launchpad.net/nunitv2/+bug/454814) as I feel there should be something to indicate definitely that a test is inconclusive. Will wait for the results of that before adding anything to the XSLT.

Created Issue: Add Support For Inconclusive Tests [5282]

MrKWatkins — Sun, 18 Oct 2009 16:35:37 GMT

Both NUnit and MSTest have a concept of inconclusive tests; make sure they are transformed correctly.

Closed Issue: Descriptions Not Transformed [5281]

MrKWatkins — Sun, 18 Oct 2009 16:05:33 GMT

The XSLT doesn't transform NUnit descriptions from the Description named parameter in the TestAttribute. A fix can be found at http://lindsve.net/2009/01/integrating-nunit-test-result-in-the-tfs-data-warehouse/.
Comments: Resolved with changeset 29503.

Closed Issue: Ignored tests are reported as failures [5111]

MrKWatkins — Sun, 18 Oct 2009 16:05:31 GMT

The NUnitToMSTest.xslt transform causes TFS to report ignored/skipped NUnit tests as failures. This thread (http://nunit4teambuild.codeplex.com/Thread/View.aspx?ThreadId=44099) details a change to the XSLT that fixes this issue. Please could this be added to source control for the next build?
Comments: Resolved with changeset 29503.

Created Issue: Descriptions Not Transformed [5281]

MrKWatkins — Sun, 18 Oct 2009 15:53:24 GMT

The XSLT doesn't transform NUnit descriptions.

Created Issue: Ignored tests are reported as failures [5111]

CtrlAltDel — Fri, 09 Oct 2009 03:03:55 GMT

Closed Issue: Problem With TestCase Attribute In NUnit 2.5

rbanks54 — Fri, 31 Jul 2009 04:43:14 GMT

If using the TestCase attribute in NUnit 2.5 you can get test names containing a ".", e.g.

[TestCase(4.5d)]
public void MyTest(double value)...

Has the name "MyTest(4.5d)". However the test name is wrongly reported as ".5d)".

I've made a fix for this, find it attached. Feel free to tidy it up and release it if you're happy with it!
Comments:

Fixed in version 1.1

Commented Issue: Problem With TestCase Attribute In NUnit 2.5

rbanks54 — Fri, 31 Jul 2009 04:42:54 GMT

Thanks for the fix

Commented Issue: Problem With TestCase Attribute In NUnit 2.5

MrKWatkins — Tue, 23 Jun 2009 11:42:48 GMT

I found a problem with the above; TFS doesn't like test names longer than 256 characters. The attached stylesheet fixes that.

Created Issue: Problem With TestCase Attribute In NUnit 2.5

MrKWatkins — Mon, 22 Jun 2009 14:31:39 GMT