Skip to content
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

Running suites does not show the tests summaries #876

Closed
briceparmentier opened this issue Feb 19, 2016 · 2 comments
Closed

Running suites does not show the tests summaries #876

briceparmentier opened this issue Feb 19, 2016 · 2 comments
Milestone

Comments

@briceparmentier
Copy link

@briceparmentier briceparmentier commented Feb 19, 2016

Hi,

I just upgraded my FitNesse instance to latest one (v20151230), and got a strange behaviour.
Running a test suite, I have a title named "Test Summaries", under this title, the name of my runner is shown, here "slim:FitSharp\Runner.exe".

Inside HTML code of this page, under the tag containing the runner name, there is an "ul" tag that should receive each test recap. But its name (its HTML id) contains the same "" as in "slim:FitSharp\Runner.exe", that is to say the id of the tag is "test-system-slim:FitSharp\Runner.exe", so that the Javascript code can not target the tag to add each test summary.

The Javascript console logs a "document.getElementById(...) is null".

For more details see the screenshot attached.
I tried to use the latest release from your Jenkins CI server, but the issue is still present. It was not present on previous official release, v20150814.

Thanks !

untitled

@amolenaar
Copy link
Collaborator

@amolenaar amolenaar commented Mar 4, 2016

Something has changed there. The escaping of html for javascript has been extended in 696dddb. Apparently I missed one case.

@amolenaar amolenaar added this to the Next release milestone Mar 4, 2016
@briceparmentier
Copy link
Author

@briceparmentier briceparmentier commented Mar 4, 2016

Thanks !

@amolenaar amolenaar closed this in 574a0d9 Mar 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants