Software Distributor Administration Guide for HP-UX 11i

Using Control Scripts
Testing Control Scripts
Chapter 11 405
7. If your product is locatable (that is, it can be installed into a different
location), then re-run the tests by installing and configuring the
product in a different location. Make sure that the scripts perform all
their operations in the new location, and not the default location.
(This verifies the correct use of $SW_LOCATION by your scripts.)
8. If you have a complex script, run additional tests for your product
that you feel will give you confidence your product has been installed
correctly on the system. For example, only install certain subsets of
your product instead of the full product.
Testing Removal Scripts
For checkremove, preremove, and postremove scripts you should perform
at least these tests. All tests can be performed on the local system (that
is, by doing local installs). There is no value gained by testing your
scripts by installing to remote target systems.
1. Run swinstall to install the full product (that is, all the filesets).
Avoid configuration by setting the defer_configure option to false.
• Run swremove to removed the unconfigured product.
• After the removal completes, check the
${SW_ROOT_DIRECTORY}var/adm/sw/swagent.log file for any
problems, either in the removal scripts or the format/contents of
the messages generated by the scripts.
• Study the resulting file system to see if the removal scripts
performed the expected actions.
2. Run swinstall to install the full product (that is, all of the filesets).
Let the installation process perform the configuration task (and run
your configure script(s)).
• Run swremove to removed the configured product.
• After the unconfiguration and removal completes, check the
${SW_ROOT_DIRECTORY}var/adm/sw/swagent.log file for any
problems, either in the removal scripts or the format/contents of
the messages generated by the scripts.
• Study the resulting file system to see if the removal scripts
performed the expected actions.