Bug 59991 - TestCase with unicode strings does not work
Summary: TestCase with unicode strings does not work
Status: NEW
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: NUnit (show other bugs)
Version: Trunk
Hardware: PC Mac OS
: Normal normal
Target Milestone: Future Cycle (TBD)
Assignee: Mike Krüger
Depends on:
Reported: 2017-10-05 16:28 UTC by Marius Ungureanu
Modified: 2017-10-06 06:41 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report for Bug 59991 on Developer Community or GitHub if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description Marius Ungureanu 2017-10-05 16:28:56 UTC
Given the following test case:

[TestCase ("バージョン", 1, 3, 4, 1)]
public void TextIndexerWorks (string arg, int index, int indexToByteIndex, int byteIndex, int byteIndexToIndex)

when running the test, you get the following message:

No tests found that match filter: [SimpleNameFilter]: MonoDevelop.Components.PangoUtilTests.TextIndexerWorks("\x30D0\x30FC\x30B8\x30E7\x30F3",1,3,3,1)

The problem is that when requesting test info from the runner, the unicode string comes in with escaped `\` in `\x`.

NUnit 3 works fine. I assume this is a bug in NUnit 2. We should workaround this issue, but not sure what to do when the test case actually should take that value.