Versions Compared

Old Version 3

changes.mady.by.user Shruti Agrawal

Saved on

compared with

New Version Current

changes.mady.by.user Shruti Agrawal

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Import Project: The project from which you want to import the tasks in the current project.

  • Current Project: The project to which you want to import the tasks.

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 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 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 header variable, the 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

📚Prerequisites

  1. User should have the QAS client installed.

  2. Projects should have been created.

  3. User should have been assigned to the project.

  4. A test scenario should exist.

🔑Privileges

User should have the below 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:

  1. Login to QAS - Client.

  2. Access Develop from left navigation to view the Test Explorer screen.

  3. Select the current project for which you want to import the task from the top menu.

  4. Now, access Import from left navigation to view the Imports screen.

  5. 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).

  6. Once the import project is set, select Tasks.

  7. 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.

  8. To import, select the task and click Import.

  9. Once the import is complete click Finish.

  10. You have successfully imported a task.

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

Update a Conflicted Task

Conflicted tasks are those tasks that were already imported in the current project, but either their steps in the import project or the current project have changed.
After a task is imported, the task ids of the task in the import project and the current project are same. Therefore, whenever a task is edited in the import or the current project, the task is displayed under Conflicted 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 task.

Import Tasks in Bulk

You can import either multiple new tasks or multiple conflicted tasks in a single go.

...

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

💡Golden Nuggets: Best Practices for Importing tasks

To cover all the similar testing scenarios, Qualitia recommends the following best practices in the import project before you start importing its tasks:

...