Worksoft Certify Reviews

My current use case for Worksoft Certify is mainly for test automation with SAP.

Worksoft Certify helps in reducing regression cycle time because manual testing takes substantial time and can lead to errors. With Worksoft Certify, it will definitely help reduce resources as time and ROI will also increase.

I have used Continuous Testing Manager (CTM) to run some tests, and it is based on lights-out testing, which helps significantly with overnight execution. CTM is effective for managing the testing process because it is helpful; you don't have to sit in front of the machine and see the execution, as you can schedule the executions and see the results.

Worksoft Certify is a no-code tool that works effectively with SAP, and I appreciate all the features compared to other tools.

Teams who are planning for automation and are still in manual testing can use Worksoft Certify, and significant time and resources will be reduced.

Reporting for Worksoft Certify is also excellent; we have the BPP reports customized, and recently WRS has been implemented, so all these features are beneficial.

If any AI-powered features are included, that would be great. We've already seen the beginning of self-healing capabilities, but additional integrations with AI would be beneficial. Focusing more on AI and its integration with Worksoft would really help enhance our processes.

I have been working with Worksoft Certify for more than 12 years.

For stability, I would rate Worksoft Certify a nine out of ten.

For scalability, I would rate it as the best.

I would rate their technical support a nine out ten. I am satisfied with it.

The setup process for Worksoft Certify is quite easy; it requires just installation to use it. I have worked in many different environments, including both on-premises and cloud options such as AWS.

We purchased Worksoft Certify through a partner because we are a vendor.

I would rate the pricing for the product as reasonable. As it is a quality tool, the price is slightly higher, but that is acceptable compared to other tools, especially considering the ROI.

I can compare Worksoft Certify with Selenium, as we need to write code in Selenium but not in Worksoft Certify, and other tools such as Katalon Studio can also be compared with Worksoft Certify.

Overall, I would rate Worksoft Certify a nine out of ten.

Our main use case for Worksoft Certify is front-end automation, and we're also looking at offline testing where we can leave Worksoft Certify running while we go offline, so there's continuous testing.

I am not the day-to-day user myself, but many members of my team are.

We're getting good value from continuous testing management, and the fact that it's also codeless is valuable. It requires minimal to no coding at all, helping to ramp up the knowledge for our testers. I've not heard of any issues related to integration from our team.

Based on my colleagues' feedback, there are still some minor issues concerning continuous testing, particularly related to the timeout feature. Overall, we don't have major issues with it. We are satisfied with the functionality part.

I have been working with Worksoft Certify for a couple of years.

It's stable. I would rate it a nine out of ten for stability. 

I would rate the scalability of Worksoft Certify a nine out of ten. We are an enterprise company. It covers companies of all sizes.

Their technical support is responsive, which is good, and their solutions are timely. We just had a couple of instances that took a bit longer, but overall, we are satisfied.

Positive

The initial setup is not so complex, but it still needs some work. Overall, it's pretty easy and straightforward. Our deployment model is hybrid.

I am not certain which competitors Worksoft Certify has on the market, but Selenium is always present. Additionally, a few AI-driven automation tools are emerging.

We are not using any AI integration with Worksoft Certify yet, but I think they are coming up with AI-supported features.

I can definitely recommend it to other users. I would rate Worksoft Certify a nine out of ten.

We primarily used Worksoft Certify to automate SAP applications, and it is also well suited for web application automation as well.

Worksoft Certify has improved in many places in my organization, mainly in automating SAP applications. It helped reduce manual testing efforts and it's minimizing the chances of human error. Its well suited to automate both SAP and web applications made it highly adaptable to our needs. With its integration into our Agile and continuous testing workflows, we were able to deliver faster and with greater confidence. Overall, it has enhanced the efficiency and quality of our testing process.

SAP objects don’t usually change much, but I found the dynamic object identification really helpful for web apps as well as SAP like after upgrade when something is changes. It helps keep the scripts stable and saves time on maintenance.

From my experience, Worksoft Certify is a good tool for automating SAP, and it also works fine with web apps. But while creating or running scripts, we do face some automation abort issues, which break the flow and need rework. Also, sometimes it feels a bit slow, especially when running more scripts together. If the speed and stability can be improved, that would really help. We are using CTM for scheduling and managing runs it’s useful, but there’s still some scope to improve things like live monitoring and checking results more easily.

I have been using Worksoft Certify for three and a half years.

From what I’ve seen, it scales well. We started with fewer scripts and later added more without issues, especially with CTM handling the runs. But yeah, we need to plan properly to manage the load smoothly.

Customer service and support were good overall. I’d rate it around 80% based on my experience.

Positive

I have only experience with Worksoft Certify itself, so I'm not completely aware of other products for comparison.

Yeah, the setup and license cost is a bit high as per I known but if you’re working mostly on SAP, it’s worth it definitely. You just need to plan based on your project and how much you’ll use it.

I can perfectly recommend this product to others because Worksoft Certify is very user-friendly and we can easily automate the test cases. I would be interested in being a reference for Worksoft. The vendor can contact me if they have any questions about my review. I rate Worksoft Certify eight to nine out of ten overall.

It serves as our primary automation tool, specifically utilized for testing purposes. The tool predominantly finds application in functional testing and integration testing for our customers.

The tool itself is highly effective, especially when it comes to comprehensibility for newcomers. Even during the initial learning phase, I found it remarkably user-friendly. It facilitates quick onboarding and training of new resources. It offers features for building automation scripts, such as search and certify capture. A notable advantage is that it doesn't rely on other tools like Micro Focus UFT or Micro Focus ALM for script execution. Worksoft can run independently without the need for support from Microsoft Office, although the option to use it for maintaining data exists. The tool also includes debugging features and comprehensive reporting capabilities, generating PDF reports for easy analysis.

The primary area for improvement is the support service. The support process can be time-consuming, with tickets sometimes remaining unresolved even after considerable follow-up. Also, it doesn't offer a training or trial version for users to explore the tool before committing. Enhancing direct connectivity between radio and Worksoft Certify would streamline and improve efficiency. Although there are YouTube videos for specific features, the Worksoft community lacks corresponding content. This has been a common concern among users who find information on YouTube but struggle to locate it on their community portal.

I have been working with it for over eight years now.

I would rate its stability capabilities eight out of ten. Stability concerns are significant in automation, especially when dealing with new applications or features. Challenges arise in assessing the feasibility of automation without adequate support.

I would rate the scalability ten out of ten. At the moment, we are involved in four distinct projects out of the overall portfolio, which consists of around thirty projects. The focus is primarily on high-scale business initiatives.

While having a partner with dedicated support can help in critical situations, as a customer, the overall support experience might not always meet expectations. It often involves multiple calls and explanations to various teams across different locations, making it a bit cumbersome. I would rate it six out of ten.

Neutral

The initial setup was straightforward. I would rate it nine out of ten.

The deployment typically takes one to two weeks. The first step involves setting up the database, determining the server specifications, and installing the servers based on the specific requirements and data activities of the project.

While I acknowledge that it's a good tool, the challenges with support are notable. Despite the tool's excellence and the introduction of new features, the ground-level implementation should align with the promised benefits. In comparison to other tools in the market, some offer superior support and features. However, it's worth noting that it remains one of the best tools for learning, especially for users who might not have many alternatives. Overall, I would rate it ten out of ten.

Worksoft Certify is an automation tool used for functional testing.

Worksoft Certify Mostly is an easy-to-learn tool and does not require any extensive training. It is easy to record and play this tool. Anybody can learn and start working on the solution. As per industry standards, Worksoft Certify is the first choice for SAP applications. It has a lot of built-in objects and repositories for SAP applications.

The solution's support could be improved. Worksoft Certify's support team should respond more promptly when we are stuck with certain issues and looking for a solution. They have been helpful so far, but quick conversations can happen if they function within the timelines.

Worksoft Certify has already come up with a new tool, a continuous testing manager for lights-out testing. It's good that they are working in those areas to develop new tools to support the lights-out testing. Worksoft Certify should also try to develop some solutions that can be more beneficial for non-SAP applications, like web-based automation or Excel-based automation. Worksoft Certify can be made more robust in those areas.

I have been using Worksoft Certify for four years.

I rate Worksoft Certify a seven out of ten for stability.

Worksoft Certify is a scalable solution. I rate Worksoft Certify a seven out of ten for scalability.

Worksoft Certify is priced higher than most tools. I rate Worksoft Certify an eight out of ten for pricing.

Different solutions are available per the client's needs, but I still recommend Worksoft Certify as the number one or number two choice for SAP-based applications. For EPC and SAP, Worksoft Certify would be the first go-to choice.

Overall, I rate Worksoft Certify an eight out of ten.

In my company, the solution is used for SAP automation.

The technical support of the product is an area of concern where certain improvements are required.

I have been using Worksoft Certify for more than three years.

I am satisfied with the tool's stability. There have been no issues with the product's stability.

Stability-wise, I rate the solution a seven to eight out of ten.

The tool's scalability features did meet my company's goals. Scalability-wise, I rate the solution a seven to eight out of ten.

The solution's technical support was pretty good. There is a ticketing system and a call system to contact the product's support team.

I rate the technical support a six to seven out of ten.

Neutral

For automation purposes, my company works with multiple open-source tools, like Selenium and Java, along with a few license-based tools, like Worksoft Certify, QuickTest Professional, HP ALM, LoadRunner, IBM Rational Performance Tester, and OpenText Silk Test.

The solution is deployed on an on-premises model.

There is a separate team in my company who has taken care of the product's deployment phase.

I chose the tool for my company since it suits the purpose for which I use it.

A specific feature that I found to be the most valuable in the solution for our company's work processes stems from the fact that it is useful as a low-code automation tool.

The tool is good for dealing with end-to-end testing scenarios in our company, and in my organization, we use it for SAP testing.

The tool is useful for functional testing, and it did add some value to my company.

The tool is useful to automate business workflows. My company used the product to automate the test cases for whichever systems were under testing phases.

I used the low code automation functionalities provided by the product. I did not use the scriptless test automation feature of the tool.

I rate the overall tool an eight out of ten.

We use this solution mainly for SAP automation and for some web applications and we also use the reporting feature. I'm a quality assurance project manager.

I would recommend Worksoft mainly for SAP. It has all the in-built functionality and Worksoft is a wonderful tool. They've introduced the hook feature in this latest version and it's great. In general, the latest version is significantly better than the earlier ones. 

I would like the Worksoft web application to be more robust. For example, SRM has different modules in SAP. When we automate some of those objects in the web app, it's initially fine, but after a couple of executions, we need to again record that particular object or get Worksoft to identify that particular object again. It works well with the SAP R/3 or GUI but there are limitations with the web application and Worksoft needs to improve that area. In terms of additional features, we'd like to see the default report which we generally get after the execution is completed. There should be an option to customize reports according to our requirements. Tosca provides that feature but it's unavailable in Worksoft.

I've been using this solution for five years. 

The solution is stable. When we're undergoing upgrades or version changes, some maintenance is required but it's quite easy. 

The solution is scalable. In my project, we have a team of around 100 people, 20 of whom are using Worksoft. We have a dedicated automation team. To date, we have automated more than 3,000 test cases using Worksoft.

Worksoft provides good technical support. They've helped us resolve issues numerous times. It's wonderful. 

Positive

We have introduced other tools like Tosca which we use as a codeless tool because it wasn't possible for us to automate through Worksoft. Where there are web application limitations in Worksoft, we switch to Tosca.

Because we have a dedicated team that takes care of deployment, it's a smooth process for us. 

I believe licensing costs are based on the number of users and licensing is on an annual basis. 

Worksoft is a good tool to start with as it is a codeless tool. There's no requirement for coding language knowledge. 

We rate this solution eight out of 10. 

Our use cases are mainly from different domains for mobility solutions. It is also for HR and eCommerce.

We implemented more than 200 test cases for critically defined processes. 

It helps us understand the end-to-end scenario and how it can be divided into multiple subprocesses. Those sub processes can be used whenever required. Based on that, we design automation scripts, then reuse them wherever required.

The solution has enabled us to find defects since it is a test automation tool. However, irrespective of the tool used, we are testing to find defects. Thus, it has found defects in our projects.

Certify is a codeless automation tool with scripts that are easy to maintain. Since it doesn't use any coding language, a person (who is unaware of any language) can directly deploy just by training him/her on how the tool works. So, if a person is well aware of at least basic programming knowledge, it can then be deployed by providing basic training.

For SAP, we have many use cases. Certify is helping us to automate things, which is really awesome. The time spent to automate is less when compared with other tools.

Initially, there were challenges because there is a concept called XF definitions, where each application type, e.g., the vendor and workflow, has to provide these XF definitions. Last year, these XF definitions were not provided. However, whenever we face any issues, we have to raise a support case, then they update the XF definitions in our enrollment. This year, they improved that and have the last XF definitions for SAP Fiori updated as of February 2021.

For integration, projects are usually agile. The customers are looking for integration with CI/CD tools, like Jenkins, Jira, Xray, Zephyr, etc. There is no clear documentation on how to integrate Certify with these tools. Also, we didn't receive the required support when needed. Worksoft used to have webinars on this, but those webinars used to be on after the integration was established and how the integration works, not on how to create an integration.

They should come up with a solution on how to do the integration. Jenkins, Jira, and Certify should be the same in every company. The only thing required is the pipeline code required to integrate Jenkins, Jira, and Certify if they make it available for everyone. Also, if an expert team could help customers to integrate, then that would really help our customers a lot. 

As part of our weekly regression, we wanted to use Execution Manager. However, from 2017 until March 2021, Execution Manager was not working as expected in our enrollment. It could have been better. If Execution Manager had worked well, then we could have doubled our productivity. Unfortunately, it had problems. 

We have been using the solution since May 2017.

The stability of the solution depends on how good the Configuration of your environment is. We haven't faced any issues w.r.t the stability and performance. So we can say the solution works good. 

We have increased the number of tests that we run based on customer requirements.

Sometimes, the support engineers will be unaware of the solution for which a support case has been raised. Their competency or knowledge on the tool could be improved. When calling them, they will see the problem but need a senior engineer who will not be available. We will then be forced to have a second meeting. Waiting for meetings and solutions can be really hard for us because we can't deliver to our customers.

But since last some moths, Customer Support has improved as they conduct bi-weekly follow-up meetings to address our pain areas and expedite the solution for the Support cases which are open.

Neutral

Compared to our previous solution, Worksoft Certify reduces our test maintenance work by 50%.

The initial setup was straightforward.

It took us a lot of effort and nerves to get it really running. I would also expect for the major CI/CD pipeline tools that these are somehow handled and covered.

The last upgrade of Certify happened in the month of March. That upgrade's time was around 30 minutes to one hour. There were also preparations needed because of internal policies for taking care of backups, which were a bit time-consuming.

There are separate server and database teams who have their own SLAs for deployment. It all depends on different project specifications. 

We have seen ROI from using Worksoft Certify. For example, in the mobility sector, we are frequently finding issues or defects that might have come into production if not properly tested. Some of them might cost some $10,000 if we had waited to solve them after they went to production.

Automation using Worksoft Certify has saved our testing times by 40% to 50%.

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.

We also evaluated Tricentis Tosca. Their pricing includes all their training. This is free of cost to everyone, even users without a Tosca license. If Worksoft came up with something similar, I think that they would get more customers.

We haven't bought any projects or use cases to automate Salesforce.

Worksoft Process Capture is a tool that captures the user actions. Usually, the functional consultant knows the functionality that has to be automated. We then have to install the feature on his machine for him to use Process Capture. The challenge is, since they will be unaware of the tool, we first need to educate him how to use the tool. Because of this challenge, we aren't using Process Capture right now.

I would rate this solution as eight out of 10. We are very satisfied with the solution.

Our primary use case is for SAP regression testing. We wanted to have our all SAP processes for regression to be optimized using Worksoft Certify. It took around one year for us to take that process and learn how it works, gradually improving it until now. 

We do regression testing on a weekly basis using Worksoft Certify. This does not include just SAP. We are also using the web-based tools when we are integrating end-to-end processes. When we are moving within one end-to-end process, we are shuffling between all the scripts and then going back to SAP. It works quite well.

At some point, we will have an RPA initiative to use this solution. For example, we need to obtain data from our development environment to check reports and verify them, then create transactions using Worksoft Certify.

We have more than 160 end-to-end processes. In our repository, we can have one transaction process or more than 40. There are big end-to-end processes and there are smaller ones. There are processes that can take hours to run and there are processes that can take a couple of minutes to run, but most of the end-to-end processes have multiple transactions. In weekly/monthly releases, we don't have any type of manual testing. We are just relying on Worksoft Certify for its test automation.

We also use Worksoft Certify for test automation in projects.

For scheduling, we are using an Execution Manager from Worksoft Certify.

Our business and IT users have been able to use the Capture feature, even without knowledge of testing tools. We have different IT people from each business area, like production planning or material managements. These people, without even having any knowledge of programming or Certify, just need to know how to use Capture. They are using it because it's really easy to use. You just have to initiate a Capture and do the same work that you are doing every day. Then, Capture will record everything.

You don't need to do any coding when creating end-to-end processes; it's a codeless because it is just recording. We don't need a specific person (or multiple persons) to work with the processes to do coding for the automation, which saves time. It increases the confidence of the process owner or IT person working on it because we provide them the capability to record their own process without doing any coding and just using Capture. They are confident that whatever they have recorded is their own process. It's not someone else recording their processes. The test automator can polish that process, but we are not recording it since they initiated the Capture. Overall, this saves time.

It has reduced our test maintenance time by more than 50 percent because we don't have to do manual test processes. We have saved over 150 man-hours monthly. It has increased our delivery times. We went from 200 man-hours down (three weeks work time frame) to approximately 40 man-hours (three days work time frame).

Using Worksoft Certify, we have found and repaired more bugs, though not that many. Users cannot manipulate information during the process. We schedule our tests at the night time and leave them working. Next morning, when we come into the office, we just check our system. These tests are pass and fail. For the failed test, we have screen captures where we can go and check the screenshot to know what the issue is. No one has to sit in front of the screen when you are running regression tests or scheduling them. I can schedule them and continue with my other daily routine work.

It is really good if you are using Capture in the new version of 11, where you can have a visual of the capture. The new version is much better. If I am using the Capture, I just initiate the capture and start working normally with my transactions. Capture will start recording all the steps that I'm working with. Before sending that one, I can even edit the capture. I can add more steps or remove them. This is one of the best features that Worksoft Certify has.

Worksoft Certify is really easy to use. You don't need any programming skills. If you just know a bit about programming, then you can easily use it because most things record by themselves. 

It's fully capable to automate testing for packaged applications, like SAP and Salesforce. You can do whatever you want and even create one specific process. For this process, you can create multiple processes. For the one transactional process that you have automated, you can utilize that process in multiple other processes too. 

They have different tools for different types of documentation, like Certify and Analyzer (for business processes). In Certify, from the repository, you can get really good, detailed documentation of what has been recorded, how it works, what steps have to be taken, and what data to use for every step. From a documentation point of view, it is valuable and can be used for future training.

Worksoft Certify's ability to build tests is really easy. You can build as many tests as you want with Capture. It is very reusable to apply one process to multiple processes. 

The scripting methodology is easy to learn. It is easy to maintain because it is presented in a simple, narrative way. You don't need to know programming.

When you are using an older version of Worksoft Certify, like version 10, Capture will be running under your status bar. Then, you don't know what transactions you are currently recording. In the old version, you don't have the visual of the capture.

It works well with other tools, but there is some integration required with Solution Manager. If you are using test repository in your solution manager, then there is no direct integration between Solution Manager and Worksoft Certify. 

There is an improvement needed in the reporting within Worksoft Certify. We have either a detailed report or a summary report. We don't have report that can be used for training purposes. A different tool from Worksoft has to be utilized for this.

Worksoft Certify needs a bit of improvement for its web-based processes. It can be difficult because you need to recall the maps, then you still have to add-on for your browser. When you are using the browser-based testing, you cannot even move your mouse or do anything on your system when you are using the web-based testing. Therefore, it needs a bit of improvement on that side. While it does work, it needs improvement. From the SAP side, there is nothing better than Worksoft Certify. However, from the web-based, we are moving towards Fiori. SAP will soon be totally web-based. For Fiori, they need to be great with SAP testing. Thus, Worksoft has to improve the web-based testing part for Certify.

They have a lot of versions coming out every year, like four or five versions. They need to reduce this number. There should be one or two versions every year with add-ons, if necessary. Because if you want to upgrade your Worksoft Certify from an older version to a newer version, you almost need to reset the solution and we don't have that much time. We cannot dedicate four times a year to having the newest version of Worksoft Certify. Though, if I don't need the need changes or improvements, I can skip the most recent upgrade until the next version comes out.

Almost six years. We started launching it in 2014.

It is very stable; nothing happens.

Two people are responsible for maintenance, deployments, and updates: the test automation administrator and the test automator. One is mainly responsible for all the administration and maintenance of the scripts and everything that goes into the integration with SAP Solution Manager. The other guy mostly works with the execution of the script. 

The solution enabled us to scale up testing because we don't need to use manually testing. We are also using it for project testing. 

There are overall 12 to 13 users. We have three users identified for test automation. We have another 10 users who use different packages from models of SAP. They use it to capture their processes.

If you have any issues, cases, or discussion, you can go on the Community portal and ask from there. They have people and technical experts there who can provide you with solutions. It's one of the best things that Worksoft Certify is doing. You can discuss with others at different companies, or possibly the technical experts from Worksoft Certify if we have an issue. Then, we can open a case directly there. 

I would rate the technical support as a nine out of 10. They are very good and available at all the times. The technical support can assist through the Community portal. You can also email them directly. Their response time to contact you back is 24 hours.

Before Worksoft Certify, we needed almost two weeks or more of regression testing to move our changes from regression to production. We were spending more than 10,000 euros for that on top of our man-hours. Even then, it was not proper testing because the user could manipulate things because they were using manual testing. For example, if something was not working, they could try to use some other way to work it. After the implementation of Worksoft Certify, we have increased our scope for regression and have more than 162 processes from all the models. We have also increased the test coverage and have less issues.

We went from two weeks and 200 man-hours to three days of testing. Within three days, we can test for the monthly release. For the weekly release, we need maybe one day or less using Worksoft Certify to test our releases and move them to production. It has really improved the collaboration between teams and our dependencies between various processes. On top of that, it provides really quick reports and results for management. We are capable of providing quicker reports and results for regression, like, "What has happened? What has gone wrong? Is everything okay to move to production?" Management is also very happy with it because it is saving time and money.

I was not involved in the process.

We have seen ROI with its efficient reporting and ability to provide results to management. It has also increased collaboration between different teams, such as, purchasing and sales.

We have used Worksoft Certify as an RPA tool when we have needed to create the master data or upload some documents. This saves a lot of time. It can reduce 10,000 transactions from weeks down to a day and a half.

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.

It is integrated with SAP. It's one of the best tool to be used if you want to automize your testing for SAP. No other tool is as good as Worksoft Certify.

I have evaluated other tools, but I find Certify really tops them. Most of them are using the command line-based tools. With some of them, you need a expert who knows how to do programming. For Worksoft Certify, you don't need programming skills. For the SAP GUI, I haven't found another tool that can work as efficiently with SAP as Worksoft Certify does.

You just have to be clear about your processes and define them before going to capture one. If you capture some processes, you can just easily manipulate and merge them to the other processes. It is really easy to use Certify, but you do need to be focused. There is also integration with Execution Manager, which can be useful when you are using Worksoft Certify for scheduling and other things.

It is not that easy to work with SAP Fiori as compared to SAP's GUI.

It can be used with non-SAP platforms. 

Overall, the solution is a nine out of 10. For just the SAP GUI, it is a 10 out of 10. For the other tools, like the web part and Fiori, it is about an eight out of 10.

I primarily used the platform for SAP projects.

From a functional perspective, I found all the solution features quite useful. Excel automation was a valuable feature that was much more efficient than working with record sets. Using it helped significantly reduce time when dealing with large datasets. 

Another standout feature is the ease with which a non-coding professional can be trained to use it for automation. The codeless automation feature, especially for SAP applications, made the process simpler and more efficient.

The product could be improved in terms of web applications. One challenge I faced was that web application parameters often change in the back end, affecting the automation scripts. Small changes in the HTML page design can impact the automation process, unlike SAP, where the script remains stable unless there is a functional change. Therefore, maintaining automation for web applications requires more effort.

If my script is long and involves a large data set with over a hundred entries, it can slow down or become inefficient. I suggest improving how the platform handles large datasets during lengthy scripts.

I have worked with Worksoft Certify for over five years.

Worksoft Certify has good integration capabilities with third-party tools. For instance, I successfully integrated it with Excel and PDF. Although I haven't used the mobile features, it supports desktop applications well. In my projects, especially SAP, it handled invoicing and PDF verifications seamlessly. 

It is a codeless automation tool. It allows even freshers to be trained and become productive within a month. Regarding project cost, having a senior resource oversee the automation is feasible, while junior resources can handle the bulk of the work. Although it is a licensed product, it significantly saves time and effort, especially with its internal tools that allow testers to capture and automate steps efficiently.

Overall, I rate it a six out of ten.