Page Comparison

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. 

...

1. From the Expand Menu, click Project Management.
2. In the left pane. click the Add Project button (  ).

3. 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.
4. Enter a Project Name and a Description.
5. 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. 
6. (Optional) Select the Design Studio Integration checkbox to integrate the project with a Qualitia Design Studio project and perform the following steps.
   
   1. Click Create.
   2. Under Connect with Design Studio
      1. Enter the Qualitia Design Studio URL.
      2. Enter your Qualitia Design Studio Username and Password.
   3. 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:
      1. Issue Types
      2. Issues
      3. Objects
      4. Tasks
      5. Test Cases
   4. Click Finish.
7. 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

You can activate or deactivate the project.

To edit a project:

1. From the Expand Menu, click Project.
2. Select the project that you want to edit.
3. In the main pane, click the Edit Project button ().
   The Edit screen is displayed.
4. Edit the Description as required.
5. If necessary, select or clear the Active checkbox to change the project status.
6. 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. 
7. Click OK to save the changes you made to the project.

Assigning Users to a Project

...

To assign users to a project:

1. From the Expand Menu, click Project.
2. In the left pane, click the appropriate project.
3. Under Assigned Users, click Manage User. 
4. From the User ID drop-down list, select a user. 
5. From the Role drop-down list, select a role for the user. For more information on Roles, refer to Adding a Role. 
6. Click the Plus sign button () to add another user.
7. After you are done adding all the users, click Add.

Removing Users from a Project

...

To remove users from a project:

1. From the Expand Menu, click Project.
2. In the left pane, click the appropriate project.
3. Under Assigned Users, click Manage User. 
4. From the User ID drop-down list, select a user. 
5. From the Role drop-down list, select a role for the user. For more information on Roles, refer to Adding a Role. 
6. Click the Minus sign button () to add another user.
7. After you are done removing all the users, click Add.

Best Practices for Project Backup and Restore

...

1. Save As operation is possible only on local system and cannot be performed across multiple servers.
2. Projects that are enabled for Qualitia Design Studio integration cannot be used as Source or Destination projects when performing Save As operation.
3. Test data conflicts will not be checked.
4. Data changes are not copied if test cases do not have changes.
5. Save As supports copying only development artifacts. Execution artifacts cannot be copied using the Save As project method. You must create suites manually.
6. Test cases cannot be copied without scenarios. Copying a test case copies its associated scenarios as well.
7. 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.
8. 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.
9. Environment variables used within the test data cannot be copied as a part of the Save As process.
10. 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.
11. 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.
12. 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:
      1. Navigate to the Source Project folder on the system.
      2. Copy the environment variables folder having the related XML.
      3. Paste into Target Project location on the system; example, location can be - C:\Qualitia\projectdb_folder\Environment variables.
13. 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. 
14. Based on the version control tool you are using, create new branch or add new folder into the remote repository.
    1. If you are using Apache Subversion, import your new Qualitia project into remote repository following steps mentioned here.
    2. If you are using Bitbucket repository, import your new Qualitia project into remote repository following steps mentioned here.

...