[
https://issues.apache.org/jira/browse/DERBY-3834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12725277#action_12725277
]
Tiago R. Espinha commented on DERBY-3834:
-----------------------------------------
Hello Kathey,
Well, considering I'm manipulating the server that the test spawns
automatically, it should never stay running. I'm not spawning an independent
server just to accommodate the locale testing; instead, I just stop the server
that the test automatically starts, change the locale and start the server
again.
The odd case would be if this fixture fails, but a possible solution is to
encapsulate this method in a try..catch statement. Since all the fixtures are
actually invoked manually because the order in which they are ran matters, I
can just catch the exception that this method may throw and set the locale back
to normal.
I'm just laying this on the table because it seems to me a bit of overkill to
create a whole new test with just one fixture that tests the locale.
> Convert derbynet/runtimeinfo to JUnit
> -------------------------------------
>
> Key: DERBY-3834
> URL: https://issues.apache.org/jira/browse/DERBY-3834
> Project: Derby
> Issue Type: Test
> Components: Test
> Affects Versions: 10.5.1.1
> Reporter: Erlend Birkenes
> Assignee: Tiago R. Espinha
> Priority: Minor
> Attachments: DERBY-3834.patch, DERBY-3834.patch, DERBY-3834.patch,
> DERBY-3834.stat, Derby-3834_1.diff
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
