Page Comparison

...

Info

Points To Know

You cannot import tasks from a web/mobile project to a desktop project and vice-versa.
After a task is imported:
- If the task name matches with an existing task in the current project, the imported task name 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 task called “login” is present in both, the imported and the current project, then after importing the task, it is named as “login_1” in the current project. If a task 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"alr eady exists in the current project, and you import a task that contains a Submit a Submit button, then this object is named as Submit“Submit_1 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 task 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.
If the imported task contains rest a REST header variable, the rest REST header should be copied manually from the source project to the target project.
You can use the Search feature to find a task by its name, its associated test case names, and associated test scenario names.
QAS stores the import details in a text file called Import.Log at the following location:
%localAppData%\Qualitia\WD\Logs

...

🔑Privileges

User should have the below following privileges to:

Import Feature: Import test case/task or other project elements.
Manage Custom Action Code: Oversee the custom action scripts in projects.
Manage Objects: Control the objects within the testing environment.
Manage Scenarios: Control the scenarios within test suites.
Synchronize Objects: Keep test objects synchronized.
Test Development: Create and update test cases.

Import a Task

To import a task:

Login Log in 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 task from the top menu.
Now, access Import from the left navigation to view the Imports screen.
Select the import project from where you want to import the task using the Project dropdown (below the hamburger menu or the menu with three horizontal lines).
Once the import project is set, select Tasks.
Under Tasks, there are three sections.
1. New: Thetasks that are part of the import project and are never imported to the current project are listed in this section. These tasks can be imported if required.
2. Conflicted: If the tasks are imported and later any changes are made to those tasks, either in the import project or the current project, they will appear under the Conflicted section.
3. Matching: The tasks that are imported without making any changes to the existing tasks, in import as well as the current project, can be viewed under this section. When a task is imported, it will be directly moved from the New sectionto the Matching section.
To import, select the task and click Import.
Once the import is complete, click Finish.
You have successfully imported a task.

You cannot modify any task in the import module. It , as it is in a read-only mode. If you want to edit or modify a task, you need to go to the develop tab.

...

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 task from the top menu.
Now, access Import from left navigation to view the Imports screen.
A list of tasks under New, Conflicted, and Matching is displayed.
Under Conflicted, click the task that you want to import.
Both the imported task and the current task opens open in the main pane.
You can know the differences between these two tasks in the following ways:
1. Steps marked in red color and red icon indicate that they will be removed from the current task after the task is imported.
2. Steps marked in green color and green icon indicate that they will be added to the current task after the task is imported.
3. Objects, custom actions, and parameters marked in red color indicate that their values are different, which will be replaced after the task is imported.
4. Steps marked in with a minus sign indicate that parameter values are different, which will be replaced after the task is imported.
In the left pane, you can see the Current Task and in the right Imported Task.
Compare the changes and click Import from the top-right corner if you want to import the updated task.
Clicking Import will open an Import Task pop-up window. Click Confirm to continue; otherwise, Discard.

...

All the tasks for bulk import will be imported in into the scenario you have selected.

...

Versions Compared

Old Version 3

New Version Current

Key

🔑Privileges

Import a Task