What is most valuable?
Parameter-driven action steps (no programming): Able to interact with all application objects, as well as execute all logical, mathematical and text manipulations, with clearly defined parameter-driven action steps. These features, and the basic structure and framework, eliminate the confusion of building a framework for every test. The framework is inherent with Certify.
Certify is built on a database where all components are indexed for easy usability and reusability. This concept is difficult to manage with most other tools where tests and components of tests are very possibly on different servers, workstations, and folders.
Process and data RecordSet coupling feature: You can import lengthy spreadsheets and, with the framework of Certify, then extract only test data needed by attaching that one imported spreadsheet RecordSet to your executable process and, with just one action step in the process, write to the RecordSet, and build only the test data you need. This feature of a Certify process does automatically read and process the next row of data in the spreadsheet RecordSet without any programming. And the feature of a Write action will write all the variables associated with a RecordSet with just one write action step.
Point and click on application objects will automatically create an action step referencing the Object's Attributes and with a variety of actions automatically promoted for selection based on your application object type. This means minimal guess work on how to interact with an object.
Easy transition during execution between application development disciplines. Go to SAP, Web, Java, mainframe, or any discipline, all in the same test execution.
Easy interaction with DOS files during execution.
How has it helped my organization?
Of course, one of the benefits is, we are able to complete and maintain more automation.
The biggest benefit for me has been that, because the automation is basically 'event-driven-executable-documentation', it has been easy to enhance my lengthy end-to-end tests with restart capability.
It has also been easy to create automation as part of the test to find, or create data as part of the test execution. This has enabled us to instantly run a test again without the delay of manually finding and populating input RecordSet data. When you are on the clock to complete regression testing for production implementation, this is critical; that you don't have any delay to rerun.
What needs improvement?
Certify has been in perpetual improvement mode since it's inception.
Although I don't think it would be easy, being able to edit and change an action and logic flow in mid-test execution would be nice. Of course, with event-driven execution, this would be a bit of a reach.
I’m not an expert on compliers however I do have a background as an Assembler coder. I believe most applications now are event driven and most, if not all, automation tools are Interpretive, compiled at execution time. Certify is Interpretive as well as having only parameter driven source (no programming syntax). During execution, the processer is using the Interpretive version of each step, not the actual source created by the developer. Linking back to that original source and maintaining executable sync and content would be a stretch. This is not a restriction of Certify but of any Interpretive complied automation tool. Certify does have a feature to execute just portions of its source, during editing; however, I believe that is more manageable than interrupting execution to then edit the source.
I found it difficult to conjure up enhancements to this tool possibly because I have intimate experience with Certify and have always found success using one or more features. However, there is one enhancement request that might have merit. Allow a Variable to be used in the Label parameter of the Execute Process Action. Certify has an Action step ‘Execute Process’ that has a Parameter for ‘Process Name’ and a Parameter for ‘Label’. This Action allows you to execute a sub-Process and begin that execution at any Label in the sub-Process. The Parameter for ‘Process Name’ can be a Variable containing the name of a sub-Process which can be changed based on application and logical response during execution. However, the Parameter for Label cannot be a Variable. If it could, it would provide yet another nice structural feature of Certify.
For how long have I used the solution?
I have been a test automation developer since about 1992, but with Worksoft Certify since Jan 2000, just over 17 years.
Buyer's Guide
Worksoft Certify
January 2026
Learn what your peers think about Worksoft Certify. Get advice and tips from experienced pros sharing their opinions. Updated: January 2026.
881,114 professionals have used our research since 2012.
What was my experience with deployment of the solution?
Because of the unique framework of Certify and the extensive object, math, text and logical parameter-driven actions, there is nothing I haven't been able to accomplish with Certify and all without traditional programming or scripting.
What do I think about the stability of the solution?
Of course, with experience, you learn that most of the stability issues are environmental; meaning, it is usually the environment that has had to be tweaked.
I have had once where a threshold has been reached in the database for updating a component, but that basically took a phone call.
What do I think about the scalability of the solution?
Worksoft has done a good job keeping abreast with browsers and various different development disciplines. In addition, database size has never been an issue. In fact, as test automation requirements have grown, being built on a database has certainly enabled better management of the automation reservoir of tests, as well as all the components, discipline interfaces, requirements, results, users, security, etc.
How are customer service and support?
Customer Service:
Customer support is always cordial and helpful. There is an annual Certify User Conference, where you get to actually hear presentations from customer support, technical support, and experienced users. You can actually meet and speak with the members of technical support, engineering and management on any issues.
Technical Support:
Early on, I needed math capability and literally within a half hour, I was sent an update to allow math using a specific Set action. Now Certify has extensive math, data math, and many other numeric and text manipulation actions. Of course, since Worksoft has grown, they have instituted a formal way of communicating, which has been very successful. I am able to report any issue with an immediate response that it is being forwarded to the appropriate engineer. If I have a high priority, I get immediate attention. That has happened once during a release update, which was addressed and handled within 24 hours, and it was caused by an in-house, user-developed map.
Which solution did I use previously and why did I switch?
As mentioned, I evaluated Certify against a tool I was using, AutoTester. I was also using WinRunner, Rational Robot, and Seque's Silk at the time. Those names have changed over the years. However, it was immediately evident that none of them could compare even closely with the productivity I could get with Certify. Also, because there is no syntax involved with Certify, process and actions are more like executable documentation, making maintenance much easier.
How was the initial setup?
Initial setup is pretty straightforward now. Early on, I used to write my own .bat files for the install. Now, they have good documentation and you can either use a .exe or .mis file for the install and upgrade. And, I have found that support is available immediately during any installs or upgrades.
What about the implementation team?
Because I have been using Certify for so long, I do my own implementation, except for local DBA support for the database. However, for brand new implementations, Worksoft has an excellent professional team for just that purpose.
What was our ROI?
I can't give you any specific dollar amount on the fly but, for instance, I was at the Certify Users Conference in the fall of 2016 and the manager from AAA Southern California mentioned that the system I architected and developed for them while training two of there business analysts back in 2006 is still being used. The system is a mainframe system for applying for insurance with quite involved requirements.
ROI tends to be substantial because business analysts can be trained in just days to be effective with Certify. With almost all other tools, you need programming experience.
What's my experience with pricing, setup cost, and licensing?
Cost is always based on need. I haven't found a vendor that could give me a straight answer unless I just wanted one or two copies of a software. And, of course, the more licences you need, the more cost reduction per seat you can get.
Which other solutions did I evaluate?
Before choosing this product, we evaluated other options, as mentioned. We were using more than one other tool at the time at Charles Schwab and we chose Certify for it's flexibility, quickness in development, and easier maintenance.
What other advice do I have?
During an R&D project to find a better automation solution at Charles Schwab (a major investment company) in January 2000, I evaluated Worksoft Certify. At the time, I had about 10 years’ experience using popular test automation tools. For the evaluation, among the considerations, I measured Certify against an automation project I recently completed. I took an IBM mainframe mutual funds order entry system I had developed with a different tool that consisted of about 10,000 syntax instructions to complete. I had been perfecting this for about one year. I used this in my R&D evaluation as a comparison. With Certify, I developed the same automation features in about 1/3 of the time and which consisted of only about 450 Certify parameter-driven actions steps. It was clear, and obvious, that going forward, development would be easier, much faster, and that maintaining 450 Certify action steps would always be easier than maintaining 10,000 syntax instructions typical with other tools.
I have been using Worksoft Certify now for over 17 years. I have Certify automation developed for HTML web, .NET, Java, PDF, mainframe, and the most beneficial, SAP. I have many test automation processes for testing SAP, including testing end to end SAP Material Management from RFQs, PR, role approvals, PO, goods receipt, payment, return product, to inventory validation. Since 2004, I continue to primarily focus on SAP test automation with Certify for easier and faster development, and easier and faster maintenance.
Is it easy to learn? Think of the concept that, with other tools, you need to develop a framework and architecture to then develop your automation in. With Certify, it is already a development framework. It is built on a database with all the features for test automation. It’s not a programming solution (no programming) just action steps with parameters against application objects and action steps with parameters for math, logic and text manipulation, etc.
And, yes it is easy to use and easy to learn. In 2016, I went to Mexico for Yazaki, the company I consult for (a major automation supplier). I went there to train two business analysts on using Certify for developing test automation for several Yazaki Web business applications.
One of the biggest benefits: I was there for only two (2) weeks and completed training of two (2) business analysts that have no programming background. Since then, they have been pretty much developing with Certify on their own, almost one year now.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Hello. How do we contact Support for Worksoft certify?