Migrate module to Magnolia 5 (MGNLCTS-31)

[MGNLCTS-43] Design and Perform Manual Black Box Tests Created: 03/Jan/14  Updated: 12/Jun/14  Resolved: 13/Jan/14

Status: Closed
Project: Content Translation Support
Component/s: None
Affects Version/s: None
Fix Version/s: 2.0

Type: Sub-task Priority: Neutral
Reporter: Cheng Hu Assignee: Peili Liang
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:

 Description   

Translation File Download Tests

  • Download something, add german translation, upload.
    • Check the help text in the dialog is as specified in the specification.
    • Check the German translation changed.
  • Download something, add Chinese translation, upload.
    • Check the Chinese translation changed.
  • Change something in Pages App in English, download.
    • Check the English changed.
    • Check that it contains the translations of the old English.
  • Change something in Pages App in Chinese, download.
    • Check the Chinese translation changed.
    • Check that it contains the old English and the other translations of the old English.
  • Add a language.
    • Check it causes a new column in the downloaded translation file.
  • Download CSV file and upload, with property value containing "," characters.
    • Check properly escaped in CSV.
  • Download Google CSV and upload to Google with conversion turned on.
    • Check Google automatically translates.
  • Download XLiff, change, and upload.
    • Check the translations are updated.
  • Download a translation file.
    • Check temp file really is deleted.
  • Change some to be translated content using Pages App.
    • Check the modification date of the page is updated in the downloaded translation file.
  • Download file containing pages and subpages.
    • Check the "Link to page" fields are correct.
  • Change the domains name in site definition.
    • Check the "Link to page" fields reflect the name change.
  • Download translation file for the entire demo-project.
    • Check the label part of "Title" column is correct in giving the dialog name. In particular, none of the labels should be paths. (There is a path label, dialogs.paragraphs.teasers.stkTeaserOpener.label but this is due to a bug MGNLSTK-1335)
    • Check the title part is correct in giving the title of the field.
  • Download translation file for the entire demo-project when using language other than English.
    • Check the label part of "Title" uses the default language label rather than English in giving the dialog name.
    • Check the title part is correct in giving the title of the field in the default language rather than English.

Translation File Upload Tests

  • Update translations and upload, the root page being updated is hidden and not selected.
    • Check the help text in the dialog is as specified in the specification.
    • Check that there is a confirmation dialog after uploading a file and clicking OK in the dialog.
    • Check that the message in the confirmation dialog gives the path to the root node being updated, in accordance with the specification.
    • Check that after confirming, the tree expands to show the root node and the root node is selected.
    • Check the new translations changed.
  • Select some pages beforehand, update translations, change the filename to be a non-path, and upload.
    • Check that there is a confirmation dialog after clicking OK in the dialog.
    • Check that the message in the confirmation dialog is generic and does not refer to the root node being updated, in accordance with the specification.
    • Check that after confirming, the tree does not change in terms of expansion or selection.
    • Check the new translations changed.
  • Check overwrite existing value works both on and off.
    • Check xls.
    • Check csv.
    • Check xliff.
  • Check import empty value works both on and off.
    • Check xls.
    • Check csv.
    • Check xliff.
  • Upload with overwrite after page has changed between download and upload, with page text changed.
    • Check it causes the text to change according to the file.
  • Upload with overwrite after page has changed between download and upload, with the node being updated deleted.
    • Check all but the deleted node is still updated, and a log entry is created for the deleted node.
  • Upload with overwrite after page has changed between download and upload, with the node being updated moved.
    • Check the moved node and all other nodes are still updated.
  • Upload some change.
    • Check the modification date of the page in Pages App is changed.
  • Upload if node ID changed accidentally in upload file.
    • Check everything else is still uploaded and a log entry is generated for the erroneous node ID.
  • Upload if property name after key has been accidentally changed.
    • Check upload still happens and new property is created, same as M4.5.
  • Upload if locale column name has been accidentally changed to something incorrect.
    • Check that a red pop-up is displayed with the title being "Import translation file failed due to invalid locale name" and nothing has been uploaded.
  • Upload if any other column name has been accidentally changed.
    • Check that a red pop-up is displayed with the title being "Import translation file failed due to invalid column name" and nothing has been uploaded.
  • Upload if actual file format is different from selected file format.
    • Check that a red pop-up is displayed with the title being "Import translation file failed due to invalid file format" and nothing has been uploaded.
  • Upload if no file has been selected.
    • Check normal field validation and markup happens in dialog.
  • Upload if value in any column other than node ID and translation columns have been changed accidentally.
    • Check upload still happens successfully.
  • Upload if column orders accidentally reversed.
    • Check upload fails with red error dialog.
  • Upload if file deleted after input but before dialog confirm.
    • Check upload still successful.
  • Add a language column by myself and that language is enabled in the system
    • Check upload file is still successful and the translations have been uploaded, same as M4.5.
  • Upload when user configured importer throws an exception
    • Check a red dialog is displayed saying that "Import translation file failed" followed by the exception message.
    • Check nothing is uploaded.
  • Upload when the extension for the importer in the configuration tree does not match the actual imported file extension.
    • Check upload still completes successfully as long as the file is in the actual expected format.
  • Upload when an empty row has been accidentally added in the middle of the uploaded file.
    • Check a red dialog is displayed saying that "Import translation file failed".
    • Check nothing is uploaded, same as M4.5.
    • This does not seem like the ideal behavior, and perhaps the empty line should be ignored?
  • Upload when two rows try to update the same node/property.
    • Check the bottom row wins and its update is uploaded, same as M4.5.

Preview Tests

  • Click the preview action while a page is selected
    • Check that the Pages App is opened and the page is displayed in a tab in preview mode
  • Click the preview action while a page is selected, with the page already open in a tab in Pages App
    • Check that the Pages App is opened and the tab displaying the page is brought to front with the page in preview mode
  • Double click on a page in CTS App
    • Check that the Pages App is opened and the page is displayed in a tab in preview mode
  • Select one page, no page, and multiple pages
    • Check that action is available only when one page is selected

Publish Tests

  • Click the Publish page action
    • Check that the page successfully publishes
  • Click the Publish incl. subpages action
    • Check that the page and all its subpages successfully publishes
  • Click the Unpublish page action for a page that has been published with new translations
    • Check that the page is successfully unpublished
  • Select one page, no page, and multiple pages
    • Check that actions are available only when one page is selected

Configuration Tree Tests

  • Add/delete field types to translate in modules/content-translation-support/config/controlTypesToExport.
    • Check the right field types are included or excluded.
  • Add new importer/exporter in configuration tree.
    • Check it is included in the download and upload dialogs and see it work.
  • Change the file extension used in the configuration tree.
    • Check file extension of downloaded file is changed.
  • Change the nodeDataToTranslateFinder to another class.
    • Check it successfully uses the other class.

Generated at Mon Feb 12 00:32:39 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.