Worksoft Certify Reviews

We have been using Worksoft Certify for ten years.

We do automation of both SAP and other applications: One of them is our new grants management system. Originally, they wanted to do everything manually. Now, they highly rely on us to do testing in very short periods. 

We do web UI testing of modern applications. In our environment, we have SuccessFactors, plus SRM through Fiori. 

We also do performance testing and end-to-end testing of packaged applications, like SAP, InfoEd, and OnCore.

The most valuable features right now are the Capture capability and versioning. The Capture 2.0 has a lot of flexibility.

The easy of use and ease of integration of Worksoft Certify are very good.

We are looking for some enhancements on the Capture 2.0 tool. This would give us the ability to control it directly, like we could with Capture 1.0. Right now, Capture 2.0 doesn't really work for our Business Analysts. Because they don't work with it all the time, it's a little complicated for them to stay up to speed on it. With Capture 1.0, we wrote a wrapper to make it easier for them to use, but we can't use that wrapper with Capture 2.0. So, if Capture 2.0 gets enhanced, we'll start using it. For an enhancement, we want to be able to start and stop recording through an API. Then, we want to see how many steps have been recorded through the API.

We do a lot of test maintenance because they are constantly changing the applications. This is one of our biggest problems that are constantly making changes and switching products. For example, we used to use the Supply Relationship Manager. Now, all those tests that we build there will be replaced when we go to Ariba. All the old SAP GUI stuff for HCM, when we got SuccessFactors was thrown out, then had to be redone with SuccessFactors.

It gives you the ability to have a more structured environment for tests. It is not just recording of key strokes. It is more systematized, more like a programming language. That is the biggest advantage for us. Because of its consistency, once the developers know one skill set, they can use it to automate any application.

It scales well. We have eight offshore people and four developers in New York. We can add developers as needed. With the offshore team, we've have at least 20 people trained on Worksoft, but eight people actively on the team now.

We have about a 1000 active users with about 5000 users total. However, this includes all of the employees and their self-service.

The technical support is very good. They have always been a great help. With a lot of companies, you can't even really talk to the developers that someones provides you. With Worksoft, you can get a hold of the developers and work with them. It is all very timely.

The initial setup was very straightforward. We just build the database and installed the client application on the system. There was nothing out of the ordinary about it. It is not like setting up a lot of the IBM products or the Quality Manager, where there were so many different modules. There was just one module to set up.

During our yearly upgrades, we have now gotten them down to ten days or less. We have Worksoft run all our integration tests, where it used to take probably six weeks to do that manually.

As far as maintenance testing, it has saved us time. We find problems a lot of the time that they aren't aware of. This is because we run the tests even though they don't ask us.

We evaluated Micro Focus QuickTest Professional (QTP).

Properly staff the testing team before they attempt to do automation. Be aware that this will not be a one-time overnight process. We tried to automate everything in two months with eight people, and it was impossible.

We have been using it for so many years that we are really very happy with it.

We will be converting to Ariba for purchasing, so that will have to be automated.

We use it for SAP and ERP. I think from the SAP and ERP point of view, it is very good.

When we used it for web based application, so it was quite poor.

One, it's module based and it's giving functionality. That is, first of all we can really implement it as an ERP (Enterprise Resource Planning). We can utilize our concept and our functional people to work with the tool and without having a lot of technical knowledge, so they can really work with the tool with small technical knowledge. So that's really a big thing for us. We can use the tool with our existing people so that we don't need to have a new technical expert using the tool.

It is poor for a web based application. We are living in very integrated organization are most of the companies out there. There's the big companies we have these organizations that we work with, where we have plenty of different services which are very much connected. So, we are really looking solution which really can support all the different services. We really need to focus end to end instead of stand alone case. 

Whatever reportings are there, so they're really not very user-friendly. So there is a lot of technical data instead of user-friendly data. It would be wonderful to add web support, I would really like to see this in the future.

If I would evaluate it on a scale of one to seven, I would give it a seven. 

It's not very scalable. 

They struggle to provide an accurate solution.

I think it was not really very difficult. It was quite easy to set up the tool. The architectural tool was really easy.

We define certain different criteria. We check if the vendor is giving support for the tool, and we also evaluate the price. Of course, we also take note of the ROI of the solution.

This product is a good one, if you are really focusing as an ERP. We really need to have a solution which is really end to end rather than just focusing on key product. It's good to be aware if there something that can support you end to end rather than one specific product.

When talking about continuous testing, so then the tool is not really good at all because you need to purchase some additional tools. For example, the Execution Manager and  other tools, which are an additional cost. 

Another added cost is the payment necessity for reporting.

We are using it so far for regression testing. We have reduced 5% to 10% of regression related issues. This is a huge impact on our organization. So that's really quite good improvement in our eyes.

Speed at which it processes our testing scripts, detail of testing results for audit validation, documentation can serve as training document for new employees.

Prior to implementing Worksoft for our testing, the scenarios required eight employees over two weeks to complete (waiting for hand off of next steps, employee availability due to meetings, etc.

After implementation of Worksoft, the same test scenarios currently run in approximately 45 minutes – hands free! We have also implemented Worksoft into our SOX Control documentation processes.

Approximately seven years.

No.

No.

Excellent. They always went above and beyond to timely support our needs

Setup of the software was extremely easy. Setting up the scripts was complicated at times (due to our customization of our SAP clients).

However, most routine transactions were handled with ease.

I am not familiar with the pricing or licensing fees.

No.

Make sure to be prepared for the amount of time it will take you to complete the testing scripts.

Have a dedicated team that performs your test script setup and execution of these tests.

Include your business users to ensure the processes are clear and accurately reflect their business processes, not what you think their processes are.

Well, obviously it's the test automation piece of it. Creating our scripts and being able to execute our SAP scripts in order for us to be able to do comprehensive regression testing of our SAP system.

Well, it's definitely reduced the number of defects that we have. Before, when we were manually testing everything, it was unclear to us where changes that we were making, where the impacts were in our system. I mean, we've got very smart people that work here, but they were not 100% on where the impacts were going to occur with their changes.

By automating our scripts, we were able to do more comprehensive testing and therefore eliminate the number of defects that were be introduced into our environment.

There is an impact assessment piece to Worksoft. I think that's one of the pieces that we still struggle to use.

What the tool does is, you can analyze a transport to know where your impacts are. I think that's one of the challenges that we still have -- is just getting a better handle on how to use the Impact Assessment better for us.

In our regression testing, all that, we've got a pretty good handle on that. We identified things. When we run the analyze of a transport, we're not...we've found other ways to do things better.

Four years now.

No. It's been very, very reliable. The only issue, we've virtualized everything. I think the only thing, the only real issue we encountered was with our virtual machines. It was not a Worksoft issue.

It was on our side -- once we worked with our sys-admins to investigate what was going on, they were able to resurrect the issue and we were fine. It was not a Worksoft issue at all. It was something with our virtual environment.

It's been very scalable for us;

Depending on how many licenses, it's all seat licensed. It's not a concurrent license. If you don't have people logged in, more people can't use your licenses from your pool.

You assign those licenses out to people and as you continue to grow, like I was talking about with our virtual machines, we do everything in a virtual environment for all of our Worksoft work.

As we've needed more virtual machines, we've got an image of our Worksoft clients and we just add them into our environment.

3 out of 10 -- You submit an email, so there's not really a hotline that you can call to talk to somebody on the other end.

I had familiarity with several tools out there. Turnkey is probably one that you guys have looked at. I've done a lot with the quality center products in the past...Quicktest Pro.

There's other test automation tools out there. I've got a background with test automation and Worksoft...really it was between Worksoft and Turnkey. Worksoft, we just found ,was going to better meet our needs.

Yeah. That was actually pretty straightforward. When we set up our environment, they gave us a technical support person that really walked through with our system administration team to get everything set up in our environment.

As far as training, they have a very comprehensive training program. I'm sure it's all ... I'm sure it's very good. What we did and what helped us to be very successful is we went through and did live test cases as part of our training.

Instead of spending all the time going through the books and learning the tool in and out, we went through and we got right into creating our test automation with the trainer that they sent out. That hands on experience was, it was priceless. It helped us to be successful and get going with creating all of our test automation.

Make sure...before you start any of your test automation, make sure you have the appropriate support from your business.

What I mean by that is, you have all of your business processes documented. There is a lot of prep work that goes into creating your test automation to make sure you're creating...you're creating your scripts in the most efficient manner. A lot of this testing is done based on your business process. You need to understand your business processes.

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.