Issue 15 in yatspec: HTML output fails to markup < and >

3 views
Skip to first unread message

yat...@googlecode.com

unread,
Jun 14, 2012, 12:17:16 PM6/14/12
to yat...@googlegroups.com
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 15 by toby.wes...@gmail.com: HTML output fails to markup < and >
http://code.google.com/p/yatspec/issues/detail?id=15

Hey folks,

How do you expect things to work when I make assertions against XML
content... for example,

given(whatever());
when(iAddSomeXmlToTheCapturedInputAndOutputs());
then(saidCapturedInputAndOutputs(),
allOf(containsString("<name>bob</name>"), containsString("<address>1 poo
street"</address>")));


It works fine for the assertions but fails to mark up the chevrons in the
HTML output. Obviously, the assertions fail if I say
`containsString("&lt;name...` but the HTML will output as expected.

Not sure how to mark up < and > as &lt; and &gt; without affecting the
expectations.

Not really and issue just thought I'd ask for a workaround / tips on my
approach.

Cheers

yat...@googlecode.com

unread,
Jun 14, 2012, 12:18:16 PM6/14/12
to yat...@googlegroups.com

Comment #1 on issue 15 by toby.wes...@gmail.com: HTML output fails to
markup < and >
http://code.google.com/p/yatspec/issues/detail?id=15

er, I can't edit this to make it something other than a defect. sorry.

yat...@googlecode.com

unread,
Jun 14, 2012, 1:30:26 PM6/14/12
to yat...@googlegroups.com
Updates:
Status: Fixed

Comment #2 on issue 15 by alex.luker: HTML output fails to markup < and >
http://code.google.com/p/yatspec/issues/detail?id=15

Looks like a bug to me. Tend to write test a lot higher level than anything
that would involve xml in the Java source, but seems sensible to be
escaping it anyway. Fixed in Yatspec-200.

yat...@googlecode.com

unread,
Jun 14, 2012, 1:51:36 PM6/14/12
to yat...@googlegroups.com

Comment #3 on issue 15 by toby.wes...@gmail.com: HTML output fails to
markup < and >
http://code.google.com/p/yatspec/issues/detail?id=15

Your face is a bug.

Reply all
Reply to author
Forward
0 new messages