Software Deployment

Because each environment is different the requirements that testing needs to achieve is different for each site.

The basics would be:

Can you login to the app
Can you load the app
Can you print from the app
Can you open a file from the app
Can you save a file from the app
Can you get into each menu item in the app

Those are a few basic tests I always do, of course there will be specifics for applications that link with others.

Paul

Most of the time application testing involves testing the existing applications as well to make sure there is no interference from the new install. In most cases there isn't, but sometimes apps lay down system files which is a big no no.

If you do a search on the forums, I've posted on this topic, as have others.

The Installshield courseware does a good job covering this as well.

additional to Inabus's comments you should also be testing this with multiple user accounts. One of the main things you want to look for here is that

user profile fix up scenarios are functional.
no self healing occurs for unplanned reasons.
lock down users can access application after installation.

Additional to John's recommendation regarding "lock down users".

Test A Package In A Locked-Down Environment
Per-machine advertisement followed by installation by a normal user account
is the most comprehensive test for this situation.

As an administrator use the following command line to advertise the application to the
local machine: msiexec.exe /jm package.msi ALLUSERS=1 /qb

Note: No package components will actually be installed, MSI will simply install the
advertised shortcuts and icons, file types and extensions, COM class registration, and
package installation information.

Next, logon with a normal user account and trigger the installation process by running the
shortcut or via a file type association. The application should start and run with
no problems at this point.

Be sure to make changes to settings, toolbars, and other preferences- then exit and
relaunch the application to ensure such information is capable of being retained in
this security context.

ORIGINAL: Inabus

Because each environment is different the requirements that testing needs to achieve is different for each site.

The basics would be:

Can you login to the app
Can you load the app
Can you print from the app
Can you open a file from the app
Can you save a file from the app
Can you get into each menu item in the app

Those are a few basic tests I always do, of course there will be specifics for applications that link with others.

Paul


Okay great it basically looks like an ad hoc type testing. Thanks for the info, will search the forums and draw up a testing plan that pertains to our specific environment.

Carlo

Because each environment is different the requirements that testing needs to achieve is different for each site.

The basics would be:

Can you login to the app
Can you load the app
Can you print from the app
Can you open a file from the app
Can you save a file from the app
Can you get into each menu item in the appI would add:

- Do the apps in your build still work after the app being tested is uninstalled?