Ah, see it now. Nothing shows here because its a whitespace diff. On
actual char diffs its highlighted. Suggest it should also be expressed
with column in string or something in the report.

On Jan 22, 4:28 pm, Mads Nissen <[email protected]> wrote:
> Eh.. can't see it anywhere. Here is a screenshot (spot the difference
> in the 
> strings):http://groups.google.com/group/MbUnitUser/web/string_differs_at.GIF?h...
>
> On Jan 21, 6:31 pm, Phil Japikse <[email protected]> wrote:
>
> > Doh! I keep forgetting about the report option. Thansk for the reminder!
>
> > Philip Japikse, MCSD.Net, MCDBA, CSM
> > Pinnacle Solutions, Inc
> > [email protected]
> > twitter/skimedic
> > (513) 312-5664
> > (sent from mobile device)
>
> > -----Original Message-----
> > From: Jeff Brown <[email protected]>
> > Sent: Wednesday, January 21, 2009 12:26
> > To: [email protected]
> > Subject: MbUnit Re: String differs at on Assert.AreEqual fail
>
> > You will see it if you open up a Gallio Test Report from within the R# Unit 
> > Test Session.  Unfortunately we cannot show the highlights in the main R# 
> > result window since that tool expects plain text output only.
>
> > Jeff.
>
> > On Wed, Jan 21, 2009 at 8:43 AM, Philip Japikse <[email protected]> 
> > wrote:
>
> >  You will not get it in the R# test runner, but it shows in the Gallio test
> >  runner.  So, what I do when I have a failed  test where I need to know the
> >  location in a string is I run the test in Gallio.  Works like a champ!
>
> >  Phil
> >  Philip Japikse, MCSD.Net, MCDBA, CSM
> >  Principal Consultant
> >  Pinnacle Solutions, Inc
> > [email protected]
> >  twitter/skimedic
> >  (513) 312-5664
>
> >  -----Original Message-----
> >  From: [email protected] [mailto:[email protected]] On
> >  Behalf Of Mads Nissen
> >  Sent: Wednesday, January 21, 2009 11:33 AM
> >  To: MbUnit.User
> >  Subject: MbUnit String differs at on Assert.AreEqual fail
>
> >  Might be me missing something obvious here, but from NUnit I'm used to
> >  getting input on where in a string there is a difference when doing an
> >  Assert.AreEqual(expectedString, actualString). Doesn't seem like I'm
> >  getting that information in my resharper testrunner (just went through
> >  an xmlblob char by char to find the whitespace:))
>
> >  mads
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"MbUnit.User" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/MbUnitUser?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to