Solution Manager testing modes: Standalone or Integrated?
When working with Solution Manager, you can use both Standalone mode or Integrated mode.
Standalone mode
When you connect to Solution Manager using OpenText Functional Testing, this is known as standalone mode. After you connect to Solution Manager in standalone mode, you can:
-
Store tests in the Solution Manager database.
-
Open existing tests from the Solution Manager database.
-
Upload files to or download files from Solution Manager.
-
Store a test's external resource files in Solution Manager. For example, you can store shared object repository files, data table files, function library files, environment variable files, and recovery files in your Solution Manager database. OpenText Functional Testing provides a special set of Solution Manager-specific options that enable you to control certain elements of the Solution Manager-OpenText Functional Testing integration.
-
Pass values from a Solution Manager test script to a GUI test, or vice versa, using GUI test parameters. For example, if you want to create tests or actions that you can use for different purposes or in different scenarios based on the data supplied to them, you can take advantage of the Automatically parameterize steps using Test Parameters option (in the General node of the GUI Testing tab in the Options dialog box (Tools > Options > GUI Testing tab > General node)). This option instructs OpenText Functional Testing to automatically parameterize all the operation arguments in the steps of one or more actions in your test, at the end of an OpenText Functional Testing recording session. You can then supply the values for these test parameters from Solution Manager.
Integrated mode
When you connect to OpenText Functional Testing from Solution Manager, this is called integrated mode. When you work in integrated mode, only OpenText Functional Testing features related to the Solution Manager test are available in OpenText Functional Testing. When you run tests in integrated mode, your run session results are accessible in the Solution Manager log.
When you log on to a Solution Manager server that is configured to integrate with OpenText Functional Testing, you can view, edit, and run GUI tests that are stored in Solution Manager. You can also use the standard Solution Manager commands to copy, rename, and delete GUI tests, just as you would with any other file stored in Solution Manager.
When you open a GUI test from Solution Manager, OpenText Functional Testing opens in integrated mode. In this mode, you can use all OpenText Functional Testing features that are associated with the open test. However, you cannot save the open test with another name.
You can run a test in integrated mode by using the Run option in OpenText Functional Testing or using the Execute Test Script (F8) option for a selected GUI test in Solution Manager. You can also execute a Solution Manager test script (or blob—Binary Large Object) that calls a GUI test. Creating Solution Manager scripts that call GUI tests is useful if you want to pass or retrieve values to or from a GUI test.
Features available in each mode
The location and features available depend on the mode you use:
Standalone Mode |
Integrated Mode |
|
---|---|---|
Open test from |
OpenText Functional Testing |
Solution Manager |
Solution Manager - OpenText Functional Testing connection |
Connect to Solution Manager from OpenText Functional Testing using the Solution Manager Connection dialog box. |
Solution Manager automatically establishes the Solution Manager - OpenText Functional Testing connection. |
Available OpenText Functional Testing features |
All OpenText Functional Testing features are available. You can open and work with any test in Solution Manager or in the file system. |
You can work only with the currently open test. File > Open, File > New, and the Recent files list options are disabled. If you select File > Save As, OpenText Functional Testing warns you that it will disconnect from Solution Manager and switch OpenText Functional Testing to standalone mode. |
Resource files |
When you open the test, you can also edit and save all the test's resource files, including those stored in Solution Manager. |
When you open the test, test resources stored in Solution Manager are opened in read-only mode. |
Save location |
Tests and uploaded files are automatically saved to the local package ($TMP) in Solution Manager. |
You can save tests to any package (including non-local packages). |
Solution Manager dependence |
Although OpenText Functional Testing is connected to Solution Manager, you can work and navigate in Solution Manager independently. |
Solution Manager is locked while the test is open in OpenText Functional Testing. To release Solution Manager, close OpenText Functional Testing. |
Run results |
All run results are stored in the file system. They cannot be accessed from your Solution Manager log list. |
Run results are stored to the network drive you specify in the Solution Manager pane of the Options dialog box and in the Solution Manager server. You can access the run results from the Solution Manager log. |