What advice do you have for others considering Tricentis Tosca?

I rate the overall product a seven out of ten.

From an environmental standpoint, we’ve noticed that some existing scripts stop working whenever a new upgrade or patch is applied. This leads to a time-consuming process of identifying the root cause. We eventually realized that after upgrading the task coverage, the scripts failed because they could no longer identify certain objects or elements. The issue arises without clear information on why the identification failed. The application would launch as usual from a specific location, but the scripts suddenly stopped working after the modules were changed or updated. Overall, I rate the solution as five out of ten since I face challenges with the environment setup, user management, and other aspects.

I rate the platform an eight out of ten.

In terms of what has significantly improved test automation in Tricentis Tosca, I would say that it is traceability. In Tosca, we can trace the user cases and all the test cases to any extent. We can measure test coverage. From the user-front, it is easy to work with the tool. Speaking about how the risk-based testing approach of Tosca impacts our clients' testing outcomes, I would say that when we start working on a client, we do some assessments to understand the maturity level of the client based on the past. Also, we work and provide some demo specials, show the features the tool has, and then provide some solutions. Tosca is not very good for test management. Tricentis has some other tools, like qTest, which is a good option. I recommend the tool to others. I rate the tool a ten out of ten.

I rate the overall product a nine out of ten.

Tricentis Tosca offers robust support for risk-based testing through its model-based testing approach. This methodology includes a risk analysis component that helps cover various test scenarios, including combinatorial testing and CVD, thus ensuring comprehensive test coverage. While the impact on testing processes might not be significant regarding productivity, Tosca's scriptless nature streamlines test case automation and maintenance, making it accessible to functional analysts without scripting expertise. Additionally, it integrates with test data management tools, such as CA Test Data Manager (TDM), to ensure updated and relevant data availability for test case execution. Regarding recommendation, it is well-suited for legacy or packaged applications but may not be optimal for web-driven projects where Selenium offers superior functionality. However, considering Tosca's roadmap, which heavily aligns with SAP and other packaged applications, it remains a preferable option for enterprises with diverse testing requirements. I rate it a seven.

Speaking about the feature of the product that has the largest impact on our company's testing process, I would say that I use Selenium to take care of the coding part. In Tricentis Tosca, we can't use Git code, considering the user-based experience and UI for the testing process. Speaking about the codeless test creation feature in Tricentis Tosca, I would say that in some of the software where the quality assurance team does the verification, Selenium is used by quality analysts. In Selenium, we used to write the codes to check basic stuff. In Tricentis Tosca, we don't have to write any scripts. Integrating the product into my company's CI/CD pipeline affected the release cycles in a good way. For beginners, the product is good, especially for those who are interested in the quality side of software testing. Considering the emerging trends in the automation space, I would say that Tricentis Tosca is a good software. I rate the tool a seven and a half out of ten.

Test data management capabilities are very proprietary and very specific. We have to compare the test data anyhow. In the end, we consolidated the two solutions. One was the open-source solution for test automation, and the other was for specific protocols. We decided to have only two types of solutions. Integrating with Jenkins or Jira requires some setup and configuration, and achieving compatibility with our existing systems, including Jenkins and our test governance processes, hasn't been straightforward. As of now, we haven't achieved a fully integrated solution. Overall, I rate the solution a seven out of ten.

Overall, I rate the solution an eight out of ten.

It is recommended to start with training sessions to understand how to use the tool effectively. Pricing might vary based on your organization's specific needs and requirements, so exploring the pricing options is advised. I rate the product a nine out of ten.

Cost is a significant factor. Tosca has strong features that may not be suitable for every product or project. Tosca should provide a free community learning platform for individuals to explore Tosca before making a purchasing decision. Tosca is primarily focused on SAP environments. SAP is a player in the IT landscape. Tosca's scope extends beyond just SAP to address various testing needs across different domains within IT. Tosca has strong integration with SAP systems. Tosca is a comprehensive test automation tool that caters to various domains, including medical, fintech, e-commerce, B2B, B2C, communication applications, and other role-based applications. Tosca can also be applied to automate testing across a wide range of IT industry sectors. It's a well-known tool in the market for its versatility and effectiveness in test automation beyond the SAP ecosystem. We are working with the MBT approach. Tosca is compatible with SDET practices, and its main purpose is achieved through model-based test automation. Tricentis Tosca offers built-in libraries for integration purposes, allowing users to implement various integrations seamlessly. Test cases can be executed by configuring AWS, Azure, or DFS integrations. These integrations are built-in and provide capabilities that enhance convenience and flexibility. Tosca is a robust and competent solution, leveraging cutting-edge technologies to capture locators, record test cases, and execute actions across various UI platforms. It is compatible with the latest technologies like TypeScript, JavaScript, Angular, and other user interface platforms. I highly recommend this solution for those who are considering purchasing it Overall, I rate the solution an eight out of ten.

I rate Tricentis Tosca an eight out of ten.

So, if you need to accelerate the delivery of your solution and leverage the low-code, no-code platform, that's where you can actually bring in quite a lot of automation with the region type in Tricentis Tosca. Maintaining your test scenarios, running them immediately to create mind maps, and then using new-generation tools like xMine to integrate with Tricentis Tosca can significantly reduce the testing cycle time from a typical 20-35% of the software engineering cycle to as low as 10%. This can significantly improve the turnaround time for decision-making. I would rate it a seven out of ten. There are lots of alternatives that are available at a good price point. So when you are working with large customers who have big budgets, bigger budgets, certain places are something that they are going to take up. When they are working with medium-sized customers, potentially, the signatures could actually address that.

For maintenance, only one person who is an admin is required. The solution's features are good. I think whoever wants to use it should understand the tool's capabilities first before taking a dive so they can try a PoC with the tool and then go ahead to use it. I rate the product a seven out of ten.

I would rate the overall product a seven out of ten. The tool is easy if you are able to find the right set of people.

I give Tricentis Tosca an eight out of ten. We have up to 80 people using the solution. I highly recommend Tricentis Tosca to others due to its extensive support for numerous technologies and platforms, making it a valuable tool.

Tricentis Tosca does not provide much support for reports and mobile automation. The speed of execution of mobile automation is low. Also, test case creation and the creation of models take a lot of time in the mobile engine. Overall, I would rate Tricentis Tosca at eight on a scale from one to ten with one being the worst and ten being the best.

I rate this solution eight out of 10.

Our company is partnered with Tricentis. We're using the latest version of the solution. I'd recommend the solution to others. It's user-friendly, easy to learn, and doesn't require any coding. New users, however, must take some lessons before starting with it. Most of the time, they might have colleagues to transfer knowledge and that makes things simpler. Still, it's really easy. I would rate the solution eight out of ten.

I would recommend this solution to others because it's stable, and you can test a lot with it. It has a good user interface for testing and when managing you don't have to do a record all the time. It can be easy to maintain and use scripts. We use the client to receive the package, and it takes a lot of time to upgrade the package. We only switch to the next version after two years. I rate Tricentis Tosca an eight out of ten.

I rate Tricentis Tosca a nine out of ten.

My company is using Tricentis Tosca and is an end-user of the solution. With the Tricentis Tosca installation that my company has, one person is enough for maintenance. My advice to others looking into implementing Tricentis Tosca is to limit it. I would use it only for specific test automation requirements, and I wouldn't use it for other purposes because it's a very expensive solution. My rating for Tricentis Tosca is seven out of ten.

I rate Tricentis Tosca nine out of 10. The tool has multiple features, and it covers a variety of applications, It's accessible, so anyone can use it even if they're not a technical person. But if you have some programming knowledge, you can create your own customized functions and automate any Windows application. Integration is straightforward, and test management tools are also available. A person can get an ES1 and ES2 certification by viewing a video tutorial before starting the actual scripting. They complete the certification work with any demo application to learn how to scan the objects, execute test cases. Tricentis supports 95 percent of applications, and it covers a broad range of areas, like DB, ETL, and website automation.

When reviewing the tool, you should make sure that any automation you've already got integrates fully with the Tosca tool. That's the biggest thing. Migration of any current automation is potentially a really difficult process. I'd give it an eight out of ten.

Tricentis Tosca is a testing tool, so we can implement it in any software projects. The tool is only applicable for on-premises deployment. Currently, it's not possible to deploy it via public or private cloud. I'm using version 15 of Tricentis Tosca. I did the deployment of the tool myself, and didn't use an integrator, reseller, or consultant. One person can deploy Tricentis Tosca. We have 1000+ people in our environment who are using the tool. Product-wise, I'm rating Tricentis Tosca eight out of ten. Service or support-wise, my rating for it is six out of ten.

From experience from using UFT, if they just compare UFT to Tricentis Tosca, I think Tricentis Tosca is a great tool compared to any other tool I have experienced. UFT is much more heavy compared to Tricentis Tosca which is lightweight and easy to learn and to work with. The stability of the Tricentis Tosca application is great. There is no scripting required in Tricentis Tosca as there is in UFT. However, there is more web scripting. You can do scripting separately and if you're going for a commercial tool Tricentis Tosca is the one to choose. I rate Tricentis Tosca an eight out of ten.

I did some certifications on Tosca. I tried to do some POCs as well. I'm using the latest version of the solution, which may be 3.2 or 3.5. I would advise new users to not go with writing the test cases manually. Try to start automating directly in Tosca, as that would help to save time. If you write manual test cases as well and then we try to automate to Tosca, it takes a lot of time. It's better to jump in right away with the automation-first mindset approach and start writing in Tosca so that you could use it in every execution cycle. On top of that, if you have a different cycle for business users to do the testing or they are testing at the user acceptance testing, you can give them the test use for Tosca as well. It's pretty easy to use, straightforward and it would save time. I would rate the solution at a seven out of ten.

I would recommend this solution to others, but in our country, I believe the importance of testing is currently ignored or underestimated. It is not popular in our country at this moment but I will recommend this tool. We are partners with Tricentis. I would rate Tricentis Tosca an eight out of ten.

The academy on user interface and the API introduction I found very useful. It has helped me understand some of the features available. I rate Tricentis Tosca an eight out of ten.

If the teams are implementing and they are doing agile development and want to stay on track with their agile deliveries, the automated testing goes hand in hand. Tosca can be an excellent enabler for you to be able to do the testing at a much faster pace than if you were trying to do that with other manual testing and that does not slow you down. It works very well if the organization is trying to move toward a more agile approach, and the ability to do automated testing lends itself very well to it. I would rate Tricentis Tosca a nine out of ten. It's pretty good.

I rate Tosca nine out of 10. So if you are considering this solution, I recommend that you make sure your team is good and stable in test definition. Also, you should build up your organization's competence in test automation. That way, you can get the most out of the tool and utilize its capabilities to benefit your organization. But there are challenges with a large organization internally. For example, we first had a central team for test automation. Then we moved to HL and de-centralized our test automation team. Unfortunately, that didn't work so well since it requires some specialized knowledge that you need to learn and to practice. So now we are trying to move again to centralized test automation and get more value for the business.

My advice is if companies have developers, or the potential to teach developers, or QA teams, I would suggest they use Selenium because the price of Tricentis Tosca is expensive. I rate Tricentis Tosca an eight out of ten.

We did not fully utilize its integration with the test management tool, but it was working fine. My recommendation would be to go through Tricentis documentation and the best practices that they are proposing. Wherever required, set up a knowledge-sharing session with Tricentis.

The recommendation of this solution depends from client to client and what their requirements would be, the parameters, and what is important to them. If the client wants good support and at the same time they want to have a good database included with the Automation Testing Suite, and is ready to spend the money, then we would definitely suggest Tricenta Tosca as a good option. Again, it is dependant on the client's requirements and what they would want in an automation tool. If you have Linux or Mac machines, then it gets very difficult to implement Tosca. I would suggest using it. For testing, they would want to migrate miscellaneous scripts and use Tosca for those migrations. But, it's very difficult. My suggestion would be to go with the Tricentis Suites and the Selenium Automation Suites. From a positive perspective, I would want people to use the reporting from Tosca. They have very good reporting. The reporting feature is very user-friendly and very easy to use. I would rate Tricenta Tosca an eight out of ten.

The biggest lesson that I have learned from using Tricentis Tosca is that for test automation, you are not required to be a programmer or very technical. Overall, this is a good product and I definitely recommend it. I would rate this solution an eight out of ten.

Overall, the product works fine. With respect to errors in the product, there is nothing in particular that comes to mind. If there were issues then I was always able to work my way around them. I would rate this solution an eight out of ten.

I would definitely recommend this product to my colleagues or my friends because it is very useful if they are using the Tosca Query Language (TQL). We can find exact data from any project, which is one of the best benefits. It is a very easy, convenient product for everyone. Tricentis Tosca is very easy to understand. We can reuse data, and no redundant data is required. I like this tool. I am also interested in self-learning this tool and its features. I would rate Tricentis Tosca an eight out of ten. It's very good performance-wise.

My advice for anybody who is implementing this product is to make use of the extensive library that they have. It is a good collection of training videos and documentation, and I would advise everybody to go through these materials. They are really helpful and it will allow them to learn much faster, bringing them to the point where they can use it to its full potential. In summary, I am really comfortable with this tool, I haven't had many problems, and it's sufficient for our work. In the three years that I have been working with it, whenever I've needed something, I've been able to find it. I would rate this solution a nine out of ten.

I'd rate the solution eight out of ten. I'd recommend people do a proof of concept (POC) around Tosca and compare it to other available tools. That way, an organization will know if the solution is right for them without investing too much time into everything.

We use the on-premises deployment model. My advice to others is to get training by a professional. This will help anyone use the product. Tosca allows users, even if they don't have some IT knowledge, to quickly start and use Tosca after about two weeks. You can take any business person, and just offer them good training. After about two weeks or a month, they could be independent and will be able to automate some complex scenarios. You don't have to be an IT specialist to handle the product. I'd rate the solution eight out of ten.

Before looking at a tool, it's not just about implementing the tool. It's about having the right mindset to be able to implement a tool. With Tosca, we didn't go and say, "We want to use Tosca. Go." We have a whole training where we talk about what needs to shift, how you need to shift, why we are doing it, and making people understand the intent behind using some of these tools. Otherwise it does not work. We have seen enough failures with other implementations to know that if we don't have the right mindset, these things don't work. Also, having the right partnership and setting expectations with the vendor is very important. If they have good best-practices and if they know what they're doing, that will help. Having a long-term vision is very important, instead of just saying, "Okay, I'm going to implement Tosca. Go," and not knowing where you want to go or what you want the future to look like. Those are things that helped us a lot in our implementations of Tosca. One lesson, as I said, is that working with the tool vendor helps. Not that Accenture didn't do a great job. They did. They helped us a lot, especially from a process and best-practices perspective. But having Tricentis in there would have been good. Tosca was relatively new in the US when we started using it. The roadmap was not fully baked. I would love to work with them on their cloud roadmap. I still don't have a great answer when it comes to cloud roadmap for Tosca, from Tricentis. That's something we're still pushing them on. Tricentis also has a great relationship with Salesforce and that has helped us a lot. We're trying to push them to have a similar kind of relationship with Guidewire, with Guidewire 10 coming and the cloud option. That's another thing which we will be using Tosca for. We have been asking Tricentis to have some kind of partnership with Guidewire, and they have been asking us if we can introduce them. We're working through that. We have a user group for that with other Tosca users that are in Guidewire and who are moving to Guidewire 10. It would be great if Tricentis could take a look ahead at some of these big vendors, packaged applications, and form some relationships with them. That would help companies like us who are heavy users of these packaged applications. We would like to see something similar to what they have done with SAP and with Salesforce. Guidewire is big right now. That's an area they have not done anything in yet. We were an IBM shop. We used to use Rational Team Concert and Rational Requirements Composer. We're shifting to JIRA for requirements. We're still looking at what we will use for persistent requirements, but right now it's JIRA. Even if users want to use Tosca for requirements, and there are teams who are doing it because it helps us get good coverage, we still use JIRA and then we try to integrate from JIRA to Tosca, but we have not done that yet. Tosca has a risk-based functionality, which we are not using, which they added after we started with Tosca. It can take a look at the data and say, "Hey, you have 200 test cases and you are getting 50 percent coverage based on the requirements that you have in Tosca. You can get the same coverage using 100 test cases." The reason we didn't use the Tosca's risk-based testing is that risk-based testing is applicable irrespective of the tool. Since Tosca is not something that is the only standard at our company — we have multiple tools — we had to choose a tool that we could use across the enterprise and not be dependent on the Tosca licenses. So we use another tool for risk-based testing. When you talk about redundancy, there are two aspects. One is: We have been using Tosca for three years; we have 2,000 scripts. Even though Tosca has all the functionality by being model-based with reusability, not everyone understands that. In these past three years, new people might have come in and added test scripts and test cases without knowing that something already existed. They may have created duplication and redundancy. Can Tosca go and help us with that? I don't think so. We are actually looking for a tool that can help us do that. We were looking at Saffron AI Suite, which is an Intel product, but Intel decided not to support it. We're still looking for a tool that can help us with duplication. But what we are doing is from a data perspective is the following: If I say, "Hey, here is my data, here is my test case, here are the data elements that are needed. Tell me what is the minimum number of scripts I need to get maximum coverage?" Tosca can do that. But as I said, we didn't want to depend on Tosca because we're not using Tosca across the enterprise. We're using another tool called Hexawise to help us do that and it's something that we're implementing across the company. It is much more cost-effective for us than having Tosca licenses for everyone. Tosca is expensive. We're trying to use the output from Hexawise to create test cases in Tosca to help us get that minimum number of test cases we need to get the maximum coverage. That coupling has been working well for us. Maintenance is better with Tosca. The way Tosca is structured, it tells you where your tests are failing and the like. If I have nine quality engineers for an application and they are spread across three build teams, if they have the continuous integration implemented, whatever issues or errors come up, we expect them to keep maintaining things on a go-forward basis. Maintenance is absolutely easier with Tosca, provided it has been implemented the right way. We're not differentiating between people who are doing build work versus people who are doing maintenance. It's the same people. We expect them to build the test cases and maintain them as well. I would rate Tosca at about eight out of ten. We're pretty happy with the results we've seen with Tosca.

If you're going to have somebody come in and help set up, don't go with a third-party vendor, but have Tricentis consultants come in, do training, and help set up. It's worth the extra money to have them come in and do right, versus a third-party that might not know everything. That was our experience. We tried the third-party route to help us, and we immediately saw that it was not the right way to go. That's when we went to Tricentis themselves to come in and help us. The biggest lesson I've learned is more connected to the tool's adoption. If people have been doing the same thing for over ten years, it tends to be a little bit hard for them to switch over because they want to do things the way they've always been doing them. But the tool itself is fairly simple. It's a pretty solid tool. There are a few ways to overcome the resistance to new technology. But it's really about creating urgency around why the tool is important to the company and why people need to adopt it. We've done lunch-and-learns to help people understand it. We also champion any success stories with the tool, through newsletters that go out. Sometimes, it's just about bringing in new people with the right mindset. We've slowly been increasing our rate of testing automation using Tosca. We did a digital transformation with SAFe Agile, and then with adopting test automation. So the tool-adoption piece has taken a little bit longer. We're not quite where we want to be yet. We're still building on it. Tosca covers about 50 percent of our test cases at this point. The solution hasn't reduced our cost of testing yet. We're still a little immature in this process. In terms of delivering more features for release, we are watching features but we're not there yet. We're just not mature enough to have those hard facts to help us state that this is helping complete more features. From a defects standpoint, we're trying to get a better handle on how defects are captured here, because before there wasn't a concise, approved process on defects. Everybody did their own thing and I'm pretty sure things fell through the cracks. People weren't identifying defects as defects. That's another one of the things we're trying to get better at. Tricentis keeps building on BI and Tosca itself, and they're just getting better and better every time. A lot of the things they're focusing on are the right things.

For organizations who want to aim for a unified continuous testing platform, and are willing to pay for it, Tricentis Tosca can be a decent investment.

Figure out your requirements and environment. We had the impression Tosca would be the perfect fit for us. We did a proof of concept test with all our applications, Tosca was able to work with them and drive the proof of concept goal. Finally, we made a decision a year ago to work with Tricentis Tosca. We are quite happy with the product.

My most important criteria when selecting a vendor are its technology and is it stable enough.

Take the online training on Udemy before you confirm the intent to buy it.