I haven't a bad opinion about the prices, however, when you pay a license is for a month or a year but in my experience, you not always use automated testing 100% of the time.
Maybe it's more useful if you will have a license per use, it could be by a number of testing or by a number of hours, it will be great.
Worksoft Certify is slightly more expensive compared to other automation tools that are available on the market. However, the majority of the clients who are utilizing this solution, don't care much about the price. The main aspect the clients look for is its stability and reliability on the automation and whether they are able to rely on the automation scripts. The solution can be purchased in different packages, some can include support.
We got subscription model licenses three or four weeks ago. Now, we are setting up enrollment for other products of Worksoft. It is recommended that we should do our migration and upgrades in a test enrollment environment first, then move to a production environment. In general, they changed their license model. Before you had to buy licenses for each component, and now they changed it so you can buy a license and use it for nearly all their applications.
Enterprise Architect SAP Solutions at Siemens Industry
Real User
2021-07-01T10:32:00Z
Jul 1, 2021
I can only judge based on the situation that we had around six years ago when we did the tool evaluation. Worksoft was not the cheapest, but it provided the value. For 25 concurrent licenses, we paid more than €400,000, so it was not cheap. In the end, if you see how much time you are saving and compare it with others, its price is okay. We had also compared its cost with the licensing costs for HP and Tricentis, and they were at another level. Now, as we have already booked the licenses, we only have to pay an annual maintenance fee, which is 70%, and that is okay.
Configuration Owner at a manufacturing company with 10,001+ employees
Real User
2020-08-03T06:11:00Z
Aug 3, 2020
Purchasing and licensing are okay. Go for the perpetual licenses. In that way, you own a license, then you can purchase maintenance and support on top of that, so you don't have to pay every year for it. Even if you don't want it a contract with Worksoft Certify in the future, you will have your own license of it. Then, if your usage is not that much, you can have one or two perpetual licenses. However, if you want to run your processes, you will need more licenses, e.g., using the run-only licenses. They are really cheap compared to the full licensing. There are multiple licenses available from Worksoft depending on your requirements. You can take any one of them, and they are really good. For example, if we are using five to 10 perpetual licenses where we need to update or create scripts and run parallelly, simultaneously multiple scripts with just one license, it will take months for us to run 162 processes. Therefore, we have run-only licenses that we use when it comes to executing our test scripts on releases.
SAP QA Manager at a manufacturing company with 10,001+ employees
Real User
2020-08-03T06:11:00Z
Aug 3, 2020
License model is a traditional one. As with any other manufacturing company, the software testing is not our core business, it's not in our interest to invest capital into the licenses. It would be preferable to have a pay-per-use model. At the same time, it's a fair game, for now. Aside from their standard licensing fee, if you want to have enterprise support, there's an additional cost.
The initial investment is probably a little high. It was a little hard for me to sell, but it was a one-shot deal and that's why it's so high. All we are doing now is paying annual maintenance, which we don't have to do if we don't want upgrades, but we do. It is based on the number of licenses. If we had bought a larger number of licenses, our costs would have come down significantly, which is fair. I did struggle a little bit trying to sell it because our company had already had one failure with a testing solution, and here I was asking for money to try again. However, since we got it in, we have had great success. We have seven licenses today. The people using it are three automation engineers/quality assurance testers who do SAP ECC. We also have three who do web application testing. They are the ones creating the automation for our portals, e.g., customer portal. I have one test lead who oversees this team and bounces between both SAP and web testing. We haven't bought a whole lot of licenses and haven't rolled it out to a massive number of users. We're doing all the work ourselves. Since these are concurrent licenses, we could double the number of users with our current licenses because six out of the seven are offshore. While we are sleeping, they're using them.
We would like to have a cheaper version for a single user/trail version of the same for our trainings. The cloud based environment should be available free for the trainings for 15 days or so.
The license cost is quite high. This might not be a consideration for a large company, but it will be for a small company. E.g., Tricentis (their competitor) offers certain exclusive use cases where a company can use it in a certain way, so this is another option that companies consider.
SR. Business Process Partner, Commercial Operations at GSK at a pharma/biotech company with 10,001+ employees
Real User
2019-02-04T08:44:00Z
Feb 4, 2019
The price is in line with everyone else's in the market. They are not cheaper nor more expensive than anyone else who was in our RFP. There is a cost involved to doing it, but once you get over the initial cost, then you'll start reaping the benefits and seeing that testing is getting done more quickly and efficiently. We are still early on with it, but the expectation and what we're seeing is that we will start seeing some savings coming out on the back-end once we have this done.
Global ERP Test Manager at a manufacturing company with 5,001-10,000 employees
Real User
2019-02-04T08:44:00Z
Feb 4, 2019
We ended up buying too many licenses. They were very good at selling it to us, and probably oversold it a little. We bought 45 licenses and have never used more than twenty. However, they gave us a pretty significant discount on the bigger license, so it made sense for us to buy enough that we wouldn't have to go back and ask for more. At that time, we had budget to do that. The licensing is pretty straightforward. We have considered using them to do robotic process automation and may still do that. Initially, we were worried that our license might preclude us from using the tool for something other than testing, but when we checked into that, there is no limitation. We could use Certify to do robotic process automation, which is basically running a process on your correction system instead of your test system. Therefore, we may do that in the future.
The initial investment is probably a little high. It was a little hard for me to sell, but it's a one shot deal and that's why it's so high. All we are doing now is paying annual maintenance, which we don't have to if we don't want upgrades, but we do. It is based on the number of licenses. So, if we had bought a larger number of licenses, our costs would have come down significantly, which is fair. I did struggle a little bit trying to sell it because they'd already had one failure, and here I was asking for money to try again. However, once we got it in, we have had great success. We have seven licenses today. The people using it are three automation engineers/quality assurance testers who do SAP ECC. We also have three who do web application testing. They are the ones creating the automation for our portals, e.g., customer portal. I have one test lead, who oversees this team and bounces between both SAP and web testing. We haven't bought a whole lot of licenses and haven't rolled it out to like massive amount of users. We're doing all the work ourselves. If the company decides that they want to roll it out then they will do that, but right now, they started small. Since these are concurrent licenses, we could double the number of users with our current licenses because six out of the seven are offshore. While we are sleeping, they're using them. As we continue to expand, we just started a PoC with our Middle East carrier business unit. Depending on how they feel about the tool, we will probably be increasing our license to get those people onboard. But, we're just starting that. We also purchased the Worksoft Analyze license and ran it. The problem I have with it is that it doesn't differentiate between objects that are in being used vs. not being used in SAP. You have to sort the unused objects out of your results. I was doing that for a while, but we will be moving to a more robust tool. We are in the process of starting to use it. The problem with Worksoft Analyze is that it's an extra tool and license, a separate license. Their main strength is automation. I don't think they are focusing on Worksoft Analyze like they focus on the automation tool, because that is really what customers want, the ability to automate tests. Worksoft Analyze is a scope definition tool. Therefore, I am not currently using Worksoft Analyze.
Testing & Quality Assurance Manager at Johnson Matthey Plc
Real User
2019-02-04T08:44:00Z
Feb 4, 2019
It is expensive compared to some of the other automation tools in the market. However, the benefits and ROI has proved that it has been a good investment. We have concurrent licenses.
IT Quality Assurance Manager at a manufacturing company with 10,001+ employees
Real User
2018-10-08T17:34:00Z
Oct 8, 2018
When talking about continuous testing, so then the tool is not really good at all because you need to purchase some additional tools. For example, the Execution Manager and other tools, which are an additional cost. Another added cost is the payment necessity for reporting.
QA Developer II at a university with 10,001+ employees
Real User
2017-07-05T06:05:00Z
Jul 5, 2017
Conduct a proof of concept (POC) so that you understand what needs to be invested with Worksoft Certify. You will need to understand what sort of time you need to initially set aside to learn and apply the tool, and how that time can be leveraged to shorten continuing development of Worksoft Certify test scripts (processes) as facility in the tool increases. * Someone needs to know to administer it. * Someone needs to know how to develop the tests. * Someone needs to develop a representative automated test script for a candidate application in your organization. * That person also needs to execute the scripts and then report results of the scripts. That script needs to execute several times. Now a comparison needs to be done with the time it takes to execute the multiple test runs against the same time it would take to do the same thing manually. In this way, you can now quantify your savings. Now apply the need over the instances in your organization and compare that to the pricing and licensing to see how many instances of this effort would give you a return on your investment. You will find that you will have many instances that would justify the price and licensing costs.
Worksoft Certify is the industry's first codeless automated testing system, created for non-technical people to test end-to-end business processes at an enterprise scale.
It was designed to test complicated processes spanning numerous apps and integrating into contemporary DevOps tool chains. Worksoft Certify manages dynamic input, process flows, and frequent variances in business processes with ease.
Worksoft Certify automates the testing of your exact business processes across all of your...
The tool is worth the money.
Worksoft Certify is priced higher than most tools. I rate Worksoft Certify an eight out of ten for pricing.
Worksoft is reasonably priced.
I haven't a bad opinion about the prices, however, when you pay a license is for a month or a year but in my experience, you not always use automated testing 100% of the time.
Maybe it's more useful if you will have a license per use, it could be by a number of testing or by a number of hours, it will be great.
Worksoft Certify is a bit costly. It is a good product so the cost is a bit high. But I'm not sure about how much we pay for it exactly.
I believe licensing costs are based on the number of users and licensing is on an annual basis.
I'm not aware of any licensing costs for Worksoft Certify.
This solution is expensive.
We have an annual license for this solution. The product is very expensive.
Worksoft Certify is slightly more expensive compared to other automation tools that are available on the market. However, the majority of the clients who are utilizing this solution, don't care much about the price. The main aspect the clients look for is its stability and reliability on the automation and whether they are able to rely on the automation scripts. The solution can be purchased in different packages, some can include support.
We got subscription model licenses three or four weeks ago. Now, we are setting up enrollment for other products of Worksoft. It is recommended that we should do our migration and upgrades in a test enrollment environment first, then move to a production environment. In general, they changed their license model. Before you had to buy licenses for each component, and now they changed it so you can buy a license and use it for nearly all their applications.
I can only judge based on the situation that we had around six years ago when we did the tool evaluation. Worksoft was not the cheapest, but it provided the value. For 25 concurrent licenses, we paid more than €400,000, so it was not cheap. In the end, if you see how much time you are saving and compare it with others, its price is okay. We had also compared its cost with the licensing costs for HP and Tricentis, and they were at another level. Now, as we have already booked the licenses, we only have to pay an annual maintenance fee, which is 70%, and that is okay.
Purchasing and licensing are okay. Go for the perpetual licenses. In that way, you own a license, then you can purchase maintenance and support on top of that, so you don't have to pay every year for it. Even if you don't want it a contract with Worksoft Certify in the future, you will have your own license of it. Then, if your usage is not that much, you can have one or two perpetual licenses. However, if you want to run your processes, you will need more licenses, e.g., using the run-only licenses. They are really cheap compared to the full licensing. There are multiple licenses available from Worksoft depending on your requirements. You can take any one of them, and they are really good. For example, if we are using five to 10 perpetual licenses where we need to update or create scripts and run parallelly, simultaneously multiple scripts with just one license, it will take months for us to run 162 processes. Therefore, we have run-only licenses that we use when it comes to executing our test scripts on releases.
License model is a traditional one. As with any other manufacturing company, the software testing is not our core business, it's not in our interest to invest capital into the licenses. It would be preferable to have a pay-per-use model. At the same time, it's a fair game, for now. Aside from their standard licensing fee, if you want to have enterprise support, there's an additional cost.
The initial investment is probably a little high. It was a little hard for me to sell, but it was a one-shot deal and that's why it's so high. All we are doing now is paying annual maintenance, which we don't have to do if we don't want upgrades, but we do. It is based on the number of licenses. If we had bought a larger number of licenses, our costs would have come down significantly, which is fair. I did struggle a little bit trying to sell it because our company had already had one failure with a testing solution, and here I was asking for money to try again. However, since we got it in, we have had great success. We have seven licenses today. The people using it are three automation engineers/quality assurance testers who do SAP ECC. We also have three who do web application testing. They are the ones creating the automation for our portals, e.g., customer portal. I have one test lead who oversees this team and bounces between both SAP and web testing. We haven't bought a whole lot of licenses and haven't rolled it out to a massive number of users. We're doing all the work ourselves. Since these are concurrent licenses, we could double the number of users with our current licenses because six out of the seven are offshore. While we are sleeping, they're using them.
We would like to have a cheaper version for a single user/trail version of the same for our trainings. The cloud based environment should be available free for the trainings for 15 days or so.
The licensing is yearly.
Cost-wise, compared with other tools, it is a great product.
The license cost is quite high. This might not be a consideration for a large company, but it will be for a small company. E.g., Tricentis (their competitor) offers certain exclusive use cases where a company can use it in a certain way, so this is another option that companies consider.
We are not using Capture 2.0 at this point, because we don't have a Worksoft Analyze license.
Worksoft can help you to select the right automation platform, then deliver value quickly.
The product works well with SAP and non-SAP products.
The price is in line with everyone else's in the market. They are not cheaper nor more expensive than anyone else who was in our RFP. There is a cost involved to doing it, but once you get over the initial cost, then you'll start reaping the benefits and seeing that testing is getting done more quickly and efficiently. We are still early on with it, but the expectation and what we're seeing is that we will start seeing some savings coming out on the back-end once we have this done.
We ended up buying too many licenses. They were very good at selling it to us, and probably oversold it a little. We bought 45 licenses and have never used more than twenty. However, they gave us a pretty significant discount on the bigger license, so it made sense for us to buy enough that we wouldn't have to go back and ask for more. At that time, we had budget to do that. The licensing is pretty straightforward. We have considered using them to do robotic process automation and may still do that. Initially, we were worried that our license might preclude us from using the tool for something other than testing, but when we checked into that, there is no limitation. We could use Certify to do robotic process automation, which is basically running a process on your correction system instead of your test system. Therefore, we may do that in the future.
The initial investment is probably a little high. It was a little hard for me to sell, but it's a one shot deal and that's why it's so high. All we are doing now is paying annual maintenance, which we don't have to if we don't want upgrades, but we do. It is based on the number of licenses. So, if we had bought a larger number of licenses, our costs would have come down significantly, which is fair. I did struggle a little bit trying to sell it because they'd already had one failure, and here I was asking for money to try again. However, once we got it in, we have had great success. We have seven licenses today. The people using it are three automation engineers/quality assurance testers who do SAP ECC. We also have three who do web application testing. They are the ones creating the automation for our portals, e.g., customer portal. I have one test lead, who oversees this team and bounces between both SAP and web testing. We haven't bought a whole lot of licenses and haven't rolled it out to like massive amount of users. We're doing all the work ourselves. If the company decides that they want to roll it out then they will do that, but right now, they started small. Since these are concurrent licenses, we could double the number of users with our current licenses because six out of the seven are offshore. While we are sleeping, they're using them. As we continue to expand, we just started a PoC with our Middle East carrier business unit. Depending on how they feel about the tool, we will probably be increasing our license to get those people onboard. But, we're just starting that. We also purchased the Worksoft Analyze license and ran it. The problem I have with it is that it doesn't differentiate between objects that are in being used vs. not being used in SAP. You have to sort the unused objects out of your results. I was doing that for a while, but we will be moving to a more robust tool. We are in the process of starting to use it. The problem with Worksoft Analyze is that it's an extra tool and license, a separate license. Their main strength is automation. I don't think they are focusing on Worksoft Analyze like they focus on the automation tool, because that is really what customers want, the ability to automate tests. Worksoft Analyze is a scope definition tool. Therefore, I am not currently using Worksoft Analyze.
It is expensive compared to some of the other automation tools in the market. However, the benefits and ROI has proved that it has been a good investment. We have concurrent licenses.
We would purchase more licenses right now if they were cheaper. Pricing is a little bit of a hindrance.
When talking about continuous testing, so then the tool is not really good at all because you need to purchase some additional tools. For example, the Execution Manager and other tools, which are an additional cost. Another added cost is the payment necessity for reporting.
Conduct a proof of concept (POC) so that you understand what needs to be invested with Worksoft Certify. You will need to understand what sort of time you need to initially set aside to learn and apply the tool, and how that time can be leveraged to shorten continuing development of Worksoft Certify test scripts (processes) as facility in the tool increases. * Someone needs to know to administer it. * Someone needs to know how to develop the tests. * Someone needs to develop a representative automated test script for a candidate application in your organization. * That person also needs to execute the scripts and then report results of the scripts. That script needs to execute several times. Now a comparison needs to be done with the time it takes to execute the multiple test runs against the same time it would take to do the same thing manually. In this way, you can now quantify your savings. Now apply the need over the instances in your organization and compare that to the pricing and licensing to see how many instances of this effort would give you a return on your investment. You will find that you will have many instances that would justify the price and licensing costs.