📚 This guide delves into the nuances of project management in Qualitia Automation Studio (QAS), a cornerstone for successful test automation. It provides a step-by-step instruction to create new projects, manage existing ones, and assign users to different projects.
The guide also shares best practices for efficient project management, and provides visual guidance with screenshots, for a more hands-on understanding.
Prerequisites:
You must have administrative access to Qualitia Automation StudioQAS, which grants you the necessary permissions to manage projects.
🔀
...
<Screenshot>
Access Project Management from left navigation of your Qualitia Automation Studio Client
Clicking Project Management will take you to the Project Management screen.
You will the list of all the Projects added to Qualitia Automation Studio <Screenshot>
👁️🗨️ View Project Details
<Screenshot>
Procedural steps
This section covers how to create a new project, view and update an existing project.
👁️🗨️ View Project Details
To view the details of a project:
Login to QAS - Client.
Access Projects from left navigation to view Project Explorer screen, where you view all existing Projects.
Click a Project to view the Project Details.
The details include information such as:
Project Type
Project Name
Description
Integration
Configuration
Note: You will see a segregation of active and inactive projects.
➕ 👥 Create Project
...
<Screenshot>
...
Navigate to the Projects section in your Qualitia Automation Studio.
...
Click Create Project in the Projects section.
...
To create a new project:
Login to QAS - Client.
Access Projects from left navigation to view Project Explorer screen, where you view all existing Projects.
From the Projects section, click Create Project. This opens a Create Project window. Enter the following:
Project Type: Select one of the below project types.
Web/Mobile Project
Desktop Project
Salesforce Project
Project Name: Provide an intuitive name for the project.
Description
...
: A brief description of the project.
The Project Type and Project Name cannot be edited once you create, so be mindful and select the right project type and provide a meaningful name.
Click Create. A Project will be created with users with Admin privileges assigned by default.Discard if you have accidentally clickedSave; otherwise, click Discard.
| Info |
|---|
When a project is created, users with administrative privileges are automatically assigned to it by default. |
| Note |
|---|
For MAC users, desktop projects will neither be visible nor allow any operations to be performed. |
👥 Update Project
<Screenshot>You can update a project the following ways:
Method 1
...
Login to QAS - Client.
Access Projects from left navigation to view Project Explorer screen, where you can view existing projects.
Hover your mouse over a Project in Projects section, to view the Edit Project option will appear.
Click Clicking Edit Project.This will open opens an Edit Project window.
Update the following:
Description: A brief description of the project.
Status checkbox: Uncheck Select the checkbox to make a project Inactive or Check to make the project Active
Click Update. The Project is saved with the edited values.
- Discard if you have accidentally clicked
; otherwise, deselect the checkbox.
Click Save to proceed; otherwise, click Discard.
Method 2
...
Click on the a specific Project to which you want to edit.
This will open the Project Details Section. Click Edit Project (, a pencil )icon.
Follow steps 4 & 5 through 6 mentioned in Method 1.
...
Note: You cannot delete a project when users are assigned to the Project in context.
<include screenshot>
Navigate to the Project Management section in your Qualitia Automation Studio.
Click on a Project in Projects section.
Click Delete Project (bin).
This will open Alert – Delete Project window.
Click
Delete to permanently delete the selected Project
Discard if you have accidentally clicked.
The Project will be deleted in Qualitia Automation Studio.
💡 Golden Nuggets: Best Practices for Project Management
Project Project is a crucial part of project management and organization. Here are some best practices to consider:
Unique: Project names should be unique to each project. This helps to avoid confusion and potential mismanagement.
Avoid Sensitive Information: It's best to avoid using sensitive information such as client names, confidential project details, or strategic plans in project names. This information can be easily viewed and used for malicious purposes.
Easy to Remember: Project names should be easy to remember, but not so straightforward that they reveal sensitive details.
Appropriate Length: A project name that is too short may not provide sufficient information, while one that is too long may be difficult to remember. A good range to consider is between 6 to 14 characters.
Avoid Special Characters and Spaces: Some systems might not support special characters or spaces in project names, or they might create difficulties when integrating with other systems hence prohibited. Underscores are accepted.
Consistent Format: If you're managing a large number of projects, consider using a consistent format for project names. This could be based on project type or department (e.g., Marketing_Project_SEOAutomation or Philips_Project_IOTAutomation), which can make managing and organizing projects easier.
Avoid Offensive Words: Project names should be professional and not include any offensive or inappropriate words.
Review: Regularly review project statuses to maintain progress and prevent delays. Keep project information up-to-date to facilitate communication and collaboration.
Archive vs Delete: If your project is temporarily on hold, consider archiving it instead of deleting. If the project is permanently closed or completed, you can consider deleting it.
🔧 Got Trouble? Let’s Fix!
If you cannot create a project, check your administrative permissions and ensure you have the necessary permissions.
Project page loads depending on project.json file in “QualitiaServer“ folder under ProgramFiles. When you are updating the projects, and if by any chance your system got shutdown, this could corrupt the project.json file. Re-running the Readiness Utility will fix the issue.
📞📚 Here to Help: Support and Resources
Need a helping hand? Don't hesitate to reach out to your Qualitia Relationship Manager. For more resources, our official Qualitia documentation and community website are just a click away!If you have questions that are not addressed in the documentation, you may raise them in the Qualitia Community.