Software Distributor Administration Guide HP-UX 11i v1, 11i v2, and 11i v3 (5900-2561, March 2013)

11.9.1 Testing Installation Scripts
For checkinstall, preinstall, and postinstall scripts you should perform at least these tests. All tests
can be performed on the local system (that is, by doing local installs).
1. The basic test:
• Run swinstall to install the full product (that is, all the filesets). To avoid testing the
configure script(s), either do not include any in the product, or set the defer_configure
option to “true.”
• After the installation completes, check the ${SW_ROOT_DIRECTORY}var/adm/sw/
swagent.log file for any problems, either in the scripts or the format/contents of the
messages generated by the scripts.
• Study the resulting file system to see if the scripts performed the expected actions.
• Re-run the test by re-installing the same product.
2. If you want to avoid the time spent loading files, then set the reinstall_files option to
“false” and the reinstall_files_use_cksum option to “false.”
3. If a previous version of the product can be updated to this version, then re-run the test by
updating this product where the previous version has been installed.
4. If your checkinstall 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 checkinstall
script correctly detects them.
5. Re-run the 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.)
6. 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 (swinstall product:new_location).
Make sure that the 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.)
7. 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.
11.9.2 Testing Configuration Scripts
For configure, verify, and unconfigure scripts you should perform at least these tests. All tests can
be performed on the local system (that is, by doing local installs).
1. Run swinstall to install the full product (that is, all the filesets). Let the installation process
perform the configuration task (and run your configure script(s)).
• After the installation and configuration completes, check the
${SW_ROOT_DIRECTORY}var/adm/sw/swagent.log file for any problems, either
in the configure script or the format/contents of the messages generated by it.
• Study the resulting file system to see if the configure script performed the expected actions.
• Test the product itself to see if the necessary configuration tasks were performed such that
the product is ready to use.
2. Run swremove to remove 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 unconfigure script or the format/contents of the messages generated by it.
• Study the resulting file system to see if the unconfigure script performed the expected
“undo” actions.
11.9 Testing Control Scripts 225