- Issue created by @joachim
ContentTranslationSyncImageTest uses a form submission to set up field translation.
This is expensive, and not what the test is covering.
It should make API calls instead.
There is also this comment about checking the two admin pages agree:
// Check that the content translation settings page reflects the changes
// performed in the field edit page.
This is also not relevant to this test. It probably doesn't need moving elsewhere -- there are already tests for the admin/config/regional/content-language form correctly showing and saving config values, and the for the field edit form correctly showing and saving config values.
Change to an API call.
Active
11.0 🔥