Skip to content

double quote or "&" in test case name will generate invalid xml file #122

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wangzq opened this issue Mar 17, 2014 · 2 comments
Closed

double quote or "&" in test case name will generate invalid xml file #122

wangzq opened this issue Mar 17, 2014 · 2 comments

Comments

@wangzq
Copy link

wangzq commented Mar 17, 2014

I think we should escape the value in templating.ps1 before replacing the placeholders in xml template.

@nohwnd
Copy link
Member

nohwnd commented Jun 8, 2014

Note to self: When fixing this there is & in the Mock tests file commented out because of this issue.

nohwnd added a commit that referenced this issue Jun 8, 2014
the & made the nUnit.xml impossible to parse. quick-fixing this. There
is #122 issue for this.
nohwnd added a commit that referenced this issue Jun 29, 2014
The output XML used templates to output the nUnit xml report, that did not support using special
characters in Describe and It descriptions. I replaced it with XmlTextWriter that does all the
escaping automatically. Also the nUnit report was not compliant with the scheme. It now has single
test-suite root name by the Path (is there better option?). Scheme is not verified as well as the
special characters.

Fixing #122
@dlwyatt
Copy link
Member

dlwyatt commented Aug 2, 2014

This is resolved in the v3.0-beta2 release, per commit 12df6f5 from @nohwnd.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants