This is a general comment on all our tests that are backed by some inserted data: Writing these tests, and to some extent reading them, requires some special knowledge of the test data that is not necessarily obvious or easy to find. For example, even looking at the dbunit files is not straightforward since states are inserted as just integers. This means we effectively have magic numbers in our code, which we should consider moving to constants.
Since we may use the same test data for several different tests, it may be useful to make an accompanying class for each set of test data with static fields describing relevant information such as which TU ids are in untranslated state. Test classes could then use a static import to bring appropriate constants into scope for the test data they use.