What is our primary use case?
My main use case for Worksoft Certify is to automate end-to-end SAP business processes, particularly in the order to cash and procure to pay areas. I used Worksoft Certify to build reusable process units for common steps like login, master login, master data entry, and document creation. This helped us create a scalable regression test suite that was executed during every release cycle to validate critical business flows such as sales order creation, delivery, building, and invoice verification. This significantly reduced manual testing effort and improved regression coverage.
What is most valuable?
What stood out the most about Worksoft Certify was the stability of the automation SAP environment and the ease of maintaining tests even after UI changes. Compared to other tools, we spent much less time fixing broken scripts after updates.
Worksoft Certify handles UI changes well because it relies on stable technical object properties and maintenance object definitions centrally. When UI changes occur, we typically only need to update the object in one place instead of modifying every test case, which significantly reduces maintenance effort.
In addition to its core automation capabilities, I found Worksoft Certify's reporting integration and enterprise test management features very helpful. The execution reports provide detailed step-level results and logs, making it easier to analyze failures and share evidence with stakeholders. I also appreciated its integration with tools like Jira and Micro Focus ALM, which helped in seamless defect tracking and test management.
Worksoft Certify has positively impacted our organization by significantly reducing regression testing time, improving test coverage, and increasing confidence in SAP releases. It enabled us to validate critical business processes more effectively, frequently, and consistently, which led to fewer production issues and smoother deployments.
Worksoft Certify made a very noticeable difference in our regression cycle time. Before automation, our regression testing for critical SAP processes typically took two to three days with multiple testers involved. After implementing automation, we were able to execute the same regression suite overnight, usually within four to six hours. This allowed us to validate releases much faster and more frequently.
What needs improvement?
While Worksoft Certify is strong in SAP automation and end-to-end business process testing, there are areas where it could be improved. For example, object identification and handling dynamic web and Fiori applications can sometimes be challenging, and debugging complex processes is not always as intuitive as in script-based tools. Enhancements in these areas would make development and maintenance even more efficient.
In addition to object handling and debugging, I believe Worksoft Certify could be further improved in areas like tool integration, reporting flexibility, and overall user interface responsiveness. While the existing features are strong, enhancements in these areas would make the tool more efficient for large enterprise teams.
I would rate Worksoft Certify around seven out of ten because it is a very strong tool for SAP automation and end-to-end business process testing. The reason I do not rate it a full ten is that there is still room for improvement in areas like UI responsiveness, reporting flexibility, and handling of highly dynamic web elements, especially because of its scriptless approach, reusable components, and stable object identification.
I chose seven out of ten because, while Worksoft Certify is strong in SAP automation and end-to-end business process testing, there are a few areas where I experience limitations in day-to-day usage. This includes UI responsiveness when working with large projects, the effort required to stabilize object identification in dynamic web and Fiori applications, limited flexibility in reporting customization, and there is more room for improvement in API automation testing. Although this did not prevent us from achieving our automation goals, it affected productivity and maintenance support, which is why I rated it lower than eight or nine.
For how long have I used the solution?
I have been using Worksoft Certify for two years.
What do I think about the stability of the solution?
Worksoft Certify has been a stable and reliable automation platform, especially for large-scale SAP regression testing. We were able to run unattended overnight execution on large regression sources without frequent crashes or tool failures. Most of the issues we encountered were related to environment configuration, system performance, or test data rather than the tool interface.
What do I think about the scalability of the solution?
Worksoft Certify handled our growing automation needs quite well. As our SAP landscape expanded and the number of regression scenarios increased, we were able to scale our automation by adding more process units, reusing existing components, and integrating with centralized execution. The platform supported larger test suites without requiring a redesign of the automation framework.
How are customer service and support?
Overall, my experience with Worksoft customer support has been positive. Whenever we faced issues related to execution errors, environment configurations, or tool behavior, we were able to raise tickets through the support portal and typically received timely responses. Complex issues were escalated to senior technical engineers who were knowledgeable and helped resolve them effectively.
Which solution did I use previously and why did I switch?
Before implementing Worksoft Certify, our team used a combination of manual testing and a traditional automation tool more focused on web applications. However, as our SAP landscape became more complex, we faced stability and maintenance challenges. We switched to Worksoft Certify because it provides native support for SAP technologies, a scriptless approach, and better handling of end-to-end business processes, which significantly reduced maintenance support and improved reliability.
How was the initial setup?
Worksoft Certify has positively impacted our organization by significantly reducing regression testing time, improving test coverage, and increasing confidence in SAP releases. It enabled us to validate critical business processes more effectively, frequently, and consistently, which led to fewer production issues and smoother deployments.
What about the implementation team?
Our organization evaluated a few other automation tools to determine the best fit for our SAP landscape before finalizing Worksoft Certify. The tools we reviewed included OpenText UFT, UFT1, Selenium, and Tricentis Tosca. Each tool had its strengths, but Worksoft Certify was selected because it offered stronger native integration with SAP, a scriptless approach, and better support for end-to-end business process automation.
What was our ROI?
We did see a clear return on investment after implementing Worksoft Certify. The biggest impact was on regression cycle time and resource utilization. Before automation, our regression testing for critical SAP processes required around six to eight testers working for three days. After automation, the same coverage was achieved with one to two testers overseeing automated runs that completed overnight, significantly reducing both education time and manual effort.
What's my experience with pricing, setup cost, and licensing?
From my experience, the pricing and licensing model of Worksoft Certify is typical for enterprise-grade automation tools. The setup and licensing were handled primarily by our organization's procurement and infrastructure teams, but from a user's perspective, the onboarding and access provisioning were straightforward. However, compared to open source or lighter automation tools, the licensing cost is higher, which means organizations usually adopt it when they have a large-scale SAP landscape and need robust enterprise-level automation capabilities.
Which other solutions did I evaluate?
Parallel reporting at scale has had a positive impact on the speed and efficiency of our reporting processes. Earlier, when large regression suites were executed sequentially, generating consolidated reports took considerable time and sometimes delayed stakeholder updates. With parallel reporting enabled through a centralized execution and reporting mechanism, we were able to process results from multiple test executions simultaneously, significantly reducing reporting turnaround time and improving visibility for the team.
What other advice do I have?
One impactful automation I implemented with Worksoft Certify was for an end-to-end order to cash process in SAP. We automated the creation of sales orders using VA01, followed by delivery creation with VL01N and billing in VF01. Using Worksoft Certify, I created reusable process units for login, master data entry, and document validation.
I automated this web application process as part of the business process. Once I finished automating the applications, I was able to integrate with the SAP application and the web applications to test whether the data flow and data integration were working properly.
For the order to cash regression suite, we automated around seventy to eighty percent of the high-priority scenarios.
In my previous project, Worksoft Certify was deployed in an on-premises environment. The Certify client was installed on dedicated education machines connected to our internal SAP system within the organization's network. This setup ensured secure access to business-critical systems and aligned with our company data security policies.
I have experienced using the impact analysis capability to identify which automated processes were affected when there were changes in the SAP environment. It helped us trace dependencies between the business process test cases and application objects, allowing us to focus our regression testing only on impacted areas rather than executing the entire test suite every time.
Based on my experience, I would advise organizations to approach Worksoft Certify not just as a tool but as a business process automation platform. Success with Certify depends heavily on proper planning, process design, and governance rather than only technical scripting. A team that invests time in designing reusable process units, maintaining consistent naming conventions, and defining strong test data strategies sees the best long-term results.
Overall, my experience with Worksoft Certify has been very positive, particularly in the context of SAP automation. The tool's scriptless approach, strong SAP integration, and ability to automate end-to-end business processes made it a valuable asset for our regression testing and release validation. It helped our team improve test coverage, reduce manual effort, and execute tests more consistently across releases. I would rate Worksoft Certify seven out of ten.
Which deployment model are you using for this solution?
On-premises
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other