[
https://issues.apache.org/jira/browse/DERBY-5155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012091#comment-13012091
]
Knut Anders Hatlen commented on DERBY-5155:
-------------------------------------------
I think RunTest and RunSuite already set user.language and user.country to
English/US. See getCommandLine() in the ...functionTests.harness.jvm class. So
hopefully there's nothing more to do for 2.
Most of the JUnit tests are independent of the locale because they only test
query results and the SQLState of errors. The exception is those that check the
contents of messages from the database. My preference would be to handle the
failures individually and only hard-code the locale for the tests that actually
depend on a particular locale in order to succeed. If we force all our tests to
run in English locale only, we lose some variation in the testing and may not
discover bugs that only appear in non-English locales.
> Make testcases pass in non-English locale
> -----------------------------------------
>
> Key: DERBY-5155
> URL: https://issues.apache.org/jira/browse/DERBY-5155
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Reporter: Houx Zhang
> Assignee: Houx Zhang
> Labels: gsoc, gsoc2011
>
> There are a lot of derby testing depending on the English locale, which will
> fail in a non-English locale. A general resolution should be provided.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
