Details
-
Story
-
Status: Closed
-
Minor
-
Resolution: Completed
-
None
-
LIMA | #38 | DEV | Jul06-Aug03, LIMA | #39 | DEV | Aug4-Sept07, LIMA | #40 | DEV | Sep07-Oct05, LIMA | #41 | DEV | Oct05-Nov02, LIMA | #42 | DEV | Nov02-Nov30
Description
Value Statement
As a translator,
I want to have a dedicated UI to translate the inline content of content page experiences
so that I can perform my task while not messing with other languages or the original content.
Use Cases
- The translator must be able to write content in the specified language due to translation permission in the role for a language
- The translator must be able to check the content in the default language and choose any other language as "translate from" language
- The translator must not be able to edit the default language content unless permissions allow.
Designs
Acceptance Criteria
Given a site
When a translator accesses the pages administration section
Then they can find an action on content pages named "translate"
Given a site
When a translator tries to translate a content page
Then they will navigate to the side-by-side UI listing the inline text of all the fragments
And they will be able to select the experience to translate
Given a user with a translator role
When they click on the "translate" action
Then they will be able to modify only the languages they have permissions for
Given a user with a translator role with no workflow for translations enabled
When they finish translating all the experiences
Then the translation for all experiences are merged
Given a user with a translator role with workflow for translations enabled
When they finish translating all the experiences
Then the translations are sent for approval
Given a user with a translator role with workflow for translations enabled
When the translation is approved
Then the translation is merged into the corresponding experience of the content page
Test Scenarios
ID | Test Priority | Test Scenarios | Covered by Backend (Unit/Integration)? | Test to add |
---|---|---|---|---|
5 | The translate action appears for a content page in the site admin | NO | TranslationsContentPages#CanPublishTranslatedHeadingWithExperience | |
5 | The inline text for fragment of a new experience appear in the side-by-side translation for a content page | NO | TranslationsContentPages#CanPublishTranslatedHeadingWithExperience | |
5 | A translator can only modify the languages he has permissions for | NO | TranslationsContentPages#CanOnlyTranslateToSpanishWithExperience | |
5 | A translator cannot see the other languages item he does not have permissions for | NO | TranslationsContentPages#CanOnlyTranslateToSpanishWithExperience | |
5 | A saved translation without workflow is visible in the new experience of the content page | NO | TranslationsContentPages#CanPublishTranslatedHeadingWithExperience | |
5 | A saved translation with workflow enabled becomes visible in the new experience of the content page after approving it | NO | TranslationsContentPageWorkflow#CanTranslateHeadingWithExperienceAfterReviewing | |
5 | A reviewer will receive a notification once a translated content page is sent for review | NO | TranslationsContentPageWorkflow#CanTranslateHeadingWithExperienceAfterReviewing | |
5 | A reviewer can approve the content page translation sent for review | NO | TranslationsContentPageWorkflow#CanTranslateHeadingWithExperienceAfterReviewing | |
5 | A reviewer can reject the content page translation sent for review | NO | TranslationsContentPageWorkflow#CanResubmitRejectedTranslationWithExperience |