Verifying Correct Menu Operation

It’s a common practice to customize the NNM menu structure. One goal of menu customization is to prevent certain classes of users from making changes to NNM’s configuration. Such users are meant to be operators of the NNM tool. Such users often have the $OVwRegDir environment variable defined in their startup shell script to point to a home grown directory tree with registration files, so that when NNM is launched, ovw scans this directory structure instead of the standard one at $OV_REGISTRATION.

You have to tolerate some potentially tedious regression testing to verify that your custom menus work properly for each user type:

Is each menu item in the right place?

Do the selection rules work for each menu item?

Is the actual code the menu executes loaded and working?

You may have to document the available menus for each type of user. One way is to incorporate ovw menu screenshots into the documentation. Why not let ovw parse the menus to help you create the documentation? The alternative is to manually draw the menu diagrams.