Details

    • Sprint:
      LIMA | #36 | DEV | May18-Jun08, LIMA | #34 | DEV | Apr06-Apr27, LIMA | #35 | DEV | Apr27-May18, LIMA | #37 | DEV | Jun08-Jul06

      Description

      As a translator

      I want to be able to translate only the fields that I want

      so that I don't need to translate the whole web content

       

      Design

      Figma

       

      Acceptance criteria

      Given a web content article
      When the user clicks on the button to translate a specific field
      Then the system translates only that field keeping the others as they where

       

      Test Scenarios

      ID Test Priority Test Scenarios Covered by Backend (Unit/Integration)? Covered by Frontend Test to add
       4.8 4 A field translation button  will be displayed on the right side of the fields after enabling the Google Cloud translation No x  AutoTranslation#TranslateButtonsAreDisabledWhenFieldsAreNull
       4.9 4 The field translation button will be hidden after disabling the Google Cloud translation No  x AutoTranslation#CanViewTranslationAfterDisablingGoogleConfiguration
       4.10 4 The field translation button will be disabled when translating field without content No  x  AutoTranslation#TranslateButtonsAreDisabledWhenFieldsAreNull
       4.11 5 A basic web content title can be translated separately
      - given a valid server response when the user clicks on the auto-translate general button updates sends a POST request to the server
      No  x  AutoTranslation#CanTranslateTitleFieldIndependently
       4.12 5 A basic web content content can be translated separately
      • given a valid server response when the user clicks on the auto-translate field or general button updates the input with the translated message with HTML unescaped character (the HTML unescaped it's related with LPS-133164)
        - given a valid server response when the user clicks on the auto-translate field or general button renders a success message
      No   x  AutoTranslation#CanTranslateContentFieldIndependently
       4.13 5 A basic web content description can be translated separately  No No   AutoTranslation#CanTranslateDescriptionFieldIndependently
       4.14 5 The title of a web content added with a structure can be translated separately No   No  AutoTranslation#CanTranslateTextFieldIndependently
       4.15 5 A text field content in customized web content can be translated separately  No No   AutoTranslation#CanTranslateTextFieldIndependently
       4.16 5 A text box field content in customized web content can be translated separately No  No   AutoTranslation#CanTranslateTextBoxFieldIndependently
       4.17 5 A rich field content in customized web content can be translated separately No  No   AutoTranslation#CanTranslateRichTextFieldIndependently
       4.18 5 A numeric field content in customized web content can be translated separately No  No   AutoTranslation#CanTranslateNumericAndDecimalFieldsIndependently
       4.19 5 A decimal field content in customized web content can be translated separately No  No   AutoTranslation#CanTranslateNumericAndDecimalFieldsIndependently
      4.20 5 Given an error server response when the user clicks on the auto-translate field or general button an error server response No  x

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              austin.chiang Austin Chiang
              Reporter:
              pablo.agulla Pablo Agulla
              Engineering Assignee:
              SE Support
              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
                  Master