Details

    • Type: Technical Testing
    • Status: Closed
    • Priority: Minor
    • Resolution: Completed
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None
    • Story Points:
      13
    • Sprint:
      LIMA | #40 | DEV | Sep07-Oct05, LIMA | #41 | DEV | Oct05-Nov02, LIMA | #42 | DEV | Nov02-Nov30

      Description

      • Create the test scenarios to validate the parent story, according to the Acceptance Criteria.
      • Those test scenarios will be writing in the parent story.

      The imported translation for a content page experience can be merged to the correct experience of a content page

      TranslationsContentPageExportImport#CanImportExportedTranslationForCorrespondingExperience

      1. Add a new content page
      2. Add a new fragment (Heading) to the page and modify the fragment text to "Title"
      3. Add a new experience for the page and modify the fragment text to "Title for new experience"
      4. Publish the page
      5. Go to export the content page for translation
        1. Select the XILLF 2.0 (default)
        2. Select Spanish (Spain) 
        3. Uncheck the default experience and ensure the new experience is checked
      6. Click the "Export" button
      7. Translate the heading fragment in the file
      8. Import the translated .xlf file
      9. Go to the draft content page> Publish
      10. Go to the page
      11. Change the locale to Spain
      12. Assert the fragment not translated
      13. Change the experience to the new one
      14. Assert the fragment is translated

      The translation for a content page experience can not be imported after deleting the experience

      TranslationsContentPageExportImport#CannotImportTranslationForDeletedExperience

      1. Add a new content page
      2. Add a new fragment (Heading) to the page
      3. Add a new experience for the page 
      4. Publish the page
      5. Go to export the content page for translation
        1. Select an available language
        2. Uncheck the default experience and ensure the new experience is checked
      6. Click the "Export" button
      7. Unzip the translation file
      8. Go to the content page delete the experience ->Publish
      9. Import the translated .xlf file
      10. Assert the error will be displayed: The translation file does not correspond to this page.

      The imported translation for a content page experience can be approved through the workflow

      TranslationsContentPageWorkflow#CanApproveImportedTranslationForExperience

      1. Add a new content page
      2. Add a new fragment (Heading) to the page and modify the fragment text to "Title"
      3. Add a new experience for the page and modify the fragment text to "Title for new experience"
      4. Publish the page
      5. Go to workflow> Translation> Change to "Single Approve"
      6. Go to export the content page for translation
        1. Select the XILLF 1.2
        2. Select Japanese 
        3. Uncheck the default experience and ensure the new experience is checked
      7. Click the "Export" button
      8. Translate the heading fragment in the file
      9. Import the translated .xlf file
      10. Notifications -> Click on new notification and Assign to Me -> Approve it
      11. Go to the draft content page> Publish
      12. Go to the page
      13. Change the locale to Japanese
      14. Assert the fragment not translated
      15. Change the experience to the new one
      16. Assert the fragment is translated

      The imported translation for a content page experience can be merged to the correct experience once it is approved by a reviewer

      Cover in : TranslationsContentPageWorkflow#CanApproveImportedTranslationForExperience

      The imported translation for a content page experience can not be merged after rejecting through the workflow

      TranslationsContentPageWorkflow#RejectedTranslationWillNotBeAppliedToExperience

      1. Add a new content page
      2. Add a new fragment (Heading) to the page and modify the fragment text to "Title"
      3. Add a new experience for the page and modify the fragment text to "Title for new experience"
      4. Publish the page
      5. Go to workflow> Translation> Change to "Single Approve"
      6. Go to export the content page for translation
        1. Select an available language
        2. Uncheck the default experience and ensure the new experience is checked
      7. Click the "Export" button
      8. Translate the heading fragment in the file
      9. Import the translated .xlf file
      10. Notifications -> Click on new notification and Assign to Me -> Reject it
      11. Go the page
      12. Change the experience to the new one and switch the language to the translated on local
      13. Assert the fragment not translated

       

        Attachments

          Activity

            People

            Assignee:
            jeremy.chen Jeremy Chen
            Reporter:
            adolfo.perez Adolfo Pérez
            Recent user:
            Austin Chiang
            Participants of an Issue:
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Packages

                Version Package