📚 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 instructions to create new projects, manage existing ones, and assign users to different projects.
...
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 status 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.
...
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.
Getting error "Early EOF" while project setup after replacing the server workspace: You might get this error while project setup if the credentials through which the VM was logged-in is different from which the Web Services were started. To avoid getting this error you have to make sure that the same log in credential is used for VM as well as web services.
Now to To fix this error, update the log-on Log On configurations of web-service with appropriate localadmin user following the below steps:Open services and go to qualitia-web-service.
Rightclick Right click on qualitia-web-service and open Properties.
Once the Properties window is open, go to Log On screen and add credentials after selecting the button next to This account.
Click Apply to save the changes.
Now go to C:\Users\{username}\AppData\Local\Qualitia Automation Studio - Client\workspace\projects and open git.
Insert the command git clone "http://IP:8887/qas-repositories/projectname".Use your machine's IP address and project name in place of “IP“ and “projectname” in the link.
Open Services and restart qualitia-web-service.
Once the project gets cloned then close the folder and open Qualitia - Client to setup the project.
After completing the Qualitia installation and license key deployment, an error may occur when loading a project in the Project tab. This issue has been observed under specific conditions.
Pre-conditions that may lead to this issue:
The server and client were installed on the same machine, which is not recommended for customer environments.
The machine was configured so that even the user profile folders were owned by the admin user, which appears to be a specific configuration on the server machine in the customer's organization.
Resolution: This issue is tied to the specific setup of the machine, and a general fix cannot be provided as the configuration is controlled by the customer. To avoid this issue, ensure the following:
Install the server and client on separate machines.
Ensure that user profiles and folders are not restricted to admin-only access.
Following these recommendations should prevent the issue from occurring.
📞📚 Here to Help: Support and Resources
...