What steps will reproduce the problem?
1. Write a failing specification where the error message would contain
special XML characters. E.G. expect.that(true).isEqualTo(false);
2. Run the instinct task
3. Run the instinct-report task
4. View the report.
What is the expected output? What do you see instead?
The report should contain:
Expected: <true>
got: <false>
Instead it renders this as
Expected:
got:
because the XML characters are not escaped.
Original issue reported on code.google.com by jem.maw...@gmail.com on 19 Nov 2008 at 11:05
Original issue reported on code.google.com by
jem.maw...@gmail.com
on 19 Nov 2008 at 11:05