Hi, NCrunch is great, but... I have troubles with error messages in russian system.
It looks like Screenshot
SetUp : System.ArgumentNullException : Значение не может быть неопределенным.
Имя параметра: loggerFactory
в Sunflower.Ant.Model.Loader.ModelLoader..ctor(ModelLoaderSettings settings, ILoggerFactory loggerFactory) â C:\src\sun-flower\Ant\Src\Sunflower.Ant.Common\Model\Loader\ModelLoader.cs:ñòðîêà 32#0
в XmlPersistence.DataDescriptorCacheTests.TestInitialize() â C:\src\sun-flower\Ant\Src\Tests\UnitTests\XmlPersistence\DataDescriptorCacheTests.cs:ñòðîêà 27#1
russian text in stack trace is in wrong encoding
AND "SetUp : System.ArgumentNullException" string has another encoding (differ from callstack I guess, and seems to be utf-8) which displays wrong too.
My system: Windows7 Professional Russian 6.1.7601 Service Pack 1
Microsoft Visual Studio 2010 10.0.30319.1 Russian
Microsoft .NET Framework 4.0.30319 + Russian Lang pack
Test environment is NUnit 2.6.2.12296
Regards
Remco NCrunch Developer
#3083
01 Nov 2012 21:36 UTC
Hi,
Thanks for reporting this problem. The issue itself appears to be some kind of rendering problem inside the Richedit control used by NCrunch to display the test output. Although the data being stored in the control is correct, certain characters can cause it to show in a corrupted form.
As the problem is deeply lodged inside the control itself, I can as-yet find no feasible way to solve it without replacing the control entirely (which is a significant piece of work).
I'll continue to investigate, although I think a fix for this is quite a way out. You may be able to work around the problem using the following methods:
- Analyse stack traces using NCrunch's inline exception data
- Examine error details from failed tests using the processing queue (clumsy, but the text output here should not be impacted by this issue)
- Copy/paste the corrupted output from the tests window into another text editor (i.e. notepad), where the rendering issue won't exist and the text should be legible
Sorry that I can't provide a better fix at the moment.
Cheers,
Remco
Thanks for reporting this problem. The issue itself appears to be some kind of rendering problem inside the Richedit control used by NCrunch to display the test output. Although the data being stored in the control is correct, certain characters can cause it to show in a corrupted form.
As the problem is deeply lodged inside the control itself, I can as-yet find no feasible way to solve it without replacing the control entirely (which is a significant piece of work).
I'll continue to investigate, although I think a fix for this is quite a way out. You may be able to work around the problem using the following methods:
- Analyse stack traces using NCrunch's inline exception data
- Examine error details from failed tests using the processing queue (clumsy, but the text output here should not be impacted by this issue)
- Copy/paste the corrupted output from the tests window into another text editor (i.e. notepad), where the rendering issue won't exist and the text should be legible
Sorry that I can't provide a better fix at the moment.
Cheers,
Remco
Thanx for reply.
Hope you will replace richedit in version 2
Hope you will replace richedit in version 2
Strange behavior in version 1.43:
The problem of this topic remains, BUT in some cases exception message looks as it should be: http://goo.gl/4SWHu
The problem of this topic remains, BUT in some cases exception message looks as it should be: http://goo.gl/4SWHu
Remco NCrunch Developer
#3496
06 Jan 2013 21:21 UTC
I believe the problem is related to the characters being displayed. Certain localised characters (such as those used in a stack trace) cause the control to start behaving erratically. Interestingly, I haven't been able to reproduce the problem on Windows 8 - so I'm wondering if it might be platform specific. Which operating system are you running on?
Remco wrote:Which operating system are you running on?
My system: Windows7 Professional Russian 6.1.7601 Service Pack 1
Remco NCrunch Developer
#3552
16 Jan 2013 21:43 UTC
Thanks. I'm wondering if this issue may be specific to Windows 7. I'll take another look to see if I can reproduce it there.
Post a reply
Log in to reply.