Page Comparison

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.

  • If the imported task contains rest header variable, the rest header should be copied manually from the source project to the target project.

• 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. 
• QAS stores the import details in a text file called Import.Log at the following location:
  
  %localAppData%\Qualitia\WD\Logs