Copado vs. Tricentis qTest

Very well suited if there are 3+ developers in the team. Very easy to maintain individual sandboxes and connect it to the pipeline. With just few clicks, it will create its git branches on its own and syncs with the sandboxes. Very helpful and time saving. might be expensive for small teams

Incentivized

Tricentis qTest integrates seamlessly with Jira, making it ideal for teams that manage user stories and defects in Jira while keeping test cases and execution in qTest. When paired with automation tools like tosca, Selenium, or WebdriverIO, qTest is excellent for aggregating both manual and automated test results in one place.

Incentivized

• Metadata Deployments
• Data Deployments
• Salesforce CPQ deployments that require a lot of various Data
• Transferring deployments between teams.

Incentivized

• As a fresher, when I started using qTest it was very handy and easy to understand.
• It helps us trace the test cases that are used to test the quality in a single location
• The main thing is its integration with JIRA as soon as we create a ticket we would be getting all the requirements in the qTest so it became easy for me

• For data migration, they can increase the limitations
• The table of components in the build section can be improved
• Hard to understand how to destructive changes. Sometimes facing issued after deleting the field or component that need to be deleted with destructive changes

Incentivized

• Make it easier to delete old users from the licensing list.
• It is difficult to trace the history of a test when going between projects.
• Allow an admin to easily group tests according to their pass/fail/incomplete status so that they can be followed up on.

Incentivized

This has been a core QA management tool for our organization and integrates well with our other SDLC platforms (Azure DevOps/Jira/Katalon).

Incentivized

very good user interface. It has reduced tons of manual efforts for the developers. Very easy to validate the release work. Easy to club multiple stories into one deployment. We can integrate Copado with our JIRA and all the PR’s are visible under the user story on JIRA board. But this can be overwhelming for beginners

Incentivized

qTest is actually intuitive and user-friendly, despite my other scathing review aspects

Incentivized

The actual answer is 0. I have never experienced worse support, whether personal or professional

Incentivized

Again, supporting documentation could have been a lot better

Incentivized

There are tools such as ANT migration tool or using sfdx but Copado makes the deployments super simple. If a user is not that technically strong still he can use Copado and deploy the changes in a few clicks. Copado provides a complete package of maintaining the development and repositories in a common platform. There are pipelines that you can set that changes will move from which org to the final org in a very organized manner. We can perform static code analysis at the time of deployment of the changes and we have to clear those if we need to deploy the changes. Creating pull requests is super easy and can be managed by Copado itself. Overall a superb managed package for deployment in Salesforce.

Incentivized

All of them offer formidable solutions in the test management realm, but each one caters to different niche and need. qTest distinguishes itself with its deep integration capabilities, especially with Agile and DevOps tools, enabling streamlined CI/CD process. Its modern, user-centric interface contrasts with ALM's more dated appearance and complex setup. While TestRail provides a clean user experience and caters to a broad spectrum of business, qTest's scalability, from SMBs to large enterprises, stands out. PractiTest's cloud-based solution is geared towards mid-sized companies, but qTest's flexibility, advanced analytics, and robust reporting grant teams actionable insights. qTest' approach to a more holistic test management closely aligning with modern software development practices

Incentivized

• It has reduced the efforts to create package.xml manually and deploy the changes
• Another positive impact is that we can track the commits to which org they have reached in an organized way and we don't need to maintain them separately
• For setting Copado it take a lot of time and training is required for the complete setup which is time-consuming

Incentivized

• Test case and requirements analysis becomes easier when you will get all test management needs in one place.
• connecting ADO,QTEST,TOSCA together helps to monitor test results and test quality on the GO
• Defect life-cycle is easier to maintain so as to ensuring a defect free system.

Incentivized