Synesso / instinct

Automatically exported from code.google.com/p/instinct
0 stars 0 forks source link

Failure detail in spec report is not XML encoded #49

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
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

GoogleCodeExporter commented 9 years ago

Original comment by jem.maw...@gmail.com on 3 Dec 2008 at 9:26

GoogleCodeExporter commented 9 years ago

Original comment by jem.maw...@gmail.com on 3 Dec 2008 at 9:55