This procedure contains general guidelines for running generated test cases. Each type of test case is more fully explained in its own topic. You can set the status for a test case or a test item.

Test cases are listed in the left pane of Test Expert.

These are some of the mandatory TESTS to be done.

Some tests are informational and might not require a Pass or Fail status for each test item. Example: When you run the Extra Files or Extra Registry Entries test cases, you see a list of items that were accessed but not installed. These items do not necessarily require a Pass or Fail status.

Many times I come across articles, where people discuss on which to choose WISE Script or VBScript while creating Custom Action in the package. Here are some advantages and disadvantages of both.

While WISE Script is easy to make, I mean takes less effort, VBScript can be very complicated. People who do not know VBScript often find themselves searching for, and copying code from net. WISE Script can be easily written once you have basic understanding of statements. I give this point as an advantage to WISE Script, but people who know how to code in VBScript, will always choose that as an easy option.

Personally, I prefer VBScript over WISE Script because it has some really good advantages. As you might know, we compile WISE Script to an exe and include that in a package. But in doing this, we lose the code...

There are many installshield applications (MSI)/ Other Vendor MSI which come wrapped in setup.exe. The packagers can extract the MSI easily, but while installing the MSI, sometimes an error comes which says that the MSI can be installed only through setup.exe.

This can be solved by two ways:

1. For Installshield applications, Set the Property ISSETUPDRIVEN=1, this will remove the error and you can install your MSI.
2. If the above does not work and also for non Installshield packages, if you still get the error, then you can create a verbose log file and search for "Return Value 3". This will take you to the Custom Action which has caused the error. You can disable this CA and then try installing the application. This works most of the time. However there are some applications in which...

Sometimes you may encounter the problem of unnecessary repairs of MSI while launching the shortcut in the same logged in user. Here is the way to troubleshoot this problem.

You can go to eventviewr (by typing eventvwr in Run command) then to applications and check the latest error message after repair. It will tell you which component is missing and because of which MSI went for self heal.

You can now check out this component in your package and see what the problem is. Maybe your keypath is a moving target for that component.