-
Type:
Technical Testing
-
Status: Closed
-
Priority:
Minor
-
Resolution: Completed
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Translations Management
-
Labels:None
-
Sprint:LIMA | #19 | May26-Jun16, LIMA | #20 | Jun16-Jul07, LIMA | #21 | DEV | Jul07-Jul28
-
Git Pull Request:
-
Test Type:
Test Scenario 1.6: User can select an xliff file when importing a translation for a web content
See Test Scenario 1.8
Test Scenario 1.7: User can import an xliff file to corresponding web content
Translations#ImportWebContentWithXliffFile
Test Steps:
- Enable the feature
- Add a basic WC article (Web Content Title, Web Content Content)
- Export for Translation of
JapaneseGerman - Translate it with the .xliff file (Need to investigate how to update the xliff file from dependencies)
- Click on Import Translation
- Select the translated file
- Import the translated file
- Assert the system shows a success message indicating the import was published
- View the web content article
- Assert the title and content are translated
Test Scenario 1.8: The translation is added to the web content once the user publishes the imported translation
Translations#ImportWebContent
Test Steps:
- Enable the feature
- Add a basic WC article (Web Content Title, Web Content Content)
- Export for Translation of Spanish
- Translate it with the .xlf file(the default file type)
- Click on Import Translation
- Select the translated file
- Import the translated file
- Assert the system shows a success message indicating the import was published
- View the web content article
- Assert the title and content are translated
Test Scenario 1.10: All the fields in the xliff file can be imported into the web content
See Test Scenario 1.7 and 1.8