Worksoft Certify Reviews

We're using it to move manual tests over to automated tests to use on major programs and projects going on within the company. We are also moving to Dell EMC Embedded Boxes for an agile approach from a waterfall approach, and part of our new addition for 2019 after merging with a new company. Our role now is to automate as much as we can for usability.

We're doing mostly end-to-end testing scenarios. We use it on SAP and ServiceNow web services, along with SRM, CRM, and various applications.

We have an internal web portal, as well as an external. We did automation for it to do regression testing and build a test space.

The most valuable feature is its time saving. Once development is complete, the short time that it takes to execute a test is invaluable. It saves a number of dollars and man-hours. 

The Capture 2.0 feature is very intuitive, useful, and user-friendly. You can do so much with it now, versus the older version.

We had a lot of issues with the optics changing because they're dynamic. We just recently learned they are already worked on fixing it.

Another feature that they are also working on is being able to export processes from one project and upload it to another project. Therefore, we can change our both structures within Worksoft. We prefer to run and set it up based on business use for separate projects. It's exciting to know that this is coming. We want to be able to move assets from project to another project without having to be in the same project or the same folder structure.

I would like the GUI to be more user-friendly and intuitive. E.g., previously, the buttons were gray. Now, they have color to them and are fun for the user. It also makes them easier to identify.

It is very stable. For example, we used it with ServiceNow. We did automation all last year for an upgrade. Once they did the upgrade, we ran a test after the upgrade and everything was successful.

It is very scalable.

The technical support has been good, but sometimes there are little delays. A lot of times when we need support, it's an emergency situation. However, we are able to reach out to our contacts, and they're able to expedite it, which has been very helpful.

Our upper management wanted to be able to do testing much quicker than what we're actually doing with the manual process. We had to research and find a tool which could provide value for the company.

We had QTP, which wasn't very user-friendly from a coding perspective. There was only a small group of people who could actually use the tool. With Worksoft, we were able to push it out to the business.

I set it up. I just followed the instructions. It was easily done.

We've saved over 80 percent in time savings.

Worksoft Certify was the only tool that we found in which you did not have to know coding or know how to script to create a test. It's more user-friendly, more intuitive, and we also have business users who are actually developing as we speak on major projects and programs.

Worksoft was able to come in on a PoC and actually do automation development on the fly. The previous vendors that I worked with for months, they never could do one test within our environment. Our environment is very complex. It has a lot of policies turned on and off, which is a challenge for a lot of vendors.

Give them a chance, because you won't regret it.

We use the solution in pharmacy and retail.

We focus on automation solutions for SAP, Oracle, and Salesforce. Worksoft Certify is developed and designed to support these platforms. It matches what we want to achieve, providing capabilities in process mining and generating process documentation from these cases. Additionally, it can create RPA bots to execute tasks in production, making it a meaningful tool.

Worksoft developed a tool to support ERP testing. All prebuilt functions are good at steering the application when the test is executed.

Some features are missing from a testing perspective. You need to know how to connect everything to create requirements and stability metrics for the routine.

I rate the solution’s stability a seven out of ten.

You can scale it as you want. Just install it properly. It is suitable for enterprise customers.

I rate the solution’s scalability a ten out of ten.

The initial setup is easy and can be completed in two days. The team provided good support. 

I rate the initial setup a nine out of ten, where one is difficult, and ten is easy. 

They conducted marketing research through some external agencies, which reported an ROI of 583% over a five-year period. This is quite significant. You don't need people to edit test cases manually; instead, it creates and runs tests automatically whenever you wish, even after working hours or at any time.

The tool is worth the money.

The usability of test cases and running tests overnight is a definite advantage of Worksoft Certify. This provides great visibility into the process. One notable feature of Worksoft Certify is its support for SAP migration. For example, it fully supports SAP migrations. Many customers use ECC, which is becoming a legacy and must migrate to SAP S/4HANA. You can create your test cases in ECC and run them later in S/4HANA. It saves a lot of time. Additionally, you can perform parallel testing to ensure that the new functionality implemented in S/4HANA matches the legacy system.

I recommend Worksoft Certify because of its stability. The company has been in business for almost thirty years, maintaining the same customer base. They have a substantial portfolio and extensive experience, contributing to their reliability and effectiveness.

Overall, I rate the solution a nine out of ten.

We get user stories from the DevOps teams, in conjunction with a recording they make with another Worksoft tool. Then we will investigate if it has already been automated and, if not, to automate the process which has been delivered to us.

This is all set up in a Citrix environment. We have SAP being used at the moment and we still have the old SAP ECC up and running. I'm not sure which part of this is cloud-based, but the Certify solution is installed on Citrix.

Because of the fact that we started just six months ago and we have a small team. But slowly but surely we are gaining more audience; more people are starting to get interested. That should lead us to be able to start implementing it the way it should be done. We have done some regression testing and, when doing so, we found real issues. So it has proven itself to be useful during regression testing at least.

We have definitely seen savings in testing time. Scripts are executed five or even 10 times faster than any one of us could do by hand. While we don't do so at the moment, we are going to start executing them in a lights-out environment. We will run tests during the night and get more numbers, execute more tests. That should also help us save time. We have to get the experience and the numbers for this, but I think it will save us a lot of time.

The biggest feature is the fact that it's codeless. It takes away the problem of finding people with the correct programming language, since there are multiple such languages. It saves time in introducing people to the solution because they don't need programming knowledge, they just need to be able to think logically. This makes it vastly usable by more people who are not even acquainted with IT at all.

Also, the solution's web UI testing abilities for testing of modern applications is pretty awesome. Like with every product there are some parts which can be improved, but overall it's great.

It's very easy to use and to install. You have to know, as a user, what your exact application is on the test; you need to know which object recognition files you need to use.

You use the tool to do your automated testing. As far as I know at this moment, it can do a lot of stuff. It's usable in DevOps, so with regards to packaged and non-packaged software, it's good.

I use Capture from within Certify. I also have a stand-alone capture that I have up and running. If you look at the whole cycle, it takes the user a lot of time to create the records. During the capture, the responsiveness of the system is really slow. But after that, when you send it to Analyze, the documentation is really easy. Just click the button and choose the format. Automate is the same. You just create automation and choose a file name. Then, when you need it, you just download it into Certify and start using it. We've been doing it for some time now.

The Capture feature helps find the actual processes to test for and to create end-to-end testing. We ask the users, when we are making the recordings, not only to enter the proper data but also to provide us with comments or LiveTouch images of messages that need to be recorded. They know, "Okay, when I see this message then it's up and running." Because they take the end-to-end as a whole in the recording, we can use that as process knowledge as well. So the process is, in fact, being captured in the Analyze software.

In terms of the solution's ability to build tests and reuse them, I would rate it at eight out of 10. We record it on one environment. We make it completely environment-agnostic, data driven. Once recorded, we can reuse it on every single environment in the development cycle, which is awesome.

Performance on the web UI part, especially with some of the more comprehensive Fiori features, like the complex tables that are being used, could be improved. In those cases we have noticed a lot of execution-time increase with regards to the Certify solution.

I have been using Worksoft Certify for six months now. I started using it in September of 2019.

We've had no Certified-related stability problems. We have issues with things like Execution Manager and Analyze. I'm not sure if those problems are infrastructure-related or due to the Worksoft setup, but with regards to Certify it's stable. Sometimes there is a crash, but I think it's more related to the fact we're doing a lot of complex stuff in a Citrix environment with low resources.

The solution hasn't enabled us to scale up testing yet. We're on the way forward, but because of some issues in our own architecture we are not able to execute those tests. But I know how the setup is working, and I think you can scale up really easily; just add more machines, add more users, and have a go.

When I started within the program itself, no one else was using it. There were two users on the Railnova team. At this moment, about 10 or 12 people are using but within a couple of months we will be around 50 users in total.

I would rate Worksoft's technical support somewhere between a six or seven out of 10. In two-thirds of the cases we get a proper technical support member who has the knowledge to help us with our problem. But at other times we get someone who doesn't really know what he or she is doing or doesn't really understand the issue.

Another big part of the grade I gave is the fact that when you are in contact with the call center, a lot of times there really is a lot of background noise. With the accent, it's already really tough for me in fact to understand them, and with the background noise the problem gets bigger. But I've had also a lot of support from the Germans and from all over the world. Most of them are really capable.

It's an easy setup. There are some small configuration settings and then you can have a go. It's all up to the user to do the updates on the definition files. That's also easily available to us.

I started using the software without hearing from Worksoft. I only had to do some courses on the Worksoft University web page they provide. I didn't have any real, proper training, and I was up and running within two or three weeks. And within two months, I was able to provide enough support to get multiple teams within our company up and running with Worksoft. It's really straightforward.

I wasn't part of it, but I believe the initial setup and further configurations took two or three months in total.

Because of the fact that it's also able to do orchestration and because of the fact that our company is moving from the old SAP towards SAP Fiori — they wanted to have the main focus on Fiori for the UI part, in conjunction with the orchestration which Worksoft is able to do — at first it was only UI-driven. But we will expand into more and more Worksoft uses.

The company used a Worksoft consultant for the deployment but I don't know her name.

We, as a company, have good contact with one of the Dutch Worksoft managers and he introduced the integrator to us, as that manager is from the United States. The consultant came over for a week to give us some training on a number of things because we are not only using Certify.

They were really happy with her. A lot of questions were answered, a lot of issues were resolved. She was able to contact Worksoft support really fast. They had a blast while she was here.

We haven't seen ROI yet because we are in start-up mode with Certify. At this time we are only investing in the solution. Hopefully, we will be able to have some insights into ROI within a half-year from now.

The licensing is yearly.

My advice would be to think outside of the box. If you've chosen to work with Worksoft, you have to embrace the product as a whole. You will find, as with any other product, that some things that don't operate the way you want them to or would have expected them to. But if you teach yourself to view your problems from different angles using the software, then you will be able to come up with the most brilliant solutions. You can do much more with a codeless tool than you might think upfront.

The biggest lesson I have learned using comes back to the codeless part. I view myself as a smart guy, but I don't have the proper coding language knowledge. I was working for myself over the course eight years, before working here, and oftentimes the jobs were really cool, but most of the time I had to do Python and this and that. That was always a struggle because sometimes, when you've learned a language but you're not using it for a year or two years and you want to go back, you have to start remembering it. So I was turned down for those jobs. In this case, and we can show the world that it can be done codeless, if you have the proper tools.

When I was first introduced to Worksoft and they told me it was codeless, I was really skeptical. I said, "I don't see that happening," because I had been doing this for quite a while and was used to doing some coding. But the tool convinced me otherwise, which is really nice.

Overall, it's capable of being used in modern technology environments. I have been using it for six months now and I still have a lot of learning to do. And as a company, we need to start using more of the Certify features, not only scripting and rerunning those scripts.

Most of the people who are using it right now in our company already have some testing experience, but it's our goal to have business and IT people use the Capture feature as part of the process for DevOps.

We don't do test maintenance at the moment. We started out with test automation. We had to set up a base for the DevOps teams and then support them from that point onwards. So we are slowly moving into the maintenance part. Because we have split the data from the script itself — everything is data-driven — so it should be fairly easy for us to make the necessary changes. I think execution is faster when compared to human hand movements. But for changing or maintenance, I don't know.

The solution hasn't enabled us to find more defects at the moment, because we have been focusing on "happy path" testing. We need to get to the end-point of the end-to-end testing. But I believe, and I'm rather positive about this, that if defects are entered into the system, given that our regression test set covers a big percentage of the complete solution, it should be able to find defects really fast. Faster than we can.

The Certify users within our company are all in scripting. We're developers. And because we are in a scrum team, we don't have different roles in our team for test automation. A lot of things are being delivered by DevOps the teams, which you can view as functional consultants. As for the deployment and maintenance, a lot of it is outsourced to one of our partners. We do have functional and technical maintenance or support. I'm the technical guy and then we have two functional guys as well.

I use Worksoft Certify primarily for the functional testing of SAP applications.

I run Worksoft Certify for the entire end-to-end process flow to ensure that it is always working before and after patch upgrades, release upgrades, or any changes to the system when I run the test script.

My company gets some savings in manpower and cost and enjoys a boost in productivity because you only need a few hours to run end-to-end testing using the tool. If you do it manually, the process takes a few weeks, so Worksoft Certify greatly benefits my company.

What I like about Worksoft Certify is that end-to-end testing becomes faster.

The problem with Worksoft Certify is that it's not always stable. It runs on a live platform that's constantly changing, so the test script needs to be adjusted every time, which is very painful. That's the pain point in Worksoft Certify, and if Worksoft could make the solution more stable and more "change-proof," that would help my company greatly.

A feature I want to see in Worksoft Certify is for it to be able to work on test cases on mobile devices, though that could be difficult. I also wish to have more portability in the solution in terms of the script because, in the SAP environment, my company has to run Worksoft Certify in more than one system, so if Worksoft can make the process more portable, than would be fantastic.

I've been working with Worksoft Certify for about four years now.

Worksoft Certify could be more stable. It has stability issues.

Scalability is closely linked to stability. If Worksoft Certify is stable, then it's easily scalable, and if it's not stable, then it's still scalable, but every time, you have to make some adjustments.

I'm working with Worksoft Certify.

I always work with the latest version of the solution.

My rating for Worksoft Certify is eight out of ten.

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.

We use this solution for functional testing and end to end regression testing.

One of the biggest advantages for this solution is codeless automation. Because it is codeless, you can train people within a couple of hours.

The overall speed and performance of this solution could be improved. In a future release, it would be useful to be able to do API testing. 

I have used this solution for one and a half years.

The stability of this solution could be improved. 

This is a scalable solution. 

The first line support of this solution are not that knowledgeable. They do not know the products well. They have knowledge of common issues and provide a check list they want you to perform. If the issue reoccurs, they contact another layer of technical support and this is really good. 

Neutral

The initial setup of this solution was straightforward as long as you have the SQL database up and running. It is a quick setup. 

This solution is expensive. 

I would rate this solution a seven out of ten. 

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.

Our use cases are mainly from different domains for mobility solutions. It is also for HR and eCommerce.

We implemented more than 200 test cases for critically defined processes. 

It helps us understand the end-to-end scenario and how it can be divided into multiple subprocesses. Those sub processes can be used whenever required. Based on that, we design automation scripts, then reuse them wherever required.

The solution has enabled us to find defects since it is a test automation tool. However, irrespective of the tool used, we are testing to find defects. Thus, it has found defects in our projects.

Certify is a codeless automation tool with scripts that are easy to maintain. Since it doesn't use any coding language, a person (who is unaware of any language) can directly deploy just by training him/her on how the tool works. So, if a person is well aware of at least basic programming knowledge, it can then be deployed by providing basic training.

For SAP, we have many use cases. Certify is helping us to automate things, which is really awesome. The time spent to automate is less when compared with other tools.

Initially, there were challenges because there is a concept called XF definitions, where each application type, e.g., the vendor and workflow, has to provide these XF definitions. Last year, these XF definitions were not provided. However, whenever we face any issues, we have to raise a support case, then they update the XF definitions in our enrollment. This year, they improved that and have the last XF definitions for SAP Fiori updated as of February 2021.

For integration, projects are usually agile. The customers are looking for integration with CI/CD tools, like Jenkins, Jira, Xray, Zephyr, etc. There is no clear documentation on how to integrate Certify with these tools. Also, we didn't receive the required support when needed. Worksoft used to have webinars on this, but those webinars used to be on after the integration was established and how the integration works, not on how to create an integration.

They should come up with a solution on how to do the integration. Jenkins, Jira, and Certify should be the same in every company. The only thing required is the pipeline code required to integrate Jenkins, Jira, and Certify if they make it available for everyone. Also, if an expert team could help customers to integrate, then that would really help our customers a lot. 

As part of our weekly regression, we wanted to use Execution Manager. However, from 2017 until March 2021, Execution Manager was not working as expected in our enrollment. It could have been better. If Execution Manager had worked well, then we could have doubled our productivity. Unfortunately, it had problems. 

We have been using the solution since May 2017.

The stability of the solution depends on how good the Configuration of your environment is. We haven't faced any issues w.r.t the stability and performance. So we can say the solution works good. 

We have increased the number of tests that we run based on customer requirements.

Sometimes, the support engineers will be unaware of the solution for which a support case has been raised. Their competency or knowledge on the tool could be improved. When calling them, they will see the problem but need a senior engineer who will not be available. We will then be forced to have a second meeting. Waiting for meetings and solutions can be really hard for us because we can't deliver to our customers.

But since last some moths, Customer Support has improved as they conduct bi-weekly follow-up meetings to address our pain areas and expedite the solution for the Support cases which are open.

Neutral

Compared to our previous solution, Worksoft Certify reduces our test maintenance work by 50%.

The initial setup was straightforward.

It took us a lot of effort and nerves to get it really running. I would also expect for the major CI/CD pipeline tools that these are somehow handled and covered.

The last upgrade of Certify happened in the month of March. That upgrade's time was around 30 minutes to one hour. There were also preparations needed because of internal policies for taking care of backups, which were a bit time-consuming.

There are separate server and database teams who have their own SLAs for deployment. It all depends on different project specifications. 

We have seen ROI from using Worksoft Certify. For example, in the mobility sector, we are frequently finding issues or defects that might have come into production if not properly tested. Some of them might cost some $10,000 if we had waited to solve them after they went to production.

Automation using Worksoft Certify has saved our testing times by 40% to 50%.

We got subscription model licenses three or four weeks ago. Now, we are setting up enrollment for other products of Worksoft. It is recommended that we should do our migration and upgrades in a test enrollment environment first, then move to a production environment. 

In general, they changed their license model. Before you had to buy licenses for each component, and now they changed it so you can buy a license and use it for nearly all their applications.

We also evaluated Tricentis Tosca. Their pricing includes all their training. This is free of cost to everyone, even users without a Tosca license. If Worksoft came up with something similar, I think that they would get more customers.

We haven't bought any projects or use cases to automate Salesforce.

Worksoft Process Capture is a tool that captures the user actions. Usually, the functional consultant knows the functionality that has to be automated. We then have to install the feature on his machine for him to use Process Capture. The challenge is, since they will be unaware of the tool, we first need to educate him how to use the tool. Because of this challenge, we aren't using Process Capture right now.

I would rate this solution as eight out of 10. We are very satisfied with the solution.