Wise Package Studio Reference
188
Test Expert
would want to do so, because running each test requires a complete exercise of the
application’s functions.
During application execution tests, an Application Monitor window appears. A series of
graphs represent the percentage of items that have been accessed so far during testing.
For details of each graph, see the individual test case descriptions.
See
How to Run Application Execution Tests
on page 189.
Note
A security setting in Windows Vista or later operating system prevents application
execution tests from working. When you try to run a test, a prompt appears and
provides the option to disable the security restriction. If you choose to disable the
security restriction, the following registry setting is set:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Windows>LoadAppInit_DLLs=1
The initial default for this setting is 0. If you disable this restriction, your computer’s
vulnerability to malicious attack is increased. However, if you run Test Expert in a
testing environment, the increased vulnerability might not be a critical issue.
Requirements
z
Application execution tests require the application to be installed. Run the
installation tests to install the application.
z
It is preferable to install the application either on a clean machine or on a computer
that contains the default software common to all computers on your network.
z
The Application Monitor window must remain open while you are running the
application, and must be closed when you finish. Closing the window stops the
monitoring of the testing computer.
Tips
z
If an error occurs when a file is accessed, the status is set to Fail and the error from
the operating system is displayed in the Error column. This lets you track such
things as missing files and user rights lacking the necessary permissions.
z
Application execution tests are primarily informational. Example: The Extra Files
test case might reveal that a printing-related system file is accessed when you print.
This is not necessarily a failure.
z
You might notice that no matter how thoroughly you exercise the application, some
files are not accessed. This could be because some files are not meant to be
accessed as part of normal functioning. Example: If data files are located in a
Samples directory, they are not opened as part of the normal functioning of the
application.
z
Some errors might appear as a result of the application design. Example: Suppose
that, to maintain backward compatibility, an application is written to check an old
registry location, then check a new location. During testing, the first registry
location might appear as an error. This merely means that the old version of the
application was never installed on the testing computer.
See also:
Extra Files Test Case
on page 190
Extra Registry Entries Test Case
on page 191
