Worksoft Certify Reviews

Primary use case is for SAP support testing.

People focus on what they actually want to test and define it in a more detailed way. It shines a light on what they are testing, along with the speed and adaptability.

• Reusability
• Scheduling ability
• The modularization of testing: It brings a more functional level, as opposed to the technical level.

A feature that I am looking forward to in version 11 is a search capability, where you can search within the script themselves for keywords. That will be really helpful.

More than five years.

It is stable from an application standpoint. Sometimes, there is complexity within the virtual machines that they run on, or the hardware, depending on the configuration that their client has setup. Sometimes, this is a bit of an issue to overcome, but I don't see this as a Worksoft Certify issue.

If done properly, it's very scalable. It creates automation which can be run from an SAP point of view. I can create automation which runs in any SAP environment that I want it to run in, as long as the UI is the same.

Their technical support is very good. They have different aspects of technical support:

• If you're standing up a project, they can be with you every step of the way. 
• When you just submit a ticket, they'll respond to you and get back to you within their service level agreement.

Worksoft Certify's codeless scripting appeals along with the use of the Capture feature which helps in those initial phases. It also helps to translate the business requirements to the automation team. If there's a separate team, this is a little better too.

There is recognition in the industry that automation capabilities, like Worksoft Certify, create value for companies, as things are only getting harder and larger. Companies are integrating systems to try to align their processes.

The initial setup is relatively straightforward. The team helps guide you. The technical support is there. It comes down to the training that's applied, and having the people who understand the use of the tool.

The typical range that we see is between 50 to 90 percent improvement in speed capabilities. Another aspect comes with the depth that they're able to test. It increases their capabilities overall to test at a broader level.

Our customers often evaluate Tricentis along with Worksoft.

From an Accenture point of view, our customer chose Worksoft because of our alliance with them. It's the capability that we've built and the knowledge base that we bring along with that.

Capture 2.0 is good for new implementations or new processes. It's not as useful when you get into more mature automation. Its documentation and automation are fairly straightforward.

There is a bit of a learning curve around the Worksoft Certify tool. The best practices, which are lined out by Worksoft, as long as those are followed, then this leads you to understanding the tool and using it in a proper way. If you don't get started off on the right foot, it will be hard to course correct. So, it is vital that they get started on the right foot and understand the best practices. The product's learning curve is relatively good.

Automation is only as good as the functional knowledge that is used in order to create it. This tool works extremely well. Manual testing and automation testing are two different animals. You have to look at automation in a different way. Simply taking manual scripts and automating them, and you're not going to get the full value out of a solution like Worksoft that you could if you were to rationalize the testing and come up with an automated approach.

When you're manually testing, it's about having the least number of clicks possible. Every click for a human is time. With automation, clicks don't cost anything. You might approach the testing in a different manner. It would take a human multiple times longer, but with automation, it makes sense not only from that specific test case point of view, but also from a reuse factor. When you're going to use a certain business process that you've created, then reuse it for different work streams.

The primary use case is more on SAP for automating all our manual business work, as well as doing regression testing. We do end-to-end regression testing on SAP.

The product has worked very well with SAP.

Worksoft is used for manual processes that needed to be automated. This has helped us make our processes be faster and more efficient because there are no manual interruptions or errors.

For my processes, Worksoft makes them faster when creating scripts.

Capture 2.0 is a very good feature, on which we can record very easily and get documentation generation and testing acceleration. 

The product had some UI issues. In the next release I heard the UI issues will be lifted up (version 11), I am excited about it because the product will have more UI features. We are thinking of upgrading our existing Worksoft Certify from 9 to 11, when it is released, as this will be good for the company and help all our users.

The stability is pretty good what I have used sofar with SAP

The scalability is good.

The technical support is pretty good. If you open a ticket, they are able to answer it within 24 hours. They are able to support us.

We previously did manually testing and used other tools. With Worksoft, we can more see the productivity and benefits that it provides. We can also do more testing, making easier for all the users. 

We used the Worksoft for the deployment. They came and helped us. We have a good relationship with them.

Worksoft Certify is an investment. We see value in it more than the money. We see value in it because the user can look at different aspects of testing and what they can do.

This solution has enabled us to automate in order to tremendously save time. Only first time when you are recording and creating the script will you spend some time with it, the rest of the time, you are just executing. If we do one manual process, it could take approximately two hours. The same process using Worksoft probably takes ten minutes.

It help cut test maintenance time too. An eight hour manually project using Worksoft can be done in an hour.

Worksoft is good for SAP to do your automation and testing.

We are not using it for web UI testing.

The primary use case is regression testing and test automation.

We use this solution for end-to-end testing of packaged applications, like SAP, ServiceNow, and some in-house web apps (which we built).

We have already found some defects using the test automation. 

One of the bigger value-adds that we had was extracting data from our warning systems to be inputted into our new learning system.

We automated because of the value. Our business users do a lot of regression testing. They often don't have the time when we need to get the testing done, so this frees them up to do more value-added work for the company.

• Speed, as far as getting tests completed on time. 
• Its ease of use and the value of that. It is a lot easier to maintain test scripts on Worksoft Certify than on other testing tools that we have had in the past.

We have had run ins with some bugs on Business Process Procedure (BPP) and Execution Manager. 

We also did upgrade Worksoft Certify recently to clear up some issues with server fogging.

More than five years.

It scales pretty well.

I would rate technical support as a seven out of ten. Sometimes, we end up going back and forth with Level 1 support. Usually, if we go back and forth, it is email most of the time, and sometimes it is once a day with 24-hour turnaround. We usually understand what they require and trying to give as much information as possible. We still need to tell them to kick it up to Level 2 support or at least have a meeting with them, so we can show them what is going on. Sometimes, it does get a little frustrating, but once we either have the meeting or get Level 2 support, the issue gets resolved pretty quickly.

We had and still use QuickTest Professional from Micro Focus a little bit, but we were approached back in 2008 about getting into Worksoft Certify.

We went with Worksoft Certify because of its ease of use. You don't have to know a scripting language, like with QuickTest Professional. Also, it has ease of maintenance.

The initial setup was not really complex, just a little. We did not understand the full setup; it was just confusing. We really didn't get a full explanation of how things connected together until we actually started to use it. Once, we start using it, things became much clearer.

During the initial deployment where we received execution suite, the necessary information was not really provided. However, it was a fast deployment. We had to meet some deadlines, so people just came in and did the installs, or helped us do the installs over the phone, then afterwards we realized how things were connected.

We used Worksoft for the deployment, who was very good.

We have seen ROI by being able to free up and give time back to the business for other value-added work.

In 2008, we evaluated SAP TAO. The person who came in to do the proof on concept wasn't able to get the test scenario working at all. He had three and a half days to do it, and he couldn't do it. When Worksoft came in, they had the same length of time and were able to get that one plus another one partially working in the same time frame.

Worksoft generally seems to want to make sure you are successful at what you are trying to do. I haven't come across an employee from Worksoft that isn't willing to help. A lot of times you do get that from other salespeople, and that is just not the case from what I have seen from Worksoft. 

The product has a lot of benefits as far as getting testing done. It gives you some value back.

The company is using it across our IT landscape on different projects. We use it to test web applications, SAP mainly. Right now, we're doing a big conversion project. The one that I am working on is a big conversion from an old mainframe system over to SAP. Thus, we are using it to automate all the UAT test cases.

We have also used it in other areas of the company for ServiceNow upgrades and general web design stuff.

For this SAP upgrade or implementation, the business users are creating building blocks in their areas, then they're changing the building blocks into long end-to-end scripts to do a complete end-to-end testing to speed up the UAT. It definitely has a bigger coverage of UAT testing.

• It is user-friendly. We can give the tool to business users, and they're able to use the tool pretty efficiently without a whole lot of training. 
• The reporting features are nice. 
• It is easy to take someone else's work and manipulate it to use yourself. 
  
• It is not heavily code-based, so you can pick it up and automate very quickly.

For Execution Manager, I would like it to be more robust interface and be able to view the remote machines full screen instead of a little window. This would be a great upgrade for us.

I would also like more customized reports without having to print out big reports.

It is a very stable product. When we have had upgrades, it's been pretty seamless. Older versions of our scripts work in the newest update without a lot of rework.

It is very scalable with users. We have business users who are scripting. We have Worksoft developers who do more complicated work. Then, it moves over to the people who do execution and process through Execution Manager, so we have several different layers of users doing different tasks.

The technical support is very good. They are very responsive. When we have created tickets with them, there is usually a 24-hour turnaround time, then we are contacted back. Their interface is good for back and forth communication.

It is not practical to do manual testing anymore due to the volume of it. The amount of data variations is too great to test manually. If we were going to do it manually, we definitely would not have full coverage, where now we can get pretty close to full coverage on our tests.

When you are implementing Worksoft Certify, it is probably best to bring some Worksoft consultants in to help get you setup, and set it properly. Because if you don't get your initial systems, like your folder structures and your naming conventions, set at the beginning, there is a lot of rework to get it to work. We did have to go through that.

We save probably 50 percent of our time. The tool does what it's supposed to do, and we are able to actually work.

Worksoft Certify is a good product. The customer support is really helpful and supportive. They are always upgrading their products to new features, which we like. It is a pretty stable tool, which doesn't require a lot of maintenance.

Our environment has SAP Fiori. They are also doing a HANA implementation. As far as the web, I don't work on that side as much.

I haven't used the Capture 2.0 very much.

My company brought on Worksoft to assist us with an SAP upgrade in order to make it so the testing was less stressful for business users through automated testing.

We configured Worksoft to setup our SAP testing environment after a refresh by regenerating all of our testing users. This sets them up with the right access, the right approvals, and everything on the back-end so we can do our scripts the next night.

The Capture 2.0 feature recording the process automatically as you go through. It saves everyone a lot of time. It allows the business to give IT the process they go through without having to spell it out so it can be recreated as an ongoing test.

There is a learn functionality where Worksoft learns applications that would be nice if Worksoft expanded its support for other applications that aren't web-oriented.

We have had some stability issues just getting stuff setup. It seems to be pretty stable outside of the web UI. We have had some issues with our testing running into nightly backups of database backups, etc. That has caused some issues, but when we get everything ironed out in a nice, controlled environment, it seems to be pretty good. The web can be a bit finicky sometimes, but it's just that the response times aren't always the same. So, it's a little harder for it to be resilient.

The scalability is really good. We had just talked with Worksoft about if there were any limits in terms of how long your scripts can run for or how many can be running at one time on the database. It seems the only concern is the hardware that you are running it on.

We ran into some issues with the version that we were on during the initial setup. We ran into a bug on one version, then they upgraded us to a new version, and we got hit with another bug. So, they had to put us in a beta. That was a little frustrating. However, besides the bugs that we ran into, the install was pretty straightforward.

It saves us time. It makes it so we are not as worried about changes which are going into the system. We know that we have nightly runs to ensure that things are working. In general, with upgrades, we can always rely on the testing to make sure that certain business processes are working. If they do stop working, we know when/where and can tie that back to changes in the environment easier.

Our eCommerce platform is Hybris. We run end-to-end tests where we place orders in Hybris, then we validate the order in ECC. Additionally, when an order is placed on Hybris, our QA environment has a lot of things which the SAP analysts have to prepare to get an order ready, so it doesn't clutter up the system, such as creating deliveries. Worksoft can do this for us as well.

Hybris is out most modern application. Our point of sale system is web-based, and it is in web form. We are on Azure. One of the things that we've been able to do is use Jenkins to put our Azure machines on business hours. We tell them to turn it off at 5 PM, then we tell them to turn it on at 7 AM. This has saved us about 62 percent of computer operations.

Prior to Worksoft, there were three different individuals within the company who worked collectively for about three years trying to automate just one of our smoke tests for our point of sale system. A lot of them got pretty far, but they weren't able to finish. However, with Worksoft, we have been able to automate six of our smoke tests in four months.

The most valuable feature is having a no-code solution for automation, so our QA team and some of our business users can work on automation. Then, they don't have to be developers.

Most of our SAP analysts use LiveTouch. They use LiveTouch along with prebuilt components. Our QA team uses LiveTouch when they need to add things.

I would like to learn how to get better logs for their support team.

It is fairly stable. We have run into some intermittent bugs off and on that we can't explain. Since they are typical Window's stuff, you just kill them.

When it is unstable, there will be times when a test that we are running in Certify will just stop, and it will say, "Aborted." There will be errors. There will be no explanation as to why it happens. It has now happened maybe one out of 20 times. When it happens, I just tell our QA team to stop Certify and restart it, hoping we don't see it again.

Scalability is throttled in part by the system that you are testing. So, how much testing can your system handle? 

I think they came out with a different type of licensing specifically for testing. Therefore, you don't have to use a more expensive user license, you can use an automation license. So potentially, if we had 100 use cases, we could spin up a 100 different machines, have them all run and be done in five minutes. That would be the goal, but I don't know if that would actually succeed or not.

For the couple of the issues that we were really scratching our heads over, we were in communication with the technical support several times, but they never got back to us. The issues are not critical because they're not really blocking anything. They're just annoying.

We needed a first step in order to get into DevOps. The first step was being able to automate our smoke tests and regression tests. They are tests that we use to make sure that our SAP environments are viable and our point of sale system. We chose Worksoft because they were the only people who we could find which were capable of automating SAP right out-of-the-box.

We needed a faster feedback loop. We have a third-party who develops our Hybris application for us and wanted to be able to hook into their Git repository, so when they push a new version, it would automatically deploy and run our smoke tests. Then, I can know within ten minutes if it works.

The new environment was pretty straightforward to set up. There were four servers, and maybe a fifth one, if you wanted to have a separate server for automation testing.

Some of the integration depends on the subject matter expertise on your team. How well do they know ECC and their processes? Then teaching them how to use Certify to build out their processes. So, on a scale of one to ten, it is probably a seven if you are not familiar with some of the development principles, like looping. If you are not familiar with them, then it will become more difficult to build out processes needed. This is just understanding the methodology of doing certain things, not Worksoft specifically.

The IT department and I worked with a Worksoft deployment engineer because of all of our Worksoft infrastructure. She walked us through setting up the database in SQL and the MongoDB with Worksoft Analyze. It was a pleasant experience. Most of the issues that we ran into were because I did not know something.

Because we haven't built out our suite of tests yet, we haven't saved that much time. However, we know that it will allow us to save a lot of time and money, because once we are fully DevOps, we'll be able to spin up and spin down our systems on demand. Then, we will know within 30 minutes whether the system deployed successfully or not.

We did not evaluate any other vendors. We didn't find anything else that did what we wanted.

if you can use Azure or AWS for your Worksoft infrastructure, then use that for ease of deployment. Once you have your environment, then you can save it using Infrastructure as Code. Thus, if you needed to rebuild or repurpose it, you would be able to do it.

We haven't taken advantage of all the current functionality.

We hardly use the Capture 2.0 feature at all.

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.