...
User should have the following privileges to:
Import FeatureArtifacts: Import test cases or other project elementsartifacts from another projects.
Manage Custom Action Code: Oversee the custom action scripts in projects: Add, edit, delete, and develop custom action.
Manage Objects: Control the objects within the testing environmentAdd, edit, and delete objects.
Manage Scenarios: Control the Add and manage scenarios within test suites.
Synchronize Objects: Keep test objects synchronizedImport and export objects from TSR (Desktop Projects Only).
Test Development: Create, update and update record test cases and task.
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 cases 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 “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 imported project matches an existing environment variable name in the current project, but their values differ, the imported environment variable name will be appended with _1 after the test case is imported.
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 desktop projects, if the TSR file is different for import and current projects, the current project will update its TSR file by adding new objects and replacing existing values for matching objects after importing the tasks. Additionally, 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.
...