Worksoft Certify Reviews

For my team the most valuable feature of Certify is its flexibility and ability to include logic in the test steps. Our previous test tool could only handle linear test processes.

The build/maintenance times for testing are much faster. It also allows us to build tests for applications our previous tool could not do.

The faster build times allow us to respond quickly to ad hoc requests from customers that were not possible previously.

The user interface isn’t the best. It is functional, but the different areas look too similar so it is not immediately obvious which module you are in. It does get easier as you become more familiar with the application.

We have been using the solution for seven months.

We have seen one issue, but it is minor and reproducible so it is easy to work around and only appears in a very specific environment.

We did not encounter any issues with scalability.

The technical support is great. It is very fast with a friendly response. Everything from the initial install to tickets is handled quickly.

Our previous tool couldn’t automate many of the applications we needed to test. Certify also allowed us to increase the number of tests we could maintain with our current team.

The setup was straightforward. We are running fine on a single applications server that houses the database and license server. The clients themselves have almost no configuration.

I was not involved in the pricing negotiation.

We evaluated Tricentis and Selenium.

Expect to include some funds for training or have someone in the QA group who is familiar with the product.

You can start making simple tests immediately, but to fully utilize the tool you will need someone with experience. It also requires some organizational discipline.

The tool is extremely flexible and can fit whatever process your team wants, but everyone needs to know and follow the process or you will end up with a confusing tangle of tests and data.

All the different kinds of recording features (learn) on the different technology platforms such as Java, SAP, and HTML are its most valuable features.

It facilitates 80% of our regression tests.

We have had problems with an external cloud service (technology is Adobe Flex).

I have used this solution for two years.

There were no stability issues.

There were no scalability issues.

The technical support level is quite high. We are very pleased with its flexibility of services and response time on issues.

Previously, we just had manual testings.

We had quite a slow implementation. The process has given us time to learn and do things in the right way. We have also received good support when we experienced any issues.

The consultant's rate is very high but Worksoft is quite flexible.

We did do a PoC and compared it with other products from SAP and HPE.

Take your time, do a business case and plan from the beginning as to how your organization will work with the test automation.

In the beginning, there will be different technical issues between Worksoft and your business application, which will take some time to fix. You also need good internal support from the people who know the business application. Support from the managers is a must.

Provides capabilities in testing SAP ERP. It’s easy to create test cases/processes using Capture/LiveTouch functionality.

We have been able to increase our overall testing maturity and test automation coverage. We have a large ERP program ongoing which requires a lot of testing. Our goal is to automate the majority of system integration test cases with Certify. This brings efficiency and quality to the program and also supports the continuous services in the future (less time needed for regression testing).

Testing of web based applications can be really cumbersome at times. But this is partially due to the way the applications themselves are developed.

We have been using this solution for one year.

In terms of stability, the new version (9.0.3), especially the client and its UI, seem more sluggish compared to the earlier version (9.0.2).

There were no scalability issues.

We have not used Worksoft’s technical support so far. We have been in “project mode” and received direct support from Worksoft team related to configurations and also for our version upgrade.

We didn’t have any other tool in use.

The initial setup was straightforward. Afterwards, we also setup Certify on the Citrix environment to be used by our partners.

What do you advise others about pricing and licensing? We will have a large number of users so we chose an enterprise license.

Plan your training schedule well. The tool is pretty easy to learn, but you will need some weeks of hands-on usage before you learn to use it efficiently. We had a too long break between the first trainings and the actual start of using the tool.

A lot of the features in Certify are valuable, but a few of those are very useful and make automation easier.

The Content Merge feature allows us to copy the Certify items from one project to another, either in the same database or in a different database. The feature set of Content Merge allows several abilities, so as to control the behavior of copying these items from one project to another.

The Recordset and Layout features help us in increasing the test coverage and reducing the test cases count in a simpler way.

Other features such as Certify learn, HPE QC integration also come in handy.

SAP automation was very easy with Certify; it reduced the automation time and also, the creation of the test cases was easy.

Web automation can get a little better.

I have used this solution for two years.

As of now, there are no stability issues.

As of now, there are no scalability issues.

I would give the technical support a 3/5 rating.

I have used Tosca Testsuite before moving over to Worksoft Certify. It depends on the client's requirements that we move over to different tools. So, nothing is specific.

It was a little difficult for installing, but the setup was not complex.

I am sure on the pricing part for Certify. One will need to connect with the Worksoft team for that.

If you are working on SAP automation with Certify, then it’s the best tool to work with. Other technologies too work well but are not that stable.

In the near future, I guess everything will be sorted out and this will be the best automation tool.

Certify and Analyze are the most valuable features.

It has greatly improved testing time and has found defects before production.

• Better Silverlight automation

I have used it for a little over a year.

I have not encountered any deployment issues.

I have not encountered any stability issues.

I have not encountered any scalability issues.

Customer service is good.

Technical support is good.

We did not previously use a different solution.

Initial setup was straightforward.

We worked with a consultant for implementation.

• Expanded test coverage/fewer defects

It is good for it's price and functionality.

Before choosing this product, we did not evaluate other options.

It is a great product with a good team behind it.

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.

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.

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.

I have been a test automation developer since about 1992, but with Worksoft Certify since Jan 2000, just over 17 years.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

It has ability to execute the scripts without any manual intervention. It has ability to run scripts overnight without any human intervention (lights-out testing), which proves to be vital in providing wider coverage in a short time.

We are able to scale up the testing and to address more business-driven projects using Worksoft, which would not be possible with any other tools. The testing organization can cut short its budget, as it is not required to hire more testers for regression testing.

Upgrading Certify takes a lot of time and effort, which is like a small project by itself.

I have used it for two years.

We have not encountered any deployment issues.

We have not encountered any stability issues.

We have not encountered any scalability issues.

Customer service is 4.5 out of 5.

Technical support is 4.5 out of 5.

We used to use QTP, but the ability of Worksoft in the SAP automation space compelled us to make the transition.

Most important feature is the ability to automatically perform test without the need of a manual script, it's very fast and can perform overnight testing without human intervention (Lights-out testing). It can perform automated end-to-end validation across application landscapes.

Organizations does not need to hire numerous resources to perform regression testing, therefore, cutting overhead cost at a substantial level.

It uses a sizeable space for its database, therefore requires a regular cleanup in the server's space. Secondly, upgrading of its version requires enormous time and effort, that it's like a mini project. It could impact testing phase if not managed well. Technical support sometimes requires access to client's server, which is not allowed for some clients.

Three years.

No issues encountered.

No issues encountered.

No issues encountered.

9 out of 10

8.5 out of 10, it is quick to respond, but takes time to resolve on some issues (related to #6).

There was no established solution and testing was being done manually.