For ‘.msi’ packages, on windows, this is done by the system’s package installer program ‘msiexec.exe’.Īt first, the windows installer executable msiexec.exe needs to be registered at the squishserver, which can be easily done by the squishrunner command: This can be done in one of the following ways:įor running such a test, Squish needs to first hook into that process which is performing the package’s installation flow. Lets say we want to test a setup-package ‘ Installer.msi‘. I will give two short examples showing how ‘ Squish for Windows‘ can be used for automating such ‘.msi’ based software installers.

So this can’t be hooked and automated the usual way like other programs.īut in most cases, testing should be possible anyway. So, to minimize the chances of losing a potential customer, it is important to develop and run additional tests (besides the regular unit and GUI tests) against the software’s installer packages.Ī setup program in most cases is a compressed data package, consisting of just the software’s binary files (plus some additional installation informationĪbout where and how these have to be installed and registered) and often there is no executable program code contained within. For a user who is evaluating new software, the installation process is usually the first interaction he’ll make with that product.ĭuring this process, any error or misbehavior which makes the installation of the software difficult could lead the user to switch to a competitor’s product.

Batch file to install msi