nunit-core team mailing list archive

[Mark Heath <mark.heath@xxxxxxxxx>]

Sounds like a reasonable solution to me. Personally I think that the VS
Test Explorer should have special support for parameterised tests, and
only populate the nodes for individual test cases when the user expands
the node or runs the test (I think the NUnit GUI already does this).
Sometimes we use TestCaseSource to probe various network locations for
data files, and I only want the testcasesource function running if I
actually choose to run that test.

Thanks for your work on NUnit. The VS test adapter has potential to be
very useful for us once VS supports filtering by test category.

-- 
You received this bug notification because you are a member of NUnit
Developers, which is subscribed to NUnit V2.
https://bugs.launchpad.net/bugs/1065462

Title:
  Failure on tests parameterized with long strings

Status in NUnit Test Adapter for Visual Studio:
  Triaged
Status in NUnit V2 Test Framework:
  Triaged

Bug description:
  Having the following test

  		[TestCaseSource("SignBufferSamples")]
  		public void GetSignBuffer(KeyValuePair<int, string> sample) {}

  the adapter fails with the following log:

  ------ Discover test started ------
  Contents of string 'GetSignBuffer([2075, MjAxMjA5MTg0MDAuMDA3MUVVUlBlbnRlZ3l0ZXN0IGFkZHJlc3MxMzQ5MDk5NzgwNGNsYXNzaWZpZWRZVDI2NjEyMzkwNDEwMjAzMjE0M0JZVDI2NjEyMzkwNDEwMjAzMjE0M0JBQVJCREU1VzEwODExMTEyMjIyNTg4ODQ4LUVVUi0zMDMxLTAxLURPTjU4ODg0OC1VQUgtMzAzMS0wMS1ET05FVVJVU0Q1NTUxMDBDb3JudWNvcGlhIEZyZXNoIEdyb2Nlcmllc0FBUkVBTCBCQU5LIEFHLDE1LCBQQVVMSU5FTlNUUkFTU0UsV0lFU0JBREVOLEdFUk1BTllBQVJCREU1VzEwOEFBUkVBTCBCQU5LIEFHLDE1LCBQQVVMSU5FTlNUUkFTU0UsV0lFU0JBREVOLEdFUk1BTll0ZXN0IGRldGFpbHMgb2YgcGF5bWVudEZhbHNlRmFsc2UyNjY0ODQwNDQzMURvbmV0c2tUcnVlRmFsc2VUcnVlRmFsc2VUcnVl])' exceeds max of '449', string has been truncated.

  Exception has been thrown by the target of an invocation.
  ========== Discover test finished: 3203 found (0:00:05.3175317) ==========

  My test assembly is built with NUnit 2.6.0.12051. The issue is
  reproduced no matter which .NET framework I target (3.5, 4.0, 4.5).

To manage notifications about this bug go to:
https://bugs.launchpad.net/nunit-vs-adapter/+bug/1065462/+subscriptions