Worksoft Certify Reviews

The primary use case is for SAP applications. We do some end-to-end testing of applications. We created a checking and boarding process for a flying scenario, which was innovative. For the back-end systems, we use it to do financial valuations.

We also have a SAP HCM module and SAP FI module where we are actively using Worksoft for our current automation.

We have Worksoft Certify on everyone's desktop. So, when we want to trigger automation, it is a advantage.

We use Worksoft Certify for smoke testing and regulation testing purposes.

There is no porting and it is easily adaptable. If you give it to a functional tester or business analyst, anyone can go, run the test, and analyze the results. It is easy to introduce automation tools to the team members. We have installed Worksoft for all of our team members. We have functional testers, business analysts, and manual test leads. We have an offshore automation team, as well as a functional team.

It is easily adoptable. I don't need to hire a highly skilled/trained person to learn it. For other tools, personnel need to be very professional and need to know how to use that tool beforehand, but very little education or help is required here. They can easily adopt and trigger the automation. 

We are not using Certify in the development area, only in the functional or end-to-end areas, and there is a lot of activity going on in the development area recently. Right now, the development teams are using open source tools, like Jenkins. This would be a game changer if Worksoft could start in the development area.

Going forward, Worksoft will be integrating with Jenkins, which will be great for us.

A part of our CI/CD pipeline, we have to deploy through Cloud AWS. So, it is good to hear that they are moving to AWS too.

The stability is pretty good. I haven't seen any stability issues.

One year ago, our SQL Server database was running slowly with it. Then, we upgraded our SQL Server database to the 2016 version. Before that, we had only upgraded Worksoft without upgrading our database, so we were noticing some latency issues. Once we upgraded our database, I have not received any complaints from our team members.

It is highly scalable and reusable. It is easy for team members to maintain and use with confidence. There is great versatility.

We have 16 applications that we do end-to-end testing using Worksoft.

Worksoft technical support is pretty good. A few times where we upgraded, our team members communicated everything to Worksoft well, and issues were resolved pretty quickly. They are pretty supportive. 

With one of our applications where we do check-in, Worksoft is not able to identify the Java-based application. We raised the ticket, but we were unable to resolve this using Worksoft.

Worksoft already existed when I joined. I am part of the team that maintains it.

If someone in the company wants Worksoft, they call the technology desk. Then, they get the proper license and credentials. The initial setup for these cases is straightforward.

Worksoft did the implementation. Our experience with them was great.

Later on, Cognizant took over from Worksoft.

The product has save us time by not needing highly skilled people, since it is hard to retain experienced development resources. Once we train our functional testers who are running the automation, they can the tool well and stable.

Cost-wise, compared with other tools, it is a great product.

Worksoft Certify is a great tool, which is easy to use and maintain, as no porting needed, development, nor high technical skills are needed. 

Worksoft Certify is a great automation tool for SAP applications.

We do test UI. The UI is very dynamic, as it keeps changing, now and then. It's a very critical, where we are using Worksoft to create innovation. However, our goal is to validate financial valuations. 

The company mainly uses Selenium for CI/CD processes for check-in. Therefore, each time a developers does a check-in, it automatically gives a bill with some pass/fail information, which includes Jenkins.

While we are not using the Capture 2.0 feature, it seems like it will be useful going forward with our end-to-end automation.

It is not for the entire automation process. It is mainly for anything which needs to be automated. Instead of just replacing human work, which it is doing now. It also includes robotic process automation for when we are replacing centralize manual work.

Our clients use Worksoft Certify for end-to-end testing of packaged applications and web UI testing of modern applications.

I have been using BPP and Execution Manager for more than seven years. I sell the product to different clients.

It is a great improvement, especially from my client side, where I have implemented it. One of my clients wanted to replace weekend production and support. They were using mini applications that did not need to work on the weekends. So, it was purely replaced with Certify's automation, so they did not need to come into the office on the weekends. This saves a lot of time and frees employees up on weekends.

The tool itself is a great tool. There are some other tool out there which support only web applications as opposed to only Windows-based applications, etc. It is a huge improvement, as it recognizes complex general applications, where most tools won't recognize the objects within them.

It is very easy to use, but there are some places where they need to improve their security. E.g., the BPP tool is just a URL, which does not ask you for a username and password. Anyone can login and can see it. This is a challenge.

Regarding the Execution Manager, which is good, since it comes with a username, password, etc. However, once you are logged inside, anyone can execute anything. It shouldn't allow this. Worksoft should create restrictions at the folder level structures, or somewhere they know they can align only few people to do the job, instead of allowing anyone do anything that they like.

The stability is good.

The scalability is working well for our needs.

The technical support is good. I would like them to get straight to the problem and provide solutions instead of asking a thousand questions.

Worksoft Certify has a very simple language. Our clients want to save on cost and ensure everyone who is manual testing knows it takes more effort.

The solution has cut our clients' test maintenance time for changes, like patches or system upgrades. They used to take a lot of time until the production validation completed. Now, it is just seconds until it is ready, so they can do executions within couple of minutes. 

This solution has enabled our clients to automate and save time (approximately 40 to 50 percent).

The product has saved our clients' money

The product works well with SAP and non-SAP products.

Use this tool. It is really good.

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 primarily use it for ERP testing. SAP is the primary application for the client, which we test using Worksoft.

We use Worksoft Certify for end-to-end testing of packaged applications. We have applications, like SAP, connecting with third-party applications, such as Oracle Transportation Management and other web applications. We have these type of use cases implemented and they are working pretty well.

We also use this solutions for web UI testing of modern applications.

With one of our top clients based in the Midwest, we have around 2500 automation scripts. These are not like unit level scripts, they are like big scripts. Previously, our development time for a medium complexity script was approximately three to five days. Now, it has come down to one and a half to two days. 

The turn around time for getting the automation tester familiarized with the tool is very quick, as it doesn't have any coding. It is fairly simple to understand.

The Capture 2.0 feature is very impressive. When creating documentation and automation, it is pretty quick, depending upon the size of the process you're trying to automate or capture. It has brought down the documentation and scripting time by at least 50 percent. It works in the background. It captures only the SAP window, it is not capturing their other work left in the emails or some confidential work that they have on the system. It's pretty seamless. Because it has security, I don't see it getting hacked. It's also pretty stable and works well.

We're really hopeful for the mobile testing in Worksoft Certify going forward. 

I would rate the stability as a seven out of ten. If there is a test script I'm running five times, I have apprehension that it might not be successful five times. The tool might be slow in +xcel or the tool will not be able to identify the same object/property. 

I have never seen the tool crash before.

It is scalable.

We use technical support quite a lot. I would rate them as an eight out of ten. They're pretty responsive, but it takes a long time to get issues resolved.

We usually replace tools, the Micro Focus UFT, with Worksoft Certify.

For a user to install it, the product can be complex.

Make sure you involve Worksoft while you do the installation. Follow their recommendations, which are very important, from framing of fuller structure designs or choosing the right capacity for the server. Their box of recommendations are definitely required.

We have cut maintenance testing time by 30 to 35 percent.

The solutions has saved us money. If we were doing everything manually, it would be two and a half times the cost.

We have a long partnership with Worksoft.

We integrated this solution with Jenkins and Micro Focus ALM for continuous testing. While Jenkins integration went pretty smoothly, Micro Focus ALM initially had hiccups.

The primary use case is SAP applications and customized web-based applications. Now, the company is moving into Salesforce, which is something big for us.

I've worked on multiple projects and our customers are very happy using it. The company is also very happy with the tool. 

We have something called automatic processing in SAP. Previously, the company was doing it manually, which used to take hours to days. Now, we have a script that processes 200 to 300 orders per day.

Everything is integrated with SAP and the web, and it works smoothly. However, we are not yet using it for web UI testing.

• The ease of use.
• It is understandable.
• Everything is integrated.

The Capture 2.0 feature is good. Our clients like using it. It does not take long to create documentation. Once the client knows how to use it, they capture the steps, like a recording. They give it to us for putting on the best practices, and we give them back the results. Efficiency-wise, it is pretty good.

I am looking forward to a feature which will be available in the next release, version 11. The search feature, where you can search for any process that you have created. 

I would like BPP to have more filtering options during the report creation. This would make our customers happy.

The product is stable.

The technical support is very good. They are helpful and provide solutions on time and very quickly.

Our customers come up with their requirements, then we come up with a PoC for them. If it works and their happy, they go ahead with it. 

I work with customers for new implementations.

The initial setup is pretty straightforward. There are a few packages that you need to install, then you have the tutorials which guide you on how to do it. It is that easy.

Our customers are saving money.

It saves us time: approximately 50 percent.

We have cut test maintenance time by 70 to 80 percent.

Experience working with the tool and explore the features of it, because I think the Worksoft Certify is the best and can do anything.

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.

We have been working on test automation for SAP-based platform for the last 15 years and leveraging Worksoft for SAP test automation in last 10 years. 

We have some fantastic use cases on how we can leverage Worksoft in large SAP transformation programs, especially for major global rollouts. If you look at some of the industries, like retail and logistics, we can see a lot of consolidation. When there is consolidation, we need to merge two SAP landscapes to a single landscape instance. It is a very complex transformation program. The testing is labor-intensive work in such a large scale IT landscape program. Worksoft has played a key role in delivering these complex integration programs on time, because we automated the core processes using Worksoft Certify. This helped us to automate the testing scenarios in new companies being integrated. At the same time, we test the existing company codes on the existing landscape to ensure that business as usual is not impacted.

If you look at the industry trend, the next six or seven years will be SAP S/4HANA migrations and adoptions of SAP cloud applications, whether it is SAP SuccessFactors, Ariba, or Fieldglass. We strongly believe that WorkSoft can play a pivotal role in delivering large-scale SAP S4 HANA programs since Worksoft can support the implementation of SAP cloud applications. We have delivered a couple of major SAP S/4HANA programs by leveraging Worksoft Certify. 

One of the key things that we have done is introduce test automation on day one in system integration testing (SIT). We don't want to wait until the program is over, then start the automation development. We start the automation right from the build phase, then we are able to deliver test automation on day one to the SIT.

If you look at the customer's experience, we have seen that if you take any testing engagement, whether it is large-scale system integration testing activities, UAT, or regression testing, and have seen that companies involve their business workforce to do lot of manual testing. Then, the business needs to take from the business critical activities and focus on testing. Worksoft significantly reduces the testing effort involved, so they can focus on their business critical activities. 

The company has been investing in a lot of new features. They are changing the trend in market demand, especially with their Worksoft Analyze features. These are important for customers when they have massive test case documentations. In addition, Worksoft is changing their direction towards Robotic Process Automation (RPA).

If you take any Robotic Process Automation, the key things you need are:

• The ability to automate SAP.
• The integrated software applications.
• Support for continuous testing or providing a platform to adopt DevOps.

I can see that Worksoft has been investing in these areas to make the product more relevant for SAP-centric platforms.

Another fantastic thing about Worksoft Certify is using it for end-to-end testing of packaged applications. We are able to automate, not just SAP, but the entire application ecosystem. If you take any company, SAP is the backbone, and if they use SAP ERP, then, there are multiple software applications, where some of them are SAP and some of them are non-SAP applications. Worksoft is one of the tools which can transcend across SAP and non-SAP applications. Non-SAP application include Java or .NET. Worksoft can seamlessly automate these applications.

If you take any ALM tool, Worksoft can be easily integrated, whether it is Micro Focus ALM or SAP Solution Manager. Another important thing is Worksoft's integration with SAP Solution Manager BPCA, this is helping customers to set up a risk-based testing platform. They can do impact assessment and identify test scripts to be tested based on the transports to be applied. Then, import that testing suite into Worksoft Certify and trigger the automation. We have seen that bi-directional integration between SAP solution manager and Worksoft Certify. This makes the product seamless, and if you take any company, they have their own ALM tool and the level of usage of Solution manager is varying. WIth the API that Worksoft provides, it can be easily integrated with the leading test management tools available in the market.

I would like Worksoft Certify to do automation at any layer (the UI layer, API layer, or database layer) and challenge competitors in the RPA industry, like UiPath and Automation Anywhere. 

A lot of customers are looking at testing, not just at the UI level, but testing the application or their ecosystem at the API layer. Worksoft could invest on testing on APIs. There are some open source tools available in market which do this, like SoapUI. 

The stability of the automation tool to run without any performance issues has improved with the use three-tier architecture. The three-tier architecture in Worksoft can help the customers access applications across globe. If global customers have geographically diverse teams, we recommend customers go with a three-tier architecture.

We have seen the customers starting their automation journey from zero test scripts to 8000 or 10,000 scripts. We have seen that Worksoft is able to scale up, then run thousands of test scripts concurrently and deliver value.

One of our customers has about 10 SAP applications with about 70 plus non-SAP applications. So, we automate approximately 80 SAP and non-SAP applications using Worksoft Certify.

A lot of our customers have used the technical support. Worksoft has a very good customer success team, as well as technical support team. When we started our first relationship with Worksoft, we had to build the integration between ALM and Worksoft Certify. So, Worksoft was agile enough to build that integration faster. We can see that the technical support team is fast enough to resolve some of the product bugs for any customer queries quickly. The team is open to build any type of new integrations to support the emerging tools available in the market.

As a partner, we help our customers to invest in the right tools and platform. So, we educate our customers to buy Worksoft Certify. We help them to build a business case or plan and do a joint PoC with Worksoft. We enable and empower our customers with enough details and help them to invest in the right automation tool for SAP, which is Worksoft Certify.

Some of our customers do not have any tools in their landscape. In that case, it is easy to position Worksoft Certify. Other customers already have other automation tools in their landscape in which they are experiencing a lot of pain points with their automation tool. They invested a lot of money in their automation tools and framework, but they did not realize the benefits. Therefore, we help those customers move away from their existing tools to Worksoft Certify. If they decide to build on their existing tool and use Worksoft Certify, it's a very complicated decision. We need to build a very strong business case and we also need to help the customers to migrate the automation test suite.

Worksoft installation is straightforward. They have a dedicated team to support the customers during the initial installation. It doesn't take more than couple of days to complete the installation. A lot of our customers are very happy with the way Worksoft completes the initial installations. 

Also, the professional services offered by Worksoft to help the customer to set up the test automation best practices using Worksoft has been helping the customers to roll out enterprise wide automation using Worksoft Certify.

Worksoft Capture 2.0 can help our customers to accelerate their automation development at least 40 percent faster than any other commercial tools available in the market.

We have seen that the initial Worksoft implementation has helped our customers reduce their testing cycle time by 50 percent. With further continuous improvement, we have seen cycle time reduced up to 75 percent. That is the level of productivity achieved using Worksoft Certify.

If I compare Worksoft Certify with other script-based automation tools, the test maintenance is relatively faster. We save about 60 to 70 percent of the maintenance effort by using it because it's model-based and scriptless. This helps the business team and the automation testers to quickly identify the changes needed to be introduced in the automation scripts.

The typical value realization takes about six to 12 months based on the number of scripts and how often the customer wants to execute.

Worksoft can help you to select the right automation platform, then deliver value quickly.

Our customers evaluate three or four major products along with Worksoft: Micro Focus UFT, Tricentis Tosca, Testimony from Basis Technologies, and then some of open source tools. Some of the customers evaluate all the tools, and some of the customers pick one of the other tools along with Worksoft Certify to make their decision.

There are a lot of tools available in the market. However, if you take any automation project, the lead time to implement an automation solution is typically, painfully longer. It may not give the right return on investments. 

We could have gone with any commercial tools available in the market or open source tools, but going with Worksoft gave us a few advantages. We were able to deliver and implement automation two and a half times faster than any other automation tools. Then, if you look at the total cost of effort to build, maintain, and run the scripts in the customer landscape, it is phenomenally low compared to other tools in the market.

Worksoft gives you return on investment faster than its competitors. It will make your QA organization more agile and nimble.

We recommend our customers be very serious about automation and not to experiment with too many tools. Start with a small PoC or pilot. Involve their business team to articulate the value of what Worksoft can deliver, not just within the IT department, but also the business. 

Worksoft Certify has ease of use, ease of maintenance, and value realization. Automation is not just completing testing faster, it's about reducing production support incidents, after go-live or ongoing production support incidents. It's a collective total cost of ownership and all about delivering value to the IT operations team, IT project team, and the business team.

With Capture 2.0, we have seen the product evolve. Worksoft Capture 2.0 is helping our customers to accelerate automation development. Introducing automation around day one is only possible because of Capture 2.0. When we are in the build phase, we can capture the important screens, whether it is in SAP Fiori apps, the SAP GUI, or SAP cloud apps. During the development phase, we can start building the automation scripts, then start leveraging automation on day one in SIT.

Worksoft can support modern UIs quite easily, such as SAP Fiori and Oracle Fusion. If you look at the modern UIs, it is all about the customer experience, and we have seen that Worksoft can evaluate that modern user interface and ensure that the customer experience is delivered as expected.

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.