Create a list of the key features and functions in your applications and evaluate their functionality under Lotus Notes/Domino 6. Apply any Notes/Domino 6 templates and the Notes/Domino 6 format to applications. Be careful to document and test the following:

• Custom changes you have made to standard templates. Notes/Domino 6 templates may incorporate the functionality you added, making custom changes unnecessary, or may have changed how the feature you are using works.
• Reuse of template code. If you duplicated standard template code, such as LotusScript(R) or @commands, in your applications, be aware that changes in how this code functions in templates will also be reflected in how your application works.
• Use of undocumented features or settings. You may have used features, commands, or items in Notes that are undocumented and unsupported. While these items may have worked in earlier releases, they might not in Lotus Notes/Domino 6.
• Creative workarounds. You may have implemented coding or design changes to overcome a limitation in earlier releases. These workarounds may no longer be necessary in Lotus Notes/Domino 6, or functionality changes could change how the workarounds operate.

Steps for documenting applications

Documenting applications organizes essential information about the application before you begin testing. If you have not already documented your application, complete these steps.

1. (Optional) Create a database to store testing information. This helps you keep track of progress, especially if you have many applications to test. If other people need to use this database at several sites, create a design template that they can use.

2. Document the type of application and its purpose. For example, determine whether this is a discussion, mail-in, or IBM Lotus Workflow(TM) application. If it is a mail-in application, document the name that the Domino Directory uses. If it is a Lotus Workflow application, document the databases that this application uses.

3. Document any external databases or files that this application uses. For example, determine whether this application accesses data stored in an external database or file using @DbCommand or @DbLookup.

4. Document any Notes databases that this application references. If the application references databases created with system templates -- for example, the Domino Directory -- document whether the formulas in the application reference hidden views. Many system design templates are changed in Lotus Notes/Domino 6. Therefore certain views may no longer exist. To prevent problems, do not design applications that rely on hidden views in system design templates.

5. Document any Notes API programs that this application uses or any API programs that modify this application.

6. Document any external OLE applications that this application uses.

7. Document the servers that this application replicates with.

8. Repeat Steps 2 through 7 for every application you need to document.

Use a test environment

A test environment is an ideal place to experiment with new Notes/Domino 6 features and functionality -- it provides real-world conditions without risk to your applications or impact on your business. Before rolling out a new Notes/Domino 6 feature set or code, use it in your test environment to prove its stability and that it functions as intended. Notes/Domino 6 features are generally not available to earlier clients, so evaluate their usability and impact on earlier releases before rolling them out to your applications and users.

Back up key applications before upgrading them. If there are problems during the upgrade, or if you encounter issues after upgrading, you can replace the application with the backed-up version.

Note After upgrading the design of an application, you must rebuild the views in that database. You can do this by opening the database in a Notes client and pressing CTRL + SHIFT + F9, or at the Domino server console, type the command:

load updall databaseName.nsf -r

and press ENTER.

Steps for testing applications

Your testing strategy may vary depending on the number of applications your organization needs to test.

1. If you have not done so already, install Lotus Domino Designer on your workstation.

2. Create documents using each form in the application, including hidden forms. Make sure that you can enter information into each field in the form, that buttons work correctly, and that the text on the form displays correctly.

3. Open in each view the documents you just created. Make sure that they display correctly and that formulas calculate correctly. Make sure hidden views work correctly.

4. Display the documents you just created. Make sure that they display correctly and that formulas calculate correctly.

5. If the application uses external databases or files, modify data in the external database or file and make sure the application updates the formulas correctly.

6. If the application uses formulas that reference hidden views in system databases -- for example, the Domino Directory -- make sure these formulas work correctly.

7. If the application uses external OLE applications, create forms that use the OLE application and launch the objects.

8. Test any agents to make sure they work correctly.

9. Check the security of the database. For example, check the access control list; encryption keys; roles; and the readers and authors access.

10. If the application uses selective replication formulas, test these formulas to make sure they work correctly. For example, check the replica database to make sure the documents you selected replicated properly.

11. Repeat Steps 2 through 11 for every application you need to test.

See Also

Planning the upgrade