Details

    • Type: Technical Testing
    • Status: Closed
    • Priority: Minor
    • Resolution: Completed
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None
    • Story Points:
      8
    • Sprint:
      LIMA | #36 | DEV | May18-Jun08, LIMA | #34 | DEV | Apr06-Apr27, LIMA | #35 | DEV | Apr27-May18, LIMA | #37 | DEV | Jun08-Jul06

      Description

      Scenario 4.8 - A field translation button will be displayed on the right side of the fields after enabling the Google Cloud translation

      See Scenarios 4.11

      Scenario 4.9 - The field translation button will be hidden after disabling the Google Cloud translation

      Update the existing test - AutoTranslation#CanViewTranslationAfterDisablingGoogleConfiguration

      1. ...
      2. Assert the field translation can not be viewed
      3. ...

      Scenario 4.10 - The field translation button will be disabled when translating field without content

      Add New Test: AutoTranslation#TranslateButtonsAreDisabledWhenFieldsAreNull

      Test Steps:

      1. Go to system setting> Translation>Enable Google cloud translation
      2. Add a web content article without content and description (By JSON)
      3. Go to translate the web content through side by side
      4. Assert the title field translation button is enabled
      5. Assert the content field translation button is disabled
      6. Assert the description field translation button is disabled

      Scenario 4.11 - A basic web content title can be translated separately

      Add New Test : AutoTranslation#CanTranslateTitleFieldIndependently

      Test Steps:

      1. Go to system setting> Translation>Enable Google cloud translation
      2. Add a web content article (By JSON)
      3. Go to translate the web content through side by side
      4. Change the target locale to Japanese
      5. Click the field translations for the Title
      6. Assert the Content and Description values haven't changed 
      7. Publish 
      8. Go to the translation process to view the translation
      9. Assert the title can be translated to Japanese correctly
      10. Assert  Content and Description are still display in English

      Scenario 4.12 - A basic web content content can be translated separately

      Add New Test : AutoTranslation#CanTranslateContentFieldIndependently

      Test Steps:

      1. Go to system setting> Translation>Enable Google cloud translation
      2. Add a web content article (By JSON)
      3. Go to translate the web content through side by side
      4. Change the target locale to Japanese
      5. Click the field translations for the Content
      6. Assert the Title and Description values haven't changed 
      7. Publish 
      8. Go to the translation process to view the translation
      9. Assert the title can be translated to Japanese correctly
      10. Assert  Title and Description are still displayed in English

      Scenario 4.13 - A basic web content description can be translated separately

      Add New Test : AutoTranslation#CanTranslateDescriptionFieldIndependently

      Test Steps:

      1. Go to system setting> Translation>Enable Google cloud translation
      2. Add a web content article (By JSON)
      3. Go to translate the web content through side by side
      4. Change the target locale to Japanese
      5. Click the field translations for the Description
      6. Assert the Title and Content values haven't changed 
      7. Publish 
      8. Go to the translation process to view the translation
      9. Assert the title can be translated to Japanese correctly
      10. Assert  Title and Content are still displayed in English

      Scenario 4.14 - The title of a web content added with a structure can be translated separately

      See scenario 4.15/4.16/4.17

      Scenario 4.15 - A text field content in customized web content can be translated separately

      Add New Test : AutoTranslation#CanTranslateTextFieldIndependently

      Test Steps:

      1. Go to system setting> Translation>Enable Google cloud translation
      2. Go to add a structure with Text field
      3. Go to add a web content article through the structure
      4. Go to translate the web content through side by side
      5. Change the target locale to Japanese
      6. Click the field translations for the title
      7. Assert the successful message can be displayed under the title
      8. Assert the Text field values haven't changed 
      9. Click the field translations for the Text field
      10. Assert the successful message can be displayed under the Text field
      11. Assert the Title field value haven't changed 
      12. Publish
      13. Go to the translation process to view the translation
      14. Assert the web content can be translated to Japanese correctly

      Scenario 4.16 - A text box field content in customized web content can be translated separately 

      Add New Test : AutoTranslation#CanTranslateTextBoxFieldIndependently

      Test Steps:

      1. Go to system setting> Translation>Enable Google cloud translation
      2. Go to add a structure with Text Box field
      3. Go to add a web content article through the structure
      4. Go to translate the web content through side by side
      5. Change the target locale to Japanese
      6. Click the field translations for the title
      7. Assert the successful message can be displayed under the title
      8. Assert the Text Box field values haven't changed 
      9. Click the field translations for the Text Box field
      10. Assert the successful message can be displayed under the Text Box field
      11. Assert the Title field value haven't changed 
      12. Publish
      13. Go to the translation process to view the translation
      14. Assert the web content can be translated correctly

      Scenario 4.17 - A rich field content in customized web content can be translated separately

      Add New Test : AutoTranslation#CanTranslateRichTextFieldIndependently

      Test Steps:

      1. Go to system setting> Translation>Enable Google cloud translation
      2. Go to add a structure with Rich Text field
      3. Go to add a web content article through the structure
      4. Go to translate the web content through side by side
      5. Change the target locale to Spain
      6. Click the field translations for the title
      7. Assert the successful message can be displayed under the title
      8. Assert the Rich Text field values haven't changed 
      9. Click the field translations for the Rich Text field
      10. Assert the successful message can be displayed under the Rich Text field
      11. Assert the Title field value haven't changed 
      12. Publish
      13. Go to the translation process to view the translation
      14. Assert the web content can be translated correctly

      Scenario 4.18 -A numeric field content in customized web content can be translated separately

      Add New Test : AutoTranslation#CanTranslateNumericAndDecimalFieldsIndependently

      Test Steps:

      1. Go to system setting> Translation>Enable Google cloud translation
      2. Go to add a structure with Numeric/Decimal **fields
      3. Go to add a web content article through the structure
      4. Go to translate the web content through side by side
      5. Change the target locale to Spain
      6. Click the field translations for the Numeric field
      7. Assert the successful message can be displayed under the Numeric field
      8. Assert the Decimal field value haven't changed
      9. Click the field translations for the Decimal field
      10. Assert the successful message can be displayed under the Numeric field
      11. Assert the Numeric field value haven't changed
      12. Publish
      13. Go to the translation process to view the translation
      14. Assert the web content can be translated correctly

      Scenario 4.19 - A decimal field content in customized web content can be translated separately

      See scenario 4.18

        Attachments

          Activity

            People

            Assignee:
            jeremy.chen Jeremy Chen
            Reporter:
            austin.chiang Austin Chiang
            Recent user:
            Jeremy Chen
            Participants of an Issue:
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Packages

                Version Package