Importing Test Suites

Administrators can use the Test Suite Importer window... to import the contents of a Test Suite into the Test Libraries on the TAS. The Test Suite can be imported into any library section that permits imports; linked test cases are imported into the Test Case Library, test sessions are imported into the Test Session library, and so on. If you choose to import into a protected section, the test cases are imported into the Extended section and the test sessions are imported into the Global section. You have the option to change the names of imported elements to avoid overwriting existing library elements.

IMPORTANT:

Only ONE import is allowed to occur at any given time. Multiple users must wait for current import to finish before they can import.
The definitions for system-related parameters — test servers and IP addresses — are cleared in all test cases contained in the imported Test Suite, and must be re-defined with resources available in the current test system. When you open an imported test session, the test cases must be repaired before the session can be executed.
The GUI Test Suite Importer has a built-in Timeout period to prevent users from leaving the window open and blocking API users. Once the Import process has started (viewing/reviewing STE contents), the GUI will require a user to Execute the IMPORT within X Seconds or else it will be automatically unlocked. The GUI Auto-Unlock will default to 5 minute (300s) timeout, and this value can be controlled by the TAS-Setting gui_import_timeout_s to 1 to 65535 seconds. The Progress bar will indicate how much time is left in 5s increments, when there is 90s (or less) remaining. Setting gui_import_timeout_s to 0 (zero) will disable this feature. Added "waitTimeS" to RESTful API query argument to define how long to wait for the Test Suite Importer to unlock before getting an error response. The Default/Configured Wait Timer for RESTful API imports on the TAS is 5 seconds by default, the TAS-Setting import_lock_timeout_s can be used to update this to another value. Using the RESTFul API contains reference information about the Landslide RESTFul API system. Refer to Swagger UI on Landslide Home Page, it contains the latest most accurate information for anything it covers.
Only official signed Test suites can be imported, otherwise you will get this error " Official Test Suite is not signed".

To import a Test Suite:

Select Admin > Test Suite Importer from the Main menu.
Click Browse and the Select Test Suite window opens.
Browse to the Test Suite file and click Select. The Test Suite is uploaded to the TAS. The name and contents of the suite and a Target Library drop-down list are displayed in the Test Suite Importer window. As of release 17.5 a new field has been added "Root Test Cases Only" that if checked, only the Root Test Cases will be replaced, all others will be skipped. If Root Test Cases Only is unchecked, all items, including DMFs, VSAs/AVPs and Root Test Cases will be replaced. See Test Suite Importer window... for example.

Select a library from the Target Library dropdown list.

NOTES:

A Test Suite that contains library elements supplied with the test system can only be imported into the Basic section of the library. When this type of Test Suite is being imported, you cannot choose the Target Library.
You can only import a test case, and any test sessions that use it, if the test case's template resides in your Basic Test Case Library.
A Data Message Flow can only be imported if your test system is licensed for the data protocol that it uses.
Links to elements, DMFs and Test Data Files used by a test case for example, are adjusted when the Test Suite is imported. If a DMF was housed in the Global section of the library in the source test system and then imported into a user section on the target system, the test case will look for the DMF in the user section, not the Global section.

Select to : Maintain Test Server IDs (Select to maintain Test Server IDs or do not select to clear them), Clear TestNodes (Select to clear them - Notes below), Include SUTs (select to include SUTs or do not select to and they will be skipped), Clear SUT Parameters (select to clear the SUT parameters), Use Matching SUTs (select and if the TAS finds a SUT in your TAS with the same IP Address, instead of creating a new SUT it will just point imported items to the existing SUT in the system ).

NOTES:

Clear TestNodes only applies when the test doesn't Override Port-Subnets as part of Reserving Ports).
When selecting Clear TestNodes , you will lose any PortCapture configurations.

The Action column displays the end result of an import on the Target Library: the element will either be added to the library, or it will replace an existing element with the same name. If you wish to retain existing elements that would be replaced, you can add a prefix or suffix to each imported element's name with the Change button. When you click the button, you can choose the renaming method (None, Prefixed, or Suffixed) and specify the text that will be added to the imported item's name. Select None to remove the name adjustment after it was enabled. In the example shown, " - v 2.0" would be appended to every element name.

NOTES:

A maximum of 10 characters can be used in the prefix/suffix string. Numbers, letters, and underscores (_) are valid characters.
If the resulting element name exceeds the allowed number of characters for an element name, the original name is truncated as needed.
The import Action always shows the result of an import using the current settings including any name adjustments.

When the import is complete, a confirmation message is displayed that lists the elements imported and the library to which each element was added.