You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by bu...@apache.org on 2010/01/09 18:23:21 UTC
DO NOT REPLY [Bug 48514] New: linebreaks in method names in html
generated by the junitreport task
https://issues.apache.org/bugzilla/show_bug.cgi?id=48514
Summary: linebreaks in method names in html generated by the
junitreport task
Product: Ant
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: Optional Tasks
AssignedTo: notifications@ant.apache.org
ReportedBy: hastebrot@gmail.com
Usually method names of JUnit tests look like thisIsATest or this_is_a_test.
I use spock for my tests (http://code.google.com/p/spock/) and you can use
strings for method names (e.g. "this is a test").
Generating html documentation with the junitreport task works fine with spock
and junit. But with the space characters in the method names are forced with
line breaks.
this
is
a
test
This should be this is a test.
So junitreport should replace " " (space chars) with " " for method names
when generating html.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
DO NOT REPLY [Bug 48514] linebreaks in method names in html
generated by the junitreport task
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=48514
Stefan Bodewig <bo...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|unspecified |1.7.1
Severity|normal |enhancement
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
DO NOT REPLY [Bug 48514] linebreaks in method names in html
generated by the junitreport task
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=48514
Jesse Glick <jg...@netbeans.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
CC| |jglick@netbeans.org
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
DO NOT REPLY [Bug 48514] linebreaks in method names in html
generated by the junitreport task
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=48514
--- Comment #2 from Stefan Bodewig <bo...@apache.org> 2010-04-06 04:39:42 UTC ---
could you provide us with a sample test XML file?
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
DO NOT REPLY [Bug 48514] linebreaks in method names in html
generated by the junitreport task
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=48514
--- Comment #1 from hastebrot@gmail.com 2010-01-09 09:29:37 UTC ---
Created an attachment (id=24823)
--> (https://issues.apache.org/bugzilla/attachment.cgi?id=24823)
screenshot of generated html page
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
[Bug 48514] linebreaks in method names in html generated by the
junitreport task
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=48514
J.M. (Martijn) Kruithof <jk...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |RESOLVED
Resolution|--- |WONTFIX
--- Comment #3 from J.M. (Martijn) Kruithof <jk...@apache.org> ---
>From the html it can be seen that the spaces are not translated to hard line
brakes, standard wrapping in the colum takes place. When reading the spock
pages it can be seen that natural language for the test cases is encouraged.
Not wrapping would probably lead to no space left for the other columns. So
simply replacing all spaces by seems unwise.
Furthermore the requested information has not been provided the last 2 years,
therefore closing as wontfix. If you have an idea what would be required and
have a corresponding sample XML file, please provide that information and
reopen as NEW.
--
You are receiving this mail because:
You are the assignee for the bug.