[ http://issues.apache.org/jira/browse/DERBY-1115?page=all ]
David Van Couvering updated DERBY-1115:
---------------------------------------
Attachment: generateClientMessageTest.sh
What I have done instead is done some ingenuous (IMHO :)) use of grep and sed
to *generate* a unit test which basically extracts all (or as many as I could
find) uses of message translation in the network client and puts it in a single
test file. I have yet to tackle this for the engine.
So, I have this all working (see attached) and I actually already found one bug
that way. Since it depends on UNIX utilities, it can't be part of the standard
unit tests, but I'd like to check it in and recommend we use it for nightly
regression and release tests.
The question is, where to put it? Where I have it right now is under
java/build/i18nTestGen. It seems a bit odd since it's not actually java code.
Is there a better place to put this? Should it go under tools?
> 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
> Reporter: David Van Couvering
> Priority: Minor
> Attachments: README, 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
