Basic Tests

Confirm the following basic tests:

• You can log in to the CMS.
• You can create pages and components within the Site Tree.
• You can upload assets within the Assets Tree.
• You can check out and check in pages, components, and assets.
• You can mark and unmark pages and components for publish.
• You can save page, component, and asset changes.
• Ensure that the Preview tab properly renders pages.
• Ensure that no errors were thrown during the upgrade process. Review the upgrade report and log files for possible errors.

Advanced and Site-Specific Tests

Asset Tests

Confirm the following for Assets:

• All assets migrated to the CMS.
• You can upload assets within the Assets Tree without issues.
• You can mark/ unmark assets for publish.
• You can view the Assets Tree and available assets in the Assets Manager.
• You can view assets in preview.
• You can add and link all asset types in XHTML editor (i.e., images, documents, and media).
• You can edit images and code assets.
• You can use version control for assets and revert assets.
• You can categorize assets (i.e., apply taxonomy).
• Verify asset security for user groups.
• Verify that users can access assets via toolbar search.
• You can view asset assignments in the Assignments pane.
• You can add, advance, or remove assets in workflow.
• You can apply and remove lingual maps for assets and asset folders.

Workflow Tests

For each workflow within the site, confirm the following:

• You can completely transition a page, component, or asset through the entire workflow.
• Ensure that the system properly sends all workflow notifications.
• Ensure that publishes execute within the appropriate steps.
• Ensure that check in and check out triggers occur on the appropriate workflow transitions.
• Ensure that mark and unmark for publish events occur on the appropriate workflow transitions.
• Verify that drop-down menus display users and transition states as expected when advancing content items.

Publishing Tests

In Publishing System, confirm the following:

• Verify that the system defines publishing targets.
• Ensure that no errors display in publishing logs for any publishing target after full and incremental publishes.
• Ensure that publish speeds are adequate.
  Note

  If performance is slow, consider ceasing scheduled publishes in favor of at-will or workflow publishing.

Preview Tests

In Preview, confirm the following:

• Ensure In-context Editing (ICE) is enabled.
• Check ICE in the Preview tab.
• You can navigate to site links within the Preview tab.
• Verify that categorized pages display correctly.
• Ensure site navigations function correctly in Preview tab.
• Ensure that the Show All Pages checkbox works correctly (i.e., verify that pages, components, assets, and navigations work as expected.)
• Ensure that Preview is faster in CMS 10.5 than in previous versions. If not, contact Ingeniux Support.

XHTML Editor Tests

In the XHTML editor, confirm the following:

• Toolbar buttons display according to group settings.
• Ensure custom styles load as expected.
  Note

  You may need to enable importcss plugin if you have not done so.

Translation and Localization Tests

In WorldView, confirm the following (if applicable):

• You can create clone sections successfully.
• You can add language locales can in System Options via WorldView Configuration.
• You can apply language locales to pages, components, folders, and assets.
• Ensure that the appropriate translation workflows apply to WorldView pages.

Custom Hook Tests

In Custom hooks, confirm the following (if applicable):

• Review custom hook usage and ensure that any actions coded into Custom Hooks are working properly.

In-Context Editing Tests

In In-context Editing (ICE), confirm the following:

• You can update and save all ICE editable fields.

Custom Application Tests

In Apps tab and custom tabs, confirm the following:

• Ensure that any items enabled in the Apps pane display properly.
• Ensure that all custom tabs display properly to the correct users.

Automated Task Tests

For automated tasks, confirm the following:

• Ensure that publishing has the appropriate automation settings. If automated publishing was activated due to performance issues, you can be disable it to return the CMS instance to manual publishing.
• Ensure that other automated tasks work as expected.

Schema Tests

In Schema Designer, confirm the following:

• Verify that there are no invalid schemas or schema errors.
• Verify that schema syncing works properly by completing the follow tasks:
  • Add and remove elements.
  • Verify that content item schema versions update after syncing.
  • Verify that embedded components sync.
  • Verify that all pages and selected pages sync.

CMS 10.6 DITA Publishing Pipeline Tests

If your implementation uses the CMS 10.6 DITA Publishing Pipeline, confirm the following:

• Verify your DITA Administration settings are configured properly.
• Verify publishing targets with DITA post-publish processors are configured properly.
• If your implementation integrates with an XML editor (e.g., Fonto, Oxygen Desktop Plugin), verify the editor works properly by completing the following tasks:
  • Verify the editor interface loads and opens successfully.
  • Open an existing DITA asset or create a new one in the editor.
  • Check in, check out, and save content using the editor interface.
  • Ensure editor tools and actions are working properly.
• Ensure DITA preview processing runs as expected.
• Ensure DITA publishing pipeline processing runs as expected.
• If your implementation uses DITA aliases, ensure your alias structures display as expected in the Site Tree and in preview/publish outputs.

Installation Outcomes After Upgrade

• Verify that the Ingeniux CMS 10.5–10.6 instance application setup installed correctly via Internet Information Services (IIS) after upgrade. Confirm that IIS lists an application pool for each CMS site instance and DssPreview and lists a Web site for each CMS site instance.
• Verify that the Raven Database service installed correctly and runs as expected.