[
https://jira.codehaus.org/browse/SUREFIRE-857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=295983#comment-295983
]
Seiji KOMATSU commented on SUREFIRE-857:
----------------------------------------
I've also been embarrassed with this behavior.
I think this behavior is much problem for non-ascii language region people.
I'm Japanese, so I usually use multibyte characters for test case methods.
Example:
{code}
public void
testExecute_検証失敗_ログインＩＤ不正()
throws Example {
}
{code}
The above case can be written in only ascii characters, as follows:
{code}
public void testExecute_ValidationFailed_LoginIdIsWrong() throws Example {
}
{code}
But, prior to version 2.9 (I've confirmed at version 2.8.1), the result of the
first case is good,
and from version 2.9 the result of that is escaped, and human-unreadable.
I hope the patch the ticket owner attached will be applied as soon as possible.
> Non-ASCII source and name in ReportEntry are escaped unicode on fork.
> ---------------------------------------------------------------------
>
> Key: SUREFIRE-857
> URL: https://jira.codehaus.org/browse/SUREFIRE-857
> Project: Maven Surefire
> Issue Type: Bug
> Components: process forking
> Affects Versions: 2.9, 2.10, 2.11, 2.12
> Reporter: kayakiss
> Attachments: unescape.patch
>
>
> Non-ASCII source and name in ReportEntry are escaped unicode on fork. For
> example 'À'(A with grave) is replaced \u00C0.
> {noformat}
> public class EscapeÀTest {
> @Test
> public void testÀTest() {
> }
> }
> {noformat}
> XML report of this test class is following.
> {noformat}
> <testcase time="0.010" classname="Escape\u00C0Test" name="test\u00C0Test">
> {noformat}
> This problem is that
> *org.apache.maven.plugin.surefire.booterclient.outpu.ForkClient* is not
> unescape for ReportEntry source and name. Because these are escaped with
> *org.apache.maven.surefire.booter.ForingRunListener*, *ForkClient* must be
> unescaped.
> In the attached patch for 2.12 I fixed this problem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
