Testing application upgrades

In general, application upgrades occur seamlessly without issue. To test Domino application upgrades, follow these best practices.

Review the list of removed features

Before fully testing your applications, review the list of features that have been removed from the Domino server platform in recent releases. See the Related information.

Review changes to the OpenJDK

For information about the OpenJDK included in the Domino 12 server, see New Java Runtime Environment.

Test an upgrade of a sampling of applications

Include in your upgrade testing:

  • Mission-critical applications that are based on different designs
  • Applications used by executives
  • Complex or custom applications that include:
    • Back-end integration
    • Reliance on third-party software
    • Undocumented functions and features
    • Extensions or add-in tasks using nsf_hooks, ext_mgr, and home-grown APIs
  • Sample of applications that use a common or standard template
Note: Use the Recompile All LotusScript tool in Designer to check for LotusScript issues.

Documents test results

Document the results of testing and convey them to the application developers.

Resolve issues

Resolve issues found based on your priorities and testing results:

  • Decide which application problems to fix before deploying to production.
  • Create a small team to address problems that arise after deploying to production.
  • Put applications into the pilot test environment for acceptance testing.
  • On successful testing, archive copies of new templates.