Hi, My first guess: When you have view specs or controller specs with render_views/integrate_views you could make I18n raise an error when its missing a translation. Then run every spec in every locale and you'll see where there are missing. This might be a lot of work and you won't get translations that have a default (like human_attribute_name).
So, my second guess: You'll probably have one base locale, the one you work in. If you consider that one to be complete, you can compare the keys from each translation. You'll have to flatten them first though. This isn't easy too. So, I hope you have some ideas from this. Good luck, and share the answer if you find it :) cheers, iain On Tue, Oct 12, 2010 at 11:35, Michael Bensoussan <[email protected]> wrote: > Hi, > We have a multilingual application using I18n, > How would you test your application have no translations missings ? > Would you test it view by view ? or have you a better solution ? > > Thanks, > > -- > You received this message because you are subscribed to the Google Groups > "rails-i18n" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/rails-i18n?hl=en. > > -- You received this message because you are subscribed to the Google Groups "rails-i18n" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rails-i18n?hl=en.
