Copado vs. Tricentis Tosca

When we have a large organization and number of changes and deployments are more than we should go for Copado. As we know it is a paid managed package and the cost is high so for dealing with fewer deployments it is not preferable to buy. Copado is well suited for users who don't have much technical understanding. So those users can see the User interface select the changes that need to be deployed by selecting the metadata. From Git operation to deployment all is handled by Copado itself. Copado has reduced the efforts for creating the package.xml and direct deployments can be done within a few clicks. Another Major aspect is that it can be directly synced with Jira or Azzure board from where the user stories will be synced and actions can be performed accordingly. For small organization, Copado can be expensive and to set up and maintain we need a technical person to do so.

Incentivized

Tricentis Tosca is well suited for packaged applications like SAP, Salesforce, Workday, etc. It also works well with API testing and Web UI testing. Tosca is highly suited for Projects which require a high level of collaboration between team members across different locations. It's less suited for mobile automation, Reporting, and test scenarios with high input data.

Incentivized

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

Incentivized

• It's one stop shop for all your test automation needs like - api layer, ui layer, load testing, mobile automation.
• It has excellent support for CI/CD and Devops environment which makes it very modern but much needed solution
• It can run in cross browser and cross devices with same test script and again saves a lot of time.
• Excellent results and dashboards gives nice view into results.

Incentivized

• Back promotions are sometimes difficult and behave in a weird manner
• After the deployment to production next changes in the pull request shows all the changes from the previous release as well
• Cannot be used through mobile

Incentivized

• It does have a steep learning curve, A tool is often perceived capable of doing only what its user is able to achieve in accomplishing while using it. For this reason, its very necessary if for the team at Tricentis to continue doing the great work they are doing to train early adopters of this fantastic tool.

Incentivized

We aim to renew Tosca for our organization. What we lose in license cost is gained by having employee that do not need programming background. We also recoup a lot of the cost on the rapidity of automation. Only the support we might not use as much. I believe Tosca is here to stay at our organization

Incentivized

It can be a challenge for new users who have never used an automation tool. For example, it is hard to understand the layout of the screen and where to find how to update the data. The interface can be overwhelming at first.

Incentivized

Tricentis team was very supportive. Support is expensive but they helped us at many level. Setting up timeline, implementation, precise questions on automation challenges. We had an account manager and technical people we could as to talk to. Support was generally timely and helping. They often proposed to come on site to help us which would cost more but could be helpful

Incentivized

Flosum is a downgrade for sure and I do not recommend it. Gearset is an upgrade and my preferred solution. Gearset has simplified the deployment path and makes it very easy to move between Salesforce instances. If there are any difficulties with Gearset they also have the best customer support for any deployment tool I've tried. Overall I'd say Gearset is #1, Copado #2 and Flosum a distant #3.

Incentivized

Tricentis Tosca is codeless and therefore easier to use. It's a great tool for people that would start doing automation and have no coding background. It seems like it has the same capabilities as other test automation suites but I felt it lacked a bit of capabilities on the test management suite such as defects test suites organizations etc

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

• After implementing Tosca we were able to reduce the cycle time that was spent on executing regression tests manually. I would say TOSCA was able to reduce close to 30% of the time that was spent for executing test cases manually.

Incentivized