When remotely executing a test, are local or remote test assets used?

Document ID : KB000048527
Last Modified Date : 14/02/2018
Show Technical Document Details

When executing a test case, it's important to know where LISA is accessing the various test assets. Some assets are accessed from the local machine where LISA Workstation is running, and others are accessed from the remote machine hosting LISA Server. Knowing where LISA is accessing a file during the staging process is critical when the local and remote machines contain different versions of the same assets.

Where certain assets are accessed from depends upon how the test is staged.

Tests staged locally from LISA Workstation

These assets from the local machine are used:

  • Test Cases (*.tst files)
  • Staging Documents (*.stg files)
  • Configuration files (*.config files)
  • Subprocesses
  • Data sets

These assets from the remote machine are used:

  • None

Tests staged remotely from LISA Workstation

These assets from the local machine are used:

  • Test Cases (*.tst files)
  • Staging Documents (*.stg files)
  • Configuration files (*.config files)

These assets from the remote machine are used:

  • Subprocesses
  • Data sets

Suites staged remotely from LISA Workstation

These assets from the local machine are used:

  • Suite Document (*.ste files)

These assets from the remote machine are used:

  • Test Cases (*.tst files)
  • Staging Documents (*.stg files)
  • Configuration files (*.config files)
  • Subprocesses
  • Data sets

Tests and Suites scheduled with CVS

These assets from the local machine are used:

  • None

These assets from the remote machine are used:

  • Suite Documents - if applicable (*.ste files)
  • Test Cases (*.tst files)
  • Staging Documents (*.stg files)
  • Configuration files (*.config files)
  • Subprocesses
  • Data sets


Figure 1