Software Distributor (SD-UX) Administration Guide HP-UX 11i v1, 11i v2, and 11i v3 (762797-001, March 2014)

3. Run swinstall to install the full product again. Set the defer_configure option to “false”
to avoid executing the configure scripts.
• After the installation completes, run swconfig to configure your product.
• 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.
• Now run swconfig -u to unconfigure your product.
• Study the resulting file system to see if the unconfigure script performed the expected
“undo” actions.
• Run swconfig again to re-configure your product.
• Study the resulting file system to see if the configure script performed the expected actions.
4. Run swverify to execute the verify script(s).
• After the verification completes, check the ${SW_ROOT_DIRECTORY}var/adm/sw/
swagent.log file for any problems, either in the verify script or the format/contents of
the messages generated by it.
5. If a previous version of the product can be updated to this version, then re-run the first test by
updating this product to a system where the previous version has been installed and configured.
6. Note that configure and unconfigure scripts are never run unless the ${SW_ROOT_DIRECTORY}
is /. However, verify scripts are run in both cases.
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 remove 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 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 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.
220 Using Control Scripts