Test upgrade - Alfresco Content Services - 23.4 - 23.4 - Ready - Alfresco - external

Alfresco Content Services
Platform
Alfresco
Product
Alfresco Content Services
Release
23.4
License

Testing an upgrade checks that Content Services is successfully upgraded and working as expected after the upgrade.

Test after upgrade

You’ve successfully upgraded. Now test that the core features that you intend to use work as expected.

Here are some of the tips to help you familiarize yourself.

Note: We recommend that you create one or two test sites for testing purpose and put all your test data in those sites. After finishing the tests, you can delete the test sites in order to clear your database.
  • Check if the roles that users had in the previous version are still valid in the new upgraded version.
  • Check if your data or documents in the previous version are available in the new upgraded version.

Test after customizing upgrade

There are a number of tests that you can perform after customizing an upgrade:

  • Make sure that the server is up and running.
  • Make sure that the errors in the alfresco.log file are checked and understood.

Test after upgrade and configuration

You’ve successfully upgraded and configured Content Services. Now make sure that the features and customizations you’ve added work as expected.

Here are some of the tips to help you test your customizations.

Note: We recommend that you create one or two test sites for testing purpose and put all your test data in those sites. After finishing the tests, you can delete the test sites in order to clear your database.
  • Check if the users or groups created previously still exist.
  • Check if all the dashboards created previously still exist.
  • Check if the folders in the document library that were created prior to the upgrade still exist.

Test after cluster upgrade

You’ve successfully upgraded and configured Content Services in a distributed/clustered environment. Now make sure that the features and customizations you’ve added work as expected.

Here are some of the tips to help you test your customizations.

Note: We recommend that you create one or two test sites for testing purpose and put all your test data in those sites. After finishing the tests, you can delete the test sites in order to clear your database.
  • Check that various components are communicating with each other.
  • For a clustered upgrade, check that if one node is down, then the request is forwarded to the next available node.

Test after cluster upgrade and configuration

You’ve successfully upgraded and configured Content Services in a distributed/clustered environment. Now make sure that the features and customizations you’ve added work as expected.

Here are some of the tips to help you test your customizations.

Note: We recommend that you create one or two test sites for testing purpose and put all your test data in those sites. After finishing the tests, you can delete the test sites in order to clear your database.
  • Check if the users or groups created previously still exist.
  • Check if all the dashboards created previously still exist.
  • Check if the folders in the document library that were created prior to the upgrade still exist.
  • Check if clustering is working properly by running the cluster validation tool in the Admin Console