...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
A project is a top-level container that contains artifacts needed for automating the test cases. The artifacts are objects, tasks, test scenarios, and many more.
...
For instructions on how to configure your project settings, refer to Configuring the Project Settings.
Creating a Project
You can create new projects and add users with different roles to them.
| Info |
|---|
Important Notice
|
To create a project:
From the Expand Menu, click Project Management.
In the left pane. click the Add Project button (
).
From the Project Type drop-down list, select one of the following project type:
Web/Mobile Project : To create a project to automate testing for web and mobile applications.
Desktop Project: To create a project to automate testing for desktop applications.
Salesforce Project: To create a project to automate testing on a SFDC application along with its associated web and mobile applications.
Enter a Project Name and a Description.
Perform this step only if you are adding a desktop project and want to map it with a tsr file.
Click the Browse (...) button next to the Global TSR Path, and then locate and select the tsr file.
Unless you map a desktop project with a tsr file, you cannot use OR objects in the project. For more information on OR objects, refer to Working with OR Objects.(Optional) Select the Design Studio Integration checkbox to integrate the project with a Qualitia Design Studio project and perform the following steps.
Click Create.
Under Connect with Design Studio
Enter the Qualitia Design Studio URL.
Enter your Qualitia Design Studio Username and Password.
Expand Sync with Design Studio Project to select an appropriate Qualitia Design Studio Project and click Sync.
The following relevant project artifacts of the Qualitia Design Studio project along with their counts appear:Issue Types
Issues
Objects
Tasks
Test Cases
Click Finish.
Click Create.
After you create a project, you need to assign existing users. For more information, refer to Assigning Users to a Project
Editing a Project
| Info |
|---|
Only administrators can edit the project details that include marking a project as Active or Inactive. You cannot edit the name of a project, but edit its description. |
You can activate or deactivate the project.
To edit a project:
From the Expand Menu, click Project.
Select the project that you want to edit.
In the main pane, click the Edit Project button (
).
The Edit screen is displayed.Edit the Description as required.
If necessary, select or clear the Active checkbox to change the project status.
Perform this step only if you are editing a desktop project and want to map it with a tsr file.
Click the Browse (...) button next to the Global TSR Path, and then locate and select the tsr file.
Unless you map a desktop project with a tsr file, you cannot use OR objects in the project. For more information on OR objects, refer to Working with OR Objects.Click OK to save the changes you made to the project.
Assigning Users to a Project
...
To assign users to a project:
From the Expand Menu, click Project.
In the left pane, click the appropriate project.
Under Assigned Users, click Manage User.
From the User ID drop-down list, select a user.
From the Role drop-down list, select a role for the user. For more information on Roles, refer to Adding a Role.
Click the Plus sign button (
) to add another user.
After you are done adding all the users, click Add.
| Info |
|---|
If this project is connected to a Version Control Management tool, then you have to add the users to the Version Control Management tool too. Otherwise, they cannot access the project. |
Removing Users from a Project
...
To remove users from a project:
...
From the Expand Menu, click Project.
In the left pane, click the appropriate project.
Under Assigned Users, click Manage User.
...
From the User ID drop-down list, select a user.
...
From the Role drop-down list, select a role for the user. For more information on Roles, refer to Adding a Role.
Select the checkbox present in front of the user you want to remove. You can select multiple users at a time.
Click the Cross sign button (
) to
...
remove the user.
Best Practices for Project Backup and Restore
...
Following is the list of some important points to be considered before you perform Save As operation for projects.
Save As operation is possible only on local system and cannot be performed across multiple servers.
Projects that are enabled for Qualitia Design Studio integration cannot be used as Source or Destination projects when performing Save As operation.
Test data conflicts will not be checked.
Data changes are not copied if test cases do not have changes.
Save As supports copying only development artifacts. Execution artifacts cannot be copied using the Save As project method. You must create suites manually.
Test cases cannot be copied without scenarios. Copying a test case copies its associated scenarios as well.
Make sure you copy the custom actions from the source project to the target project before performing any Save As project operation.
In case your target project does not have custom actions imported, you may refer to the Importing Existing Custom Actions into Qualitia section.Save As operation on custom actions does not work on parameter name differences. A check is performed on the action name, parameter count, function name, and Qualitia class.
Environment variables used within the test data cannot be copied as a part of the Save As process.
The custom action files from the source project do not move automatically to the target project. You need to manually move the dependent jars and Custom Action Function code associated with the Custom Actions (keywords) that were selected during Save As process.
Custom action code is not copied as a part of Save As operation. It is expected that you check-in the code into the version control system so that it is available to all other users. Other users need to ensure that the code for custom actions is checked out on to the local system and the appropriate path for custom actions is specified in the .config file.
To ensure that the Target Project can use environment variables, use the following steps:
If the Target Project is new (there are no environment variables by default), do the following:
Navigate to the Source Project folder on the system.
Copy the environment variables folder having the related XML.
Paste into Target Project location on the system; example, location can be - C:\Qualitia\projectdb_folder\Environment variables.
If the Target Project already exists and has some environment variables, do the following:
Open the EnvironmentVariables.xml in the Source Project and Target Project folders.
Append the Target Project EnvironmentVariables.xml file manually with the environment variables from Source Project.
Based on the version control tool you are using, create new branch or add new folder into the remote repository.
Additional Points for Desktop Projects
You cannot use SaveAs feature for moving project artifacts from a desktop project to a web/mobile project and vice-versa.
There must be more than two desktop projects.
You must perform the SaveAs feature process in the following sequence:
Create a blank target project without mapping it to a tsr file.
Perform the Save As operation from the source project.
After the Save As operation completes, map the tsr fie path of the source project to the target project.
If you map a tsr file with the Target project before performing the Save As operation on the source project, then except for the custom actions, the other test artefacts are not imported.
Copying Qualitia Project
The key features of Save As are mentioned below:
...
To Save As on a blank project:
From the Expand Menu, click Project Management.
In the left pane, click the source project.
In the main pane, click the Save As button (
).
The following confirmation message prompts that none of users are working on the source project.
...
Click one of the the following buttons:
OK: To continue the saving project as process after ensuring that none of the users are working on the source project.
Cancel: To stop the saving project as process.
The Save As dialog box opens.
You can perform save as operation on the selected artifact type by using the filters available as shown in the following figure:
...
Do in the following order listed:
From the Target Project drop-down list, select a target project to which you want to copy the artifacts.
From the Change Status drop-down list, select one of the following options:
All: To select all the artifacts.
Never Moved: To select only those artifacts that were never copied to the selected target project.
Already Moved: To select only those artifacts that were already copied to the selected target project.
Changed and Moved: To select only those artifacts that after copying to the selected target project were edited in the source project.
Artifacts: You can select test case, independent task, or custom action.
After applying the filters, click Go.
Info If you select test case, the left pane in the dialog box shows test cases under their scenarios. When a test case is copied to the target project, the associated tasks are also copied.
Do in the following order listed:
Expand the left hand side tree to view the artifacts.
You can click a test case node to view the associated tasks on the main pane.
You can click a task node to view the status of associated objects and actions.
Click the Preview button to open the Save As Preview Report and view its results.
...
Do in the following order listed:
Expand the left hand side tree to view the artifacts.
You can click a test case node to view the associated tasks on the main pane.
You can click a task node to view the status of associated objects and actions.
The following icons denote:
denotes that the artifact can be copied.
denotes that the artifact cannot be copied as its xml file is missing in the source project.
denotes that the artifact is already copied to the target project.
Click Confirm & Move to complete the operation.
An information message appears to indicate if the operation was successful.Click Yes to export the report to a spreadsheet.
If Save As operation has found artifacts which are already existing or conflicting with the target project, then the message changes. You can export the report to a spreadsheet clicking Yes.
The spreadsheet report is displayed. You can store the report at any desired location.
Saving to an Existing Project
...
The roll-up effect of conflicts is seen when a conflict exists in an artifact which is used within test cases or tasks. In such cases, the test cases or tasks will also be set with a conflict status.
The following are the conditions of roll-up conflict situations:
An object or action has conflicts but the tasks and test cases using them have no conflicts - the tasks and test cases using the task with conflicting object or action will be displayed with a conflict status.
Note: All other tasks within the test case which have passed will appear with a success status.A task has conflicts along with the test cases using them - a task used within a test case(s) has conflicts, and then all test cases using the task will display a conflict status.
A task has conflicts but the objects/actions used within the task have no conflicts - a task has conflicts on task name, then the task will show conflicts, and objects and actions will not be displayed.
A test case has conflicts but the tasks, objects/actions used within the task have no conflicts - a test case has conflicts on test case name, then the test case will show conflicts, and tasks, objects, and actions will not be displayed.