Destroyed Files Test Case - Symantec WISE PACKAGE STUDIO 8.0 - REFERENCE V1.0 Reference

Wise Package Studio Reference

Destroyed Files Test Case

Quality Assurance module only.
The Destroyed Files test case in Test Expert shows files that existed on the computer
before installation, but were missing after uninstall.
Note
Uninstall tests do not appear if a group is open.
After uninstall tests are run, the test case list is populated with destroyed files and all
statuses are set to Pending. Review the list and select the status for each test item.
Because all uninstall tests are run at the same time, the test items for every test case in
the Uninstall Tests group are updated simultaneously.
This test compares the pre-installation snapshot to the post-uninstall snapshot and
reports the differences between the two snapshots. Files accessed by other applications
can interfere with the test results. Before you run this test, close all applications other
than Wise Package Studio and Test Expert, including all background applications and
services that might access files or registry entries on the testing computer.
Normally, an installation should not uninstall files that it did not install. If it does, this is
a serious error because removing files that another application installed could potentially
break the other application.
This error can be caused when two separate packages install the same file to the same
place, but the file has a different component ID in each package. Example: Suppose
Package1 installs sample.dll into the System32 directory, then Package2 installs a newer
version of sample.dll over the original. When Package2 is uninstalled, it removes
sample.dll, breaking Package1.
How to Fix Errors
The best method is to isolate the file using Application Isolation in Wise Package
Studio. This tool isolates shared .DLLs in the application directory of the application
that uses it, ensuring that each application uses its own version of the file.
See Application Isolation
If you have access to both packages that install the file, and the file is really the
same in each, try aligning the component IDs of the components that contain the
file. Open the package in Windows Installer Editor and align component IDs on the
Setup Editor > Components tab.
Set the .MSI to leave the file installed during uninstall. To do this, open the package
in Windows Installer Editor. Display the component's details on the Setup Editor >
Components tab and mark Leave installed on uninstall. This has the
disadvantage of bloating the computer's contents, because the file will not be
uninstalled by the other application either.
See also:
How to Run Uninstall Tests
About Test Cases on page 164
on page 89.
on page 194
Test Expert
197