You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kathey Marsden (JIRA)" <ji...@apache.org> on 2009/05/07 20:48:45 UTC
[jira] Closed: (DERBY-1115) Write a test that ensures that code
that translates a message id into a message does so correctly
[ https://issues.apache.org/jira/browse/DERBY-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden closed DERBY-1115.
---------------------------------
Resolution: Fixed
Closing this as fixed as there was a test written. That said there are still some problems with the test. This is filed as DERBY-1567, but there is no need to keep both issues open.
> Write a test that ensures that code that translates a message id into a message does so correctly
> -------------------------------------------------------------------------------------------------
>
> Key: DERBY-1115
> URL: https://issues.apache.org/jira/browse/DERBY-1115
> Project: Derby
> Issue Type: Test
> Components: Test
> Reporter: David Van Couvering
> Priority: Minor
> Attachments: genClient1.sed, genClient2.sed, generateClientMessageTest.sh, README, TestClientMessages.java
>
>
> After finding, in my and others' code, a number of situations where we used a message id with no matching message, or used the incorrect number of parameters for an internationalized message, I became determined to write a test that tries to track down these bugs, a kind of "i18n lint".
> It's very hard, almost impossible, to test these invocations of message formatting through a normal unit test, because basically you have to write a full suite of negative tests.
> This bug is a placeholder for some work I am doing to accomplish this task using code parsing rather than trying to execute negative tests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.