Test Scenarios Coverage | Poshi Validation

• 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: https://github.com/austinchiang/liferay-portal/pull/835
• Test Type:
  • Functional

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:

1. Enable the feature
2. Add a basic WC article (Web Content Title, Web Content Content)
3. Export for Translation of Japanese German
4. Translate it with the .xliff file (Need to investigate how to update the xliff file from dependencies)
5. Click on Import Translation
6. Select the translated file
7. Import the translated file
8. Assert the system shows a success message indicating the import was published
9. View the web content article
10. 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:

1. Enable the feature
2. Add a basic WC article (Web Content Title, Web Content Content)
3. Export for Translation of Spanish
4. Translate it with the .xlf file(the default file type)
5. Click on Import Translation
6. Select the translated file
7. Import the translated file
8. Assert the system shows a success message indicating the import was published
9. View the web content article
10. 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