[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
AW: [geclipse-dev] Another useful feature to the build / test system
|
You must test all methods where the Message.getMessage() is called. I mean, it is not possible to only go through the properties file using Message.getMessage() because in this way you can not test if you misspell the parameter.
Jie
-----Ursprüngliche Nachricht-----
Von: geclipse-dev-bounces@xxxxxxxxxxx [mailto:geclipse-dev-bounces@xxxxxxxxxxx] Im Auftrag von Mateusz Pabis
Gesendet: Donnerstag, 19. Juni 2008 12:56
An: Developer mailing list
Betreff: [geclipse-dev] Another useful feature to the build / test system
Hi,
Sometimes it happens that there is missing externalized string. It can be due to misspell in the getMessage() parameter, or due to refactoring where one string is left behind.
In such cases there is no warning nor error. Only during runtime there is strange message instead of the one you expected.
Is there a way to create such test, which will check for the Messages.properties and Message.getMessage() consistency and report back in case of problems?
I tried to create it by myself, but I didn't spent on this reasonable amount of time.
--
Mateusz
_______________________________________________
geclipse-dev mailing list
geclipse-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/geclipse-dev
