Page MenuHomePhabricator

Define core workflows for ContentTranslation testing
Closed, ResolvedPublic


As part f the process to expose Content Translation to more users (T102107), we wanted to define a set of core workflows to test. The idea is to identify a set of example scenarios that cover the basic functions of the tool to make sure that the main translation functionality has not been affected by the many changes that are planned before the release.

The workflows captured cover different entry points, translation patterns and publishing destinations:

Publishing a draft of a missing page through grey links

(This scenario requires to pick languages for which Machine translation is available)

  1. Find a Wikipedia page with grey language links (indicating the page is not available in a language the user speaks).
  2. Start a translation for that page from the grey interlanguage link.
  3. Add 3 paragraphs: a check the content added is translated and correct the content.
  4. Add a new link for a word in one paragraph. Ignoring the link suggestions, make it link to a different page.
  5. Open the links for the translated and original paragraphs to check they point to the correct articles.
  6. Modify the translation title for the translation to be published under the user namespace.
  7. Publish the translation and access to the result. Check that instructions are given on how to move the published article to the main namespace.

Publishing a suggested article in two steps

  1. Access the translation dashboard by using the contributions popup.
  2. Access the list of suggested articles.
  3. Refresh the list to get different suggestions and keep some for later.
  4. Start a new translation from the list of suggestions.
  5. Translate the initial paragraph and one image.
  6. Publish the result in the main namespace.
  7. Go back to translate another paragraph (from the contributions page)
  8. Continue the published translation.
  9. Translate a new paragraph and publishing. A warning will be shown about the article already existing.
  10. Publish to the main namespace and check the article content is updated.

Publishing a draft with the corresponding warnings

  1. Access the translation dashboard through the contributions page.
  2. Start a new translation and find an article that already exists as a stub. Check that there is a warning about the article already existing.
  3. Add several paragraphs to the translation. Check that a warning about having too much automatic translation is shown.
  4. Access a paragraph and try alternative translations: other MT engines, source text and empty paragraph.
  5. Leave the translation by navigating away.
  6. Access the translation dashboard and resume the translation.
  7. Publish the content. An option indicating the article exists should appear. Publish the translation as a draft.