...
Import Project: The project from which you want to import the test cases in the current project.
Current Project: The project to which you want to import the test cases.
📚Prerequisites
User should have the QAS client installed.
Projects should have been created.
User should have been assigned to the project.
A test scenario should exist.
🔑Privileges
User should have the below privileges to:
...
Point to Know
After a test case is imported:
If the test case name matches with an existing test case in the current project, the imported test case name is appended with _N, where N is a number that is incremented by 1 if there are multiple test case with the same name.
For example, if a test case called “login” is present in both, the imported and the current project, then after importing the test case, it is named as “login_1” in the current project. If a test case with a name “login_1” already exists in the current project, then it is named as “login_2”, and so on.If an object name matches with an existing object in the current project, the imported object name in the current project is appended with _N, where N is a number that is incremented by 1 if there are multiple tasks with the same name.For example, if a button called "Submit" already exists in the current project, and you import a task that contains a Submit button, then this object is named as Submit_1 in the current project.
If an object with a name “Submit_1” already exists in the current project, then it is named as “Submit_2”, and so on.Similarly, if an environment variable name in the import project matches with an existing environment variable name in the current project, but their value differs. Then, after the test case is imported, the environment variable name is appended with _1.
The imported custom actions along with their parameters are displayed in the Test Case Editor screen. However, you need to manually copy all the external files and codes of the imported custom actions to execute them.
In case of desktop projects, if the TSR file is different for import and current projects, then after importing the tasks the current project updates its TSR file with the additional objects and replaces the existing values for the same objects associated with the imported tasks from the TSR file of import project. Also, when you synchronize the TSR file for any other project that shares the same TSR file with the current project, the TSR file for other project is updated too.
You can use the Search feature to find a task by its name, its associated test case names, and associated test scenario names.
If the imported task contains rest header variable, the rest header should be copied manually from the source project to the target project.
...
Import a Test Case
To import a test case:
Login to QAS - Client.
Access Develop from left navigation to view the Test Explorer screen.
Select the current project for which you want to import the test case from the top menu.
Now, access Import from left navigation to view the Imports screen.
Select the import project from where you want to import the test case using the Project dropdown (below the hamburger menu or the menu with three horizontal lines).
Once the import project is set, select Test Cases.
Under Test Cases, there are three sections.
New: Thetest cases that are part of the import project and are never imported to the current project are listed in this section. These test cases can be imported if required.
Conflicted: If the test cases are imported and later any changes are made to those test cases, either in the import project or the current project, they will appear under the Conflicted section.
Matching: The test cases that are imported without making any changes to the existing test cases, in import as well as the current project, can be viewed under this section. When a test case is imported, it will be directly moved from the New sectionto the Matching section.
To import, select the test case and click Import.
You will see a message Do you want to import Test Case alongwith the options Without Data and With Data. Select Without Data or With Data depending on if you don’t want or if you want to import the test data. Then click Confirm to continue.
After clicking Confirm, a pop-up window will appear with Select Scenario to import Test Case message and a drop-down to select a scenario. Select Scenario and click Confirm to continue.
Once the import is complete click Finish.
You have successfully imported a test case.
You cannot modify any test case in the import module. It is a read-only mode. If you want to edit or modify a test case, you need to go to the develop tab.
If you try adding a step to an imported test case, but then at the same time decide to remove it; though the test case is with no changes, it will appear under the Conflicted section on the Import tab.
Update a Conflicted Test Case
Conflicted test cases are those test cases that were already imported in the current project, but either their steps in the import project or the current project have changed.
After a test case is imported, the test case ids of the task in the import project and the current project are same. Hence, whenever a test case is edited in the import or the current project, the test case is displayed under the Conflicted test cases even if you change its name in the import or the current project.
...
The main pane does not allow you to dry run or make any changes to the test case.
When you import a test case, and make some changes to the task, both the task and the test case will appear under the Conflicted section. Now, when you import the conflicted test case, the test case and the task both will be moved to the Matching section. However, when you import the conflicted task, only the task will be moved to the Matching section and the test case still appears under the Conflicted section.
Import Test Cases in Bulk
You can import either multiple new test cases or multiple conflicted test cases in a single go.
...
All the test cases for bulk import will be imported in the scenario you have selected.
📞📚 Here to Help: Support and Resources
If you have questions that are not addressed in the documentation, you may raise them in the Qualitia Community.
...