Closed GoogleCodeExporter closed 8 years ago
Hmm, that's an interesting one! Could you please attach the xml report that
you're
generating from?
Original comment by grahamr...@gmail.com
on 1 Jun 2009 at 9:07
I've seen this before and have an open issue to pre-filter test output before
writing
it into the report. XML does not allow certain characters to be represented.
To work around this issue, try to find a test that might be writing binary
output
directly into the test log. If you open up the XML file then it should be easy
enough to spot the stray U+000E character in there and you'll see which test it
belongs to.
Likely culprit: A test that does something like
TestLog.WriteLine(Encoding.UTF8.GetString(arrayOfBytes));
Of course the real bug remains in that it makes no sense for us to store
unprintable
or invalid-for-XML characters in the report so we should strip them out early.
Original comment by jeff.br...@gmail.com
on 1 Jun 2009 at 10:09
I'll try to deal with this in the v3.0.7 timeframe.
Original comment by jeff.br...@gmail.com
on 1 Jun 2009 at 10:10
I think the problem that my test result contains words in Arabic language.
Since that my application is Bilingual with Arabic/English support.
I've generated and attached an XML report.
Sure, on my machine Arabic words looks fine in XML file, but I don't know how
it will
be for you.
Original comment by waheedsayed
on 2 Jun 2009 at 8:33
Attachments:
I downloaded the recent binaries you pointed to (build 787).
I tried the same and got the same result.
Original comment by waheedsayed
on 2 Jun 2009 at 8:36
The Arabic words came through just fine on my end so it's likely that Gallio is
using
the correct Unicode encodings end-to-end. I went through a few months ago to
make
sure of this (but I might still have missed something!).
However I did find some very strange characters spanning multiple code pages in
the
output of HashingFixture.CanHashString. It looks like the test is writing out
raw
bytes to the Console.
Original comment by jeff.br...@gmail.com
on 2 Jun 2009 at 5:37
You are exactly right. This is the test & method that prevents report
generation.
The point those strange characters are print of the resulting hashed string to
console. By commenting, the following line I can generate test report:
Console.WriteLine("Test Value: [{0}] Hashed Value: [{1}]", input, hashed);
Is there another way to print hashed string to console & generate the report?
Original comment by waheedsayed
on 3 Jun 2009 at 10:52
You might consider printing the hashed string as hex. It's not really going to
be
readable otherwise as some of the characters in the hashed string are not
printable.
Original comment by jeff.br...@gmail.com
on 3 Jun 2009 at 4:50
Original comment by jeff.br...@gmail.com
on 29 Jun 2009 at 8:33
Original comment by jeff.br...@gmail.com
on 18 Jul 2009 at 5:12
Original issue reported on code.google.com by
waheedsayed
on 1 Jun 2009 at 4:50Attachments: