Software Distributor Administration Guide for HP-UX 11i

Using Control Scripts
Testing Control Scripts
Chapter 11406
3. If your checkremove script can generate error or warning conditions
based on the current activity or configuration of the target system,
then enable those conditions to ensure that the checkremove script
correctly detects them.
4. Re-run the first test by installing into an alternate root directory
(swinstall -r) instead of the primary root directory (“/”). Make sure
that the scripts perform all of their operations (if any) within the
alternate root directory. (This verifies the correct use of
${SW_ROOT_DIRECTORY} by your scripts.)
5. If your product is locatable (that is, it can be installed into a different
location), then re-run the tests by installing the product into a
different location. When removing the product, make sure that the
removal scripts perform all of their operations in the new location,
and not the default location. (This verifies the correct use of
$SW_LOCATION by your scripts.)
6. 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, then perform the remove
operations. (Or only remove subsets of the fully installed product.)