What is our primary use case?
It is used for codeless automation. I am using its most recent version, and it is on-premises, but we are using it through some virtual machines. It is installed on some virtual machines, and by accessing those virtual machines, we're using Worksoft Certify.
How has it helped my organization?
It is codeless. Typically, you have to write code in Java, Python, or another language to automate web applications or ERP applications, but Worksoft Certify is completely different. You do not need to do any coding, and you do not need to know any coding language for automation. It is completely a techno-functional tool. You can just enable the application that you want and start automating.
There are certain tools in the market for writing the code, but they are not supported with some of the ERP solutions available, such as SAP, Oracle, etc. Worksoft Certify is not like that. It supports each and every ERP solution available in the market.
An organization doesn't need to hire new people for automation. For example, if you already have people who are well versed in SAP, you can just train them on this particular tool, and they'll be able to do automation for you. You do not need to hire any new resources for this particular tool, and even if you are hiring, you would need a less number of people. It saves costs in terms of resources.
Scheduling and lights-out testing are very easy. You can schedule any number of test cases on a recurring or on-demand basis. So, you can run any number of test cases. Test maintenance is very easy, and you can very easily manage all your tests, which also saves cost. So, it saves costs in terms of resources and maintenance.
What is most valuable?
The Worksoft Capture feature is most valuable. For example, if you are creating a sales order in SAP, you do not need to go to each field and do everything. You do not need to write code for each and every line. You can just turn on the Worksoft Capture feature and manually perform your actions. It will capture all manual actions, and it will give you the steps. It will write the steps for you.
What needs improvement?
They have a scheduler in Execution Manager, but it is not customizable. Its UI needs a lot of improvement. The lights-out testing is a bit difficult with that particular tool, and it needs a lot of improvement. Of course, there are so many integration options with Worksoft for execution, but when it comes to Execution Manager, which is their own tool, there is a lot of scope for improvement.
The integration with mobile needs to be improved. Initially, they used to support certain applications, and now, they are supporting all the web applications, but with minimal knowledge, it's very difficult for any tester to automate web applications. That's where they need to improve a lot. They are already working on it. They have given additional features, and with the help of those features, you can easily automate, but they need to keep making it easier for business users who do not want to get into each and every technical aspect of it. They just want to capture the actions. It is working fine with SAP, but they have to concentrate on web applications. They also need to support Safari, as well as macOS, better.
If you keep on running it for a long time without removing unnecessary things, the load on the database increases, which impacts the performance of the tool. Sometimes, it hangs or is slow. We have faced this situation with the earlier versions, such as version 9, but in the current version, there is an improvement. The slowness has drastically reduced, but a lot of improvement is still required in this particular area.
Another negative of this tool is that its license is costly. It is a bit more expensive than other tools.
For how long have I used the solution?
I have been using this solution for close to six years.
What do I think about the stability of the solution?
Its stability is very good. It is reliable.
What do I think about the scalability of the solution?
Its scalability is very good. We are a very big organization. In my team, we have close to 14 automation engineers, but there are so many other projects where Worksoft is used. I don't know the exact number, but it would be very high. Its usage is not extensive because it is mostly being used for ERP applications.
In my previous organization also, it was implemented for many projects.
How are customer service and support?
Their support is excellent. When you raise a ticket, within a day, you get the solution. If they're not able to resolve the issue at their end, and it is on our side, they connect with us and show us what exactly is happening. They check everything.
How was the initial setup?
Its initial setup is very simple.
What about the implementation team?
It was implemented in-house. We get some files that we can directly install, and that's it. We do not need to do anything other than double-clicking the given files, and it creates everything automatically.
What's my experience with pricing, setup cost, and licensing?
It is costly. It is a bit more expensive than Tricentis Tosca and other tools. If they reduce its price going forward and have partnerships with other vendors, it will grow like anything.
Which other solutions did I evaluate?
Tricentis Tosca is a strong competitor. Worksoft Certify is more expensive than Tricentis Tosca. The solution that we use depends on a client's choice.
What other advice do I have?
In the long run, most people will prefer non-coding tools, where 0% coding is required. It is, for sure, a tool that would be useful, but there is only one hiccup. If you are executing tests multiple times, you'll have various results, such as pass, fail, etc. When you are running it for so long time, the file size on the database will keep on increasing. So, you have to keep on doing the maintenance. For example, if you need the results for 2018, you should download everything. You would need some kind of storage.
In many organizations, the managers think that if they hire one or two resources with Worksoft knowledge, they can train everyone in their team, and build a good team, but that's not going to happen in the short run. That's why I advise having two to three dedicated people to train other people and build a team. With only functional team members, it is very difficult to build a proper automation team. I have seen an automation team that wanted to train 20 people. Currently, we are training 100 people. There are three of us who are training 100 people, which doesn't work out very well. So, there should be a few dedicated people for training and implementation.
I would rate Worksoft Certify an eight out of ten. It is a fantastic tool. Its maintenance is easy. Building test cases is easy, and planning is easy. Almost everything is easy, but the look-and-feel of the Execution Manager scheduler is not good, and currently, customization is not available, and product creation is not available.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.