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 "Mike Matrigali (JIRA)" <de...@db.apache.org> on 2006/04/12 01:40:23 UTC

[jira] Updated: (DERBY-1115) Write a test that ensures that code that translates a message id into a message does so correctly

     [ http://issues.apache.org/jira/browse/DERBY-1115?page=all ]

Mike Matrigali updated DERBY-1115:
----------------------------------

    Component: Test

> Write a test that ensures that code that translates a message id into a message does so correctly
> -------------------------------------------------------------------------------------------------
>
>          Key: DERBY-1115
>          URL: http://issues.apache.org/jira/browse/DERBY-1115
>      Project: Derby
>         Type: Test

>   Components: Test
>     Reporter: David Van Couvering
>     Priority: Minor
>  Attachments: README, TestClientMessages.java, genClient1.sed, genClient2.sed, generateClientMessageTest.sh
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira