Login to participate
Endpoint Management & Virtualization BlogsRSS

Mandatory TESTS

TilakGovind's picture
TilakGovind
September 11th, 2008
Filed under: , , ,

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.

0 votes
ThomasVogel's picture
ThomasVogel
1 year 10 weeks ago

Additional mandatory tests

I would like to add another test scenario, that has shown a lot of installation and application problems in the past and this is:
"Install the software of an terminal server". As more and more companies use terminal services (either native RDP from MS or ICA from Citrix) this has in the meantime become a mandatory test for me.
Although the installer has administrative rights in most of the cases, a "Startup Test" with a minimum of functionality should be performed to see if there are principal "multiuser" problems in a software package. These can arise from using common resources (e.g. HKLM in the registry instead HKCU) performance bottlenecks that are not visible in a single user computer, etc.

Regards,
Thomas.

PS: Of course many of these problems (like use of Registry keys) could be tested upfront by the package creator, but any dynamic problems cannot.

0 votes
looeee's picture
looeee
1 year 5 weeks ago

Great Test Script :)

You should always test the user with no rights before you test the software with the admin user.

Quite often the application can fix itself on 1st run (e.g. ActiveX EXEs reregistering themselves) in a way that it cannot in a restructed user's account.

Your uninstall commandline is "msiexec /x “app.msi” TRANSFORMS=”transform.mst”"
You do not need to specify the transform at uninstall- (or repair-) time.

As a restricted user, I test that the settings stick in Tools->Options by exiting and restarting the program.

0 votes