Issue 49 in instinct: Failure detail in spec report is not XML encoded

[codesite...@google.com]

Issue 49: Failure detail in spec report is not XML encoded
http://code.google.com/p/instinct/issues/detail?id=49

New issue report by jem.mawson:
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.

Issue attributes:
Status: Accepted
Owner: jem.mawson
Labels: Type-Defect Priority-Medium

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings